Discussion:
Biztalk 2006 Configuration issue
(too old to reply)
Steveo
19 years ago
Permalink
Hi Folks
I am having some configuration issues with Biztalk 2006.
My Environment is Win XP SP2, SQL 2005,VS 2005,Biztalk 2006, service packed
and updated completely etc.

This is all installed on my dev laptop which occasionally has to go out to
site to demo's, work onsite etc. The laptop is a member of a the domain here
wher I work.
I have installed BT several times now and reconfigured several times but my
main problem is that I cannot get BT2006 to work disconnected from the
network, even when i configure it to run all its different services under
local accounts to the laptop. I had no problems with managing this in BT
2004, so i have obviously missed something. If I am disconnected from the
domain and then run up Biztalk Server Administrtor and drill down to my
server I get the following error:
TITLE: BizTalk Server 2006 Administration Console
------------------------------

Failed to load Group [DEVLAPSTE:BizTalkMgmtDb] data providers.
(Microsoft.BizTalk.Administration.SnapIn)

For help, click:
http://go.microsoft.com/fwlink/?LinkId=47400&ProdName=Microsoft+BizTalk+Server+2006&ProdVer=3.5.1602.0&EvtSrc=Microsoft.BizTalk.Administration.SnapIn.Properties.Errors&EvtID=FailedLoadingGroupProviders&EvtChain=BTSAdminMsg+%2c9674

------------------------------
ADDITIONAL INFORMATION:

Instance of the WMI class is not found. (WinMgmt)

For help, click:
http://go.microsoft.com/fwlink/?LinkId=47400&ProdName=Microsoft+BizTalk+Server+2006&ProdVer=3.5.1602.0&EvtSrc=BTSAdminMsg&EvtID=9674

------------------------------

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: "[DBNETLIB][ConnectionRead
(recv()).]General network error. Check your network documentation."

------------------------------
BUTTONS:

OK
------------------------------


I also sometimes get the following :
"Could not generate SSPI context"

Is the error related to SQL 2005, I have checked that the service accounts
etc have access to the relevant databases.

Anyone any ideas????
Thanks in advance.
Cheers
Steve
Steveo
19 years ago
Permalink
...
Hi Folks
I fixed it, basically this is how I fixed it for my specific circumstances
which are that BT2006,SQL2005,VS2005 are all installed on a laptop that is a
member of a domain. I had TCP/IP enabled under "Protocols for MSSQLSERVER"
which can be found under "SQL 2005 Network Configuration" in SQL Server
Configuration Manager, this application is in the SQL server group off of the
Programs menu. Basically I have disabled this protocol, I have shared memory
and named pipes enabled. Now the admin console for Biztalk works when I am
connected to my domain and also when I am diconnected from the domain. I am
not sure what the long running impact of this is at the moment, I'm guessing
that someone else won't be able to use my server as a remote datastore and
authenticate with NT credentials, I could be wrong but that doesn't bother me
as thats not how we work. If TCP/IP is disabled in SQL server it won't need
an SSPI context to authenticate, in which case its not going to bother trying
to create one,which was the root cause of my problem.

Oddly enough I disconnected from the network logged on and ran up the BT2006
Admin console after disabling TCP/IP, it worked.
Then
I reenabled the TCP/IP prtocol and it still worked, then i logged off
reconnected the network cable.
Then
Logged on, ran the BT admin console, it worked, logged off and disconnected
the cable to the network.
Then
Logged on, ran the BT Admin tool, it failed.
Basically it looked as though it was caching the last successfully used
protocol to connect to SQL server, I'm not sure that makes sense? Can anyone
shed any light on that?
Cheers
Steve

Loading...