December 18, 2007 at 10:09 am
I'm a tech for a company that uses SQL to hold the data that supports an application we support. We have ran into a problem with a couple of different customers that are using the same baseline system (Server 2K3, SQL 2K)
A user went to Enterprise Manager and when he tries to expand the SQL Server he receives a "Connection failed, Check SQL Server Registration properties" message. The SQL Server registration properties are correct. If you try to use the "edit SQL Server Registration" function, you get a warning that the account doesn't have permissions/rights - The person is logged on as the Administrator of the server. The SQL Server icon indicates it is running, he also verified through SQL Service Manager that both the MSSQL Server and SQL Server Agent services are running. My company's application continues to work, even though it appears that the instance of SQL Server isn't connected/available?
Appreciate any guidance.
December 18, 2007 at 11:57 am
Are the client tools on their pc also updated to the server servicepack level?
server: sql server 2000 sp3 -> client enterprise manager sp3
server: sql server 2000 sp4 -> client enterprise manager sp4
Somewhat sturdier tool for testing a connection is the client tool Query Analyzer.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply