Biztalk Configuration Problems
Calvin Willman
Domain. I've running VS.NET 2005 and SQL Server 2005.
Installation goes ok. SSO configures ok. I get problems when trying to
configure BizTalk Runtime. I get following error message.
TITLE: Microsoft BizTalk Server 2006 Configuration Wizard
------------------------------
Failed to setup database objects associated with BizTalk Host
"BizTalkServerApplication" on MessageBox database server "LAPTOP" / database
name "BizTalkMsgBoxDb".
BizTalk Server cannot access SQL server. This could be due to one of the
following reasons:
1. Access permissions have been denied to the current user. Either log on
as a user that has been granted permissions to SQL and try again, or grant
the current user permission to access SQL Server.
2. The SQL Server does not exist or an invalid database name has been
specified. Check the name entered for the SQL Server and database to make
sure they are correct as provided during SQL Server installation.
3. The SQL Server exists, but is not currently running. Use the Windows
Service Control Manager or SQL Enterprise Manager to start SQL Server, and
try again.
4. A SQL database file with the same name as the specified database already
exists in the Microsoft SQL Server data folder.
Internal error from OLEDB provider: "Cannot open database "BizTalkMsgBoxDb"
requested by the login. The login failed."
SQL Server seems to be fine though. I'm able to log in using Windows
Authentication. I've also created a user called BizTalk on both Server and
Windows Users and given the required Rights/Permissions... As well as
Administrator. I used the same login on the opening configuration page the
basic configuration page.
I've been trying this for hours and it's really getting me down!
Kiggins@discussions.microsoft.com Peter Kiggins
> I'm trying to configure BizTalk on my notebook, which isn't part of a
> Domain. I've running VS.NET 2005 and SQL Server 2005.
>
> Installation goes ok. SSO configures ok. I get problems when trying to
> configure BizTalk Runtime. I get following error message.
>
> TITLE: Microsoft BizTalk Server 2006 Configuration Wizard
>
> ------------------------------
>
>
>
> Failed to setup database objects associated with BizTalk Host
> "BizTalkServerApplication" on MessageBox database server "LAPTOP" / database
> name "BizTalkMsgBoxDb".
>
> BizTalk Server cannot access SQL server. This could be due to one of the
> following reasons:
>
> 1. Access permissions have been denied to the current user. Either log on
> [...]
> Internal error from OLEDB provider: "Cannot open database "BizTalkMsgBoxDb"
> requested by the login. The login failed."
>
> SQL Server seems to be fine though. I'm able to log in using Windows
> Authentication. I've also created a user called BizTalk on both Server and
> Windows Users and given the required Rights/Permissions... As well as
> Administrator. I used the same login on the opening configuration page the
> basic configuration page.
>
> I've been trying this for hours and it's really getting me down!
>
Me too. Have you had any responses, or managed to solve this yourself?
--Pete
Morten
I am not connected to a domain. Could that be the problem?
Here is my log file:
2006-07-21 13:36:11:0031 [WARN] AdminLib GetBTSMessage: hrErr=c0c025ca; Msg=BizTalk Server cannot access SQL server. This could be due to one of the following reasons:
1. Access permissions have been denied to the current user. Either log on as a user that has been granted permissions to SQL and try again, or grant the current user permission to access SQL Server.
2. The SQL Server does not exist or an invalid database name has been specified. Check the name entered for the SQL Server and database to make sure they are correct as provided during SQL Server installation.
3. The SQL Server exists, but is not currently running. Use the Windows Service Control Manager or SQL Enterprise Manager to start SQL Server, and try again.
4. A SQL database file with the same name as the specified database already exists in the Microsoft SQL Server data folder.
Internal error from OLEDB provider: "Cannot open database "BizTalkMsgBoxDb" requested by the login. The login failed.";
2006-07-21 13:36:11:0062 [WARN] AdminLib GetBTSMessage: hrErr=c0c02529; Msg=Failed to setup database objects associated with BizTalk Host "BizTalkServerApplication" on MessageBox database server "BIZTALK" / database name "BizTalkMsgBoxDb".
BizTalk Server cannot access SQL server. This could be due to one of the following reasons:
1. Access permissions have been denied to the current user. Either log on as a user that has been granted permissions to SQL and try again, or grant the current user permission to access SQL Server.
2. The SQL Server does not exist or an invalid database name has been specified. Check the name entered for the SQL Server and database to make sure they are correct as provided during SQL Server installation.
3. The SQL Server exists, but is not currently running. Use the Windows Service Control Manager or SQL Enterprise Manager to start SQL Server, and try again.
4. A SQL database file with the same name as the specified database already exists in the Microsoft SQL Server data folder.
Internal error from OLEDB provider: "Cannot open database "BizTalkMsgBoxDb" requested by the login. The login failed.";
---
Posted via www.DotNetSlackers.com
Peter Kiggins
> I have the same problem. I use a stand alone win xp, sql 2005 and bts 2006.
>
> I am not connected to a domain. Could that be the problem?
>
> Here is my log file:
>
> 2006-07-21 13:36:11:0031 [WARN] AdminLib GetBTSMessage: hrErr=c0c025ca; Msg=BizTalk Server cannot access SQL server. This could be due to one of the following reasons:
> 1. Access permissions have been denied to the current user. Either log on as a
>
> [ ... ]
>
> 4. A SQL database file with the same name as the specified database already exists in the Microsoft SQL Server data folder.
>
> Internal error from OLEDB provider: "Cannot open database "BizTalkMsgBoxDb" requested by the login. The login failed.";
I did solve the problem - which of the steps I took actually solved I'm not
sure. I did the following:
1) Uninstalled everything I had installed (BT, SQL, Visio). The instruction
for removing BT and friends were clear and effective.
2) Re-installed as a local user, up to and including "Configure BT".
3) "Configure BT" failed in a number of ways.
4) Go edit the groups for the installing user (a member of *everything* was
my frustrated choice).
5) In SQL Management Studio, make sure the installing user is a dbcreator,
serveradmin, and sysadmin (server->security->logins).
A general step is to delete the databases that get half-made when
configuration goes wrong, mostly using SQL Management Studio. The most
extreme example was a database with files left lying around and which SQL
Management Studio could not "see". In this case, the files themselves needed
deleting.
I still have some problems with BAM Tools and BAM Portal - something for
anotehr day ;)
--Pete
morten
I use a local user (administrator and member of everything...) for the
installation. This user is sysadmin in SQL, and has created the group
databases correctly.
I have installed bts 2002 before, and it didn't give me any problems at
all. But installing 2006 seems almost impossible.
Peter Kiggins
"morten" wrote:
> I have tried it two, but it didn't work for me.
> I use a local user (administrator and member of everything...) for the
> installation. This user is sysadmin in SQL, and has created the group
> databases correctly.
Is SQL Server Agent running? A box needs to be checked during the install,
so it an easy one to miss.
>
> I have installed bts 2002 before, and it didn't give me any problems at
> all. But installing 2006 seems almost impossible.
>
There seem to be a lot of traps, and too many generic error messages. I
wonder if there is a gap between the technology used to check for
configuration, and the technology used for configuration.
--Pete