4.0.0 HP PolyServe Software for Microsoft SQL Server Administration Guide (T5392-96056, March 2010)

End If
oRecordset.Close
oConnection.Close
Sub ShowUsage()
Wscript.Echo " USAGE: " & WScript.ScriptName & _
" SpnToFind [GC Servername or Forestname]"
Wscript.Echo
Wscript.Echo " EXAMPLES: "
Wscript.Echo " " & WScript.ScriptName & _
" MSSQLSvc/MySQL.company.com:1433"
Wscript.Echo " " & WScript.ScriptName & _
" HOST/Server1 Corp.com"
Wscript.Quit 0
End Sub
Sub ParseCommandLine()
If WScript.Arguments.Count <> 1 And WScript.Arguments.Count <> 2
Then
ShowUsage()
Else
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:
HP PolyServe Software for Microsoft SQL Server administration guide 119