BCM with Server 2008 Warren 11/20/2008 6:04:46 PM I'm moving from SQL 2005 to SQL 2008 for a Shared BCM database, I've tried using the BCM manager database tool to backup and restore the database to the new server and receive "Cannot retrive the list of SQL Server instances. Please make sure that SQL Server 2005 or SQL Server 2005 Express is installed and that the service is running" This also happened when I tried to create a new database in SQL 2008. I've also tried using SQL server backup and restore to copy the database, clients can't connect to the new database either using computer\instance,1172 "Cannot access the database server on computer 'server'"

Re: BCM with Server 2008 Luther <enowning[ at ]gmail.com> 11/24/2008 4:47:19 PM On Nov 20, 10:04 am, Warren <War...[ at ]discussions.microsoft.com> wrote: [Quoted Text] > I'm moving from SQL 2005 to SQL 2008 for a Shared BCM database,  I've tried > using the BCM manager database tool to backup and restore the database to the > new server and receive "Cannot retrive the list of SQL Server instances.   > Please make sure that SQL Server 2005 or SQL Server 2005 Express is installed > and that the service is running"  This also happened when I tried to create a > new database in SQL 2008.   > > I've also tried using SQL server backup and restore to copy the database, > clients can't connect to the new database either using computer\instance,1172 >   "Cannot access the database server on computer 'server'" If you have a Sql Server 2005 instance with a BCM database, update to Sql 2008, then the Sql 2008 install should migrate the BCM's MSSMLBIZ sql instance to 2008, the instance retaining the same TCP port number and user permissions. At least that's my theory. Because it is supposed to work side-by-side with sql 2005, the sql 2008 setup may have to be tweaked; e.g. specify that MSSMLBIZ should be migrated. I know some people on this list have switched to sql 2008. Perhaps they can share their findings. I've noticed that Sql 2008 has stricter permissions (at least on Vista) than 2005. That means that some actions in BCM or the database tool (which was designed to work with Sql 2005) may not work without changing some default permissions on Sql 2008. However, I have not seen a list of what permissions need to be changed to make sql 2008 behave like 2005.

Re: BCM with Server 2008 Warren 11/25/2008 5:58:01 PM Let's try and make this simplier. I have a SQL 2005 instance installed on Server 2008. I install the BCM database manager and when I run it to create or share a database it doesn't recognize any SQL instances installed. "Cannot retrive the list of SQL Server instances. Please make sure that SQL Server 2005 or SQL Server 2005 Express is installed and that the service is running" "Luther" wrote: [Quoted Text] > On Nov 20, 10:04 am, Warren <War...[ at ]discussions.microsoft.com> wrote: > > I'm moving from SQL 2005 to SQL 2008 for a Shared BCM database, I've tried > > using the BCM manager database tool to backup and restore the database to the > > new server and receive "Cannot retrive the list of SQL Server instances. > > Please make sure that SQL Server 2005 or SQL Server 2005 Express is installed > > and that the service is running" This also happened when I tried to create a > > new database in SQL 2008. > > > > I've also tried using SQL server backup and restore to copy the database, > > clients can't connect to the new database either using computer\instance,1172 > > "Cannot access the database server on computer 'server'" > > If you have a Sql Server 2005 instance with a BCM database, update to > Sql 2008, then the Sql 2008 install should migrate the BCM's MSSMLBIZ > sql instance to 2008, the instance retaining the same TCP port number > and user permissions. At least that's my theory. Because it is > supposed to work side-by-side with sql 2005, the sql 2008 setup may > have to be tweaked; e.g. specify that MSSMLBIZ should be migrated. I > know some people on this list have switched to sql 2008. Perhaps they > can share their findings. > > I've noticed that Sql 2008 has stricter permissions (at least on > Vista) than 2005. That means that some actions in BCM or the database > tool (which was designed to work with Sql 2005) may not work without > changing some default permissions on Sql 2008. However, I have not > seen a list of what permissions need to be changed to make sql 2008 > behave like 2005. >

Re: BCM with Server 2008 Luther <enowning[ at ]gmail.com> 11/26/2008 4:41:36 PM On Nov 25, 9:58 am, Warren <War...[ at ]discussions.microsoft.com> wrote: [Quoted Text] > Let's try and make this simplier.  I have a SQL 2005 instance installed on > Server 2008.  I install the BCM database manager and when I run it to create > or share a database it doesn't recognize any SQL instances installed.   > > "Cannot retrive the list of SQL Server instances.   > Please make sure that SQL Server 2005 or SQL Server 2005 Express is installed >  and that the service is running"   > > > > "Luther" wrote: > > On Nov 20, 10:04 am, Warren <War...[ at ]discussions.microsoft.com> wrote: > > > I'm moving from SQL 2005 to SQL 2008 for a Shared BCM database,  I've tried > > > using the BCM manager database tool to backup and restore the database to the > > > new server and receive "Cannot retrive the list of SQL Server instances.   > > > Please make sure that SQL Server 2005 or SQL Server 2005 Express is installed > > > and that the service is running"  This also happened when I tried to create a > > > new database in SQL 2008.   > > > > I've also tried using SQL server backup and restore to copy the database, > > > clients can't connect to the new database either using computer\instance,1172 > > >   "Cannot access the database server on computer 'server'" > > > If you have a Sql Server 2005 instance with a BCM database, update to > > Sql 2008, then the Sql 2008 install should migrate the BCM's MSSMLBIZ > > sql instance to 2008, the instance retaining the same TCP port number > > and user permissions. At least that's my theory. Because it is > > supposed to work side-by-side with sql 2005, the sql 2008 setup may > > have to be tweaked; e.g. specify that MSSMLBIZ should be migrated. I > > know some people on this list have switched to sql 2008. Perhaps they > > can share their findings. > > > I've noticed that Sql 2008 has stricter permissions (at least on > > Vista) than 2005. That means that some actions in BCM or the database > > tool (which was designed to work with Sql 2005) may not work without > > changing some default permissions on Sql 2008. However, I have not > > seen a list of what permissions need to be changed to make sql 2008 > > behave like 2005.- Hide quoted text - > > - Show quoted text - Possibly a permissions issue. Have you tried running the tool as admin.

Re: BCM with Server 2008 Warren 11/26/2008 6:18:11 PM Yes I was running the tool as an admin. The only other thing I can think of is this is a 64bit server.

Re: BCM with Server 2008 Warren 11/26/2008 8:00:00 PM Issue resolved. 64 Bit instance was the problem I installed a 32 bit instance and that solved the problem.

Re: BCM with Server 2008 MichaelMc 12/31/2008 4:26:01 AM Could you please give me some guidance? I am in the same predicament of being unable to use the Database Tool on a 64-bit Windows Server 2008 machine with SQL Server 2008 installed. I have a 64-bit default instance and a 32-bit MSSMLBIZ instance, but I still get the error that says that the Database Tool cannot determine the SQL server instances and that it needs SQL Server 2005. Thanks. "Warren" wrote: [Quoted Text] > Issue resolved. 64 Bit instance was the problem I installed a 32 bit > instance and that solved the problem.