MSO OL sp2 for BCM broke SQL Database connection

[MaitreMind]

Two days ago an MS update for MSO OL sp2 for BCM wanted to be installed so I
left it get installed. After the installation I noticed that my data
connection to the BCM database was broken.

I am using MSSQLSERVER instance name for SQL Server Developer Edition
instead of MSSQL instance name which is for SQLEXPRESS. I have been usine SQL
Server Developer edition with BCM for quite awhile without any problem but
now after sp2 was installed I cannot connect to the database as it cannot
find it.

I ran the database Admin tool to share it and everything ran successfully
with a pretty instruction page that opened in IE to walk one through
connecting to the database in OL. The initial connection failed when I
selected the connect to an existing databse as it wanted to connect to the
default SQLEXPRESS instance, then I typed in the computer name
localhost\MSSQLSERVER,1433 and it cannot find the database to connect.

Has anyone else had this ridiculous issue and how can I solve it?

 

[Luther Blissett]

Two days ago an MS update for MSO OL sp2 for BCM wanted to be installed so I
left it get installed. After the installation I noticed that my data
connection to the BCM database was broken.

I am using MSSQLSERVER instance name for SQL Server Developer Edition
instead of MSSQL instance name which is for SQLEXPRESS. I have been usineSQL
Server Developer edition with BCM for quite awhile without any problem but
now after sp2 was installed I cannot connect to the database as it cannot
find it.

I ran the database Admin tool to share it and everything ran successfully
with a pretty instruction page that opened in IE to walk one through
connecting to the database in OL. The initial connection failed when I
selected the connect to an existing databse as it wanted to connect to the
default SQLEXPRESS instance, then I typed in the computer name
localhost\MSSQLSERVER,1433 and it cannot find the database to connect.

Has anyone else had this ridiculous issue and how can I solve it?

By default, BCM creates and uses a sql instance named MSSMLBIZ, and
not the default instances. If Sql is installed by BCM Setup, it
doesn't even create the default instances.

 

[Raul Thomas]

Also the port number has to be 5356

--
Regards

Rahul Thomas [MSFT]

The posting is provided "AS IS" with no warranties and confers no rights.
https://blogs.msdn.com/rathomas