3.6.0 MxDB for SQL Server Installation and Administration Guide (5697-7088, December 2007)

Chapter 7: Troubleshooting 101
Copyright © 1999-2007 PolyServe, Inc. All rights reserved.
strSPN = WScript.Arguments(0)
If WScript.Arguments.Count = 2 Then
strGCPath = "GC://" & WScript.Arguments(1)
Else
'--- Get GC --
Set oNSP = GetObject("GC:")
For Each oGC in oNSP
strGCPath = oGC.ADsPath
Next
End If
End If
End Sub
Connection Error With Windows Authentication
When connecting to a SQL Server instance using local Windows
authentication, you may receive the following error:
Login failed for user '(null)'. Reason: Not associated with
a trusted SQL Server connection.
This error is addressed in the following Microsoft Knowledge Base
article:
http://support.microsoft.com/default.aspx?scid=kb;en-us;840219
Windows Authentication Fails with SQL Server
Replication
When replication is set up using SQL Server tools, by default the
replication agents are configured to use Windows authentication.
However, if at any time the replication agent runs on the same machine as
the replication distributor or publisher, the agent will fail to connect to
those instances. This situation occurs because of a SQL Server problem
described in the following Microsoft Knowledge Base article:
http://support.microsoft.com/default.aspx?scid=kb;en-us;840219
To work around this problem, you will need to modify the steps in the
replication job to use SQL authentication instead of Windows
authentication. Add the following options:
For the log reader agent:
logread [-?]
-Publisher server_name[\instance_name]