Re: SQL 2K SSL Connection Problem

Why did not you check (I assume you did not because you didn't mention it) the SQL Server service itself?

SQL Server Agent is dependant on the SQL Server service. If SQL Server Service is not running then the Agent won't run. So ensure your SQL Server service runs and the best practice for SQL Server service is using a domain account in domain environments.

Check SQL Server Error Logs and Windows Event Logs for possible error reasons if your SQL Server service does not start.

If it runs then try to log in to your SQL Server using EM and ensure it works.

--
Ekrem Önsoy



"Jim Raykowski" <JimRaykowski@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:B829DF60-CBE4-41E1-BD87-D411B497F00B@xxxxxxxxxxxxxxxx
Windows 2003 x64 edition with service packs. SQL 2000 with SP4 installed
supporting Microsoft Groove Server. After OS and SQL, created a special
account for use groove and gave the acct server and security admin and create
DB perms, installed fully patched both and then installed MS Groove Manager.
Initially had a few network issues but resolved all and eventually was able
to create all groove all grove domain intengrate with AD and sync. Added
relay server and then started adding users to test. Added two users in the
late afternoon got their clients connected and then went home for the
evening. I was able to access the groove manager web site and make all
configuration change no issues.
When I cam in the next morning I was unable to access the groove manager
web site or connect to the database using EM. In the app event log there is
an ASP.NET 2.X error. It is below
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 1/24/2008 9:43:14 AM
Event time (UTC): 1/24/2008 5:43:14 PM
Event ID: 4b1f69a8eb8444a597530de82542821b
Event sequence: 5563
Event occurrence: 5562
Event detail code: 0

Application information:
Application domain: /LM/W3SVC/1/Root/GMS-1-128456698832752092
Trust level: Full
Application Virtual Path: /GMS
Application Path: C:\Inetpub\wwwroot\GMS\
Machine name: GBGRV1

Process information:
Process ID: 2092
Process name: w3wp.exe
Account name: NT AUTHORITY\NETWORK SERVICE

Exception information:
Exception type: GMSException
Exception message: Database error

Request information:
Request URL: http://gbgrv1/gms/ManagementServer.aspx
Request path: /gms/ManagementServer.aspx
User host address: 192.168.2.60
User:
Is authenticated: False
Authentication Type:
Thread account name: NT AUTHORITY\NETWORK SERVICE

Thread information:
Thread ID: 1
Thread account name: NT AUTHORITY\NETWORK SERVICE
Is impersonating: False
Stack trace: at Groove.Management.Server.GMSDBProc..ctor(String
connectionString, String procName)
at Groove.Management.Server.GMSObject.FetchParameters(String ipprocName)
at Groove.Management.Server.GMSObject.PrepareCommand(String ipprocName)
at Groove.Management.Server.GMSObject.Execute(String ipprocName)
at Groove.Management.Server.GMSServer..ctor()
at Groove.Management.Server.GMSServer.get_Instance()
at
Microsoft.GrooveManagementServer.UI.Controls.GMSUIResourceUtility.GetFirstValidUserCulture()
at
Microsoft.GrooveManagementServer.UI.Controls.GMSUIResourceUtility..ctor(String[] ipUserLanguages, Hashtable& ipRMHashtable, ArrayList& ipSupportedCultures)
at
Microsoft.GrooveManagementServer.UI.Global.Application_BeginRequest(Object
sender, EventArgs e)
at
System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean&
completedSynchronously)

The EM error is as follows:

A connection could not be established to (local).
Reason: SSL Security error
ConnectionOpen (SECDoClientHandshake()).

Please verify SQL Server is running and check you SQL Server Registration
properties (by right-clicking on the (local) node) and try again.


When I checked to see if the SQLServerAgent was running it was not so I
tried to start it and received the below error:

SQLServerAgent could not be started (reason: Unable to connect to server
‘(local)’;SQLServerAgent cannot start).


It appears that the groove manager server is running but I am unable to do
anything to the domain. Any ideas with these errors? As an FYI you have to
use a cert with Groove and I decided to use the built in capability of groove
to manage certs.

TIA,
--
Jim

"Nothing is fool proof to a talented fool"

.

Relevant Pages

  • Re: xpsql.cpp
    ... The SQL Server service account also needs the rights below. ... > SQLAgentCmdExec login in EM and restarting SQL Server can help. ...
    (microsoft.public.sqlserver.security)
  • Re: Distributed Query - Linked Servers?
    ... Server1 - backend SQL Server ... the domain user account will not be able to register SPNs ... or register the SPNs manually using the SetSPN ... enable the SQL Server service account for delegation. ...
    (microsoft.public.sqlserver.server)
  • Re: Get "credentials not valid" message installing SQL2008 Failver
    ... The user account that I'm supplying does exist. ... "Geoff N. Hiten" wrote: ... Microsoft SQL Server MVP ... credentials for the SQL Server service are not valid. ...
    (microsoft.public.sqlserver.setup)
  • Re: sql server
    ... The message is saying that you have SQL Server setup to use ... the local system account for the startup account. ... You need to change the SQL Server service startup account to ...
    (microsoft.public.sqlserver.security)
  • Re: file backup component
    ... Otherwise you can try to use audit techniques to find out who's trying to access the LDF file. ... file backup app or any other app that need LDF file a while. ... he meant something that belongs to the SQL server itself. ... Delay the start of the SQL server service until manual start. ...
    (microsoft.public.windowsxp.embedded)