Forums  Register  Login  My Profile  Inbox  Address Book  My Subscription  My Forums 

Member List  Search  FAQ  Ticket List  Log Out

 

Problems checking SQL Server 2000

  		Logged in as: Guest
Users viewing this topic: none
  Printable Version
All Forums >> [Networking & Security] >> GFI Network Server Monitor >> Problems checking SQL Server 2000 Page: [1] 2   next >   >>
Login
Message << Older Topic   Newer Topic >>
Problems checking SQL Server 2000 - 25.Jul.2005 8:28:00 AM   
MaZo

 

Posts: 11
Joined: 24.Jul.2005
Status: offline 		Hi,

I'm trying to monitor our MS SQL Server 2000, but I am unable to login. The SQL Server runs in mixed mode (Windows & SQL login).

The parent folder is using the domain admin credentials, and my connection string is as follows:

Provider=sqloledb;Data Source=xxx;Initial Catalog=master;User Id=sa;Password=xxx;

Now the weird part. Even though I use the 'sa' SQL account, I'm getting the following error:
quote:
Queuing check...
The check is being loaded by the engine...

Result: Failed
Explanation: ERROR: Opening connection to database, ADO error: IDispatch error #3149 Login failed for user 'DOMAIN\Administrator'.
Why is it using the parent credentials while I filled in the 'sa' user credentials? The rule even says Credentials -> Not Used.

[Confused]

Edit:

I have the same on a different MS SQL Server 2000 (which isn't on a domain), it just tries to login using the parent (folder) credentials!

[Frown]

[ July 25, 2005, 02:45 PM: Message edited by: MaZo ]
Post #: 1
RE: Problems checking SQL Server 2000 - 25.Jul.2005 9:34:00 AM   
Doug Ferguson

 

Posts: 8
Joined: 17.Jul.2005
From: Eugene
Status: offline 		I have had the same kind of luck on our SQL 2000 Servers. No matter which DB I try or which user account I try to use I get this error:

quote:
Queuing check...
The check is being loaded by the engine...

Result: Failed
Explanation: ERROR: Opening connection to database, ADO error: IDispatch error #3149 Login failed for user 'gfinsm'.

NOTE: This is a dry run test to help set up the proper parameters for the monitoring check. No email/sms/network notifications are sent out when the "Monitor Now..." option is used.

When this monitoring check will fail the following groups will be notified:

Email Notifications
------------------------------------------
<No groups/users configured to be notified>

SMS Notifications
------------------------------------------
<No groups/users configured to be notified>

Network Notifications
------------------------------------------
<No groups/users configured to be notified>
Has anyone got the SQL Server 2000 monitoring check to work? If you did, can you share what the secret is?

Thanks -

[ July 25, 2005, 03:35 PM: Message edited by: Fergy ]

(in reply to MaZo)
Post #: 2
RE: Problems checking SQL Server 2000 - 25.Jul.2005 6:19:00 PM   
blaster88

 

Posts: 16
Joined: 12.Jun.2005
From: McLean, VA
Status: offline 		I am monitoring dozens of SQL2k dbs with the ADO availability check - you are using the Generic ADO type when you create it?

(in reply to MaZo)
Post #: 3
RE: Problems checking SQL Server 2000 - 25.Jul.2005 11:12:00 PM   
MaZo

 

Posts: 11
Joined: 24.Jul.2005
Status: offline
quote:
Originally posted by AvAdmin:
I am monitoring dozens of SQL2k dbs with the ADO availability check - you are using the Generic ADO type when you create it?
What connection string are you using?
And why is it inheriting from the parent folder while I use the 'sa' user to connect to the db?

(in reply to MaZo)
Post #: 4
RE: Problems checking SQL Server 2000 - 26.Jul.2005 1:55:00 AM   
blaster88

 

Posts: 16
Joined: 12.Jun.2005
From: McLean, VA
Status: offline 		I think the reason it is using the folder credentials is your string - you specify "Data Source."

Try something like this:

Provider=sqloledb;Server=[Server name or ip];Initial Catalog=master;User Id=sa;Password=[password];

(in reply to MaZo)
Post #: 5
RE: Problems checking SQL Server 2000 - 26.Jul.2005 3:21:00 AM   
amusc

 

Posts: 130
Joined: 19.Nov.2002
From: Malta
Status: offline 		The login failure is being caused by the database check trying to make use of folder credentials. When the folder has alternate credentials specified, then the MS SQL/ADO check will try to use those credentials.

In many cases, the folder would have credentials to log on to machines and not those of SQL Server itself, causing the logon to fail.

To workaround this issue, put the MS SQL/ADO checks in a separate folder which does not use alternate username and password.

In this way, the username and password defined in the connection string can be used.

(in reply to MaZo)
Post #: 6
RE: Problems checking SQL Server 2000 - 26.Jul.2005 4:23:00 AM   
MaZo

 

Posts: 11
Joined: 24.Jul.2005
Status: offline
quote:
To workaround this issue, put the MS SQL/ADO checks in a separate folder which does not use alternate username and password.
The method sucks, but it works! [Smile]

GFI has to fix this if u ask me.

[ July 26, 2005, 10:31 AM: Message edited by: MaZo ]

(in reply to MaZo)
Post #: 7
RE: Problems checking SQL Server 2000 - 26.Jul.2005 5:20:00 AM   
Calin Ghibu

 

Posts: 1194
Joined: 15.Dec.2002
Status: offline 		Yes this issue has been confirmed by the development team and will be addressed.

In order to re-create your situation it would be helpful if you could indicate what type of logon you use to the SQL Server : NT Authentication mode or mixed mode ?

Thanks and regards,

[ July 27, 2005, 04:21 AM: Message edited by: Calin Ghibu ]

(in reply to MaZo)
Post #: 8
RE: Problems checking SQL Server 2000 - 27.Jul.2005 3:49:00 AM   
MaZo

 

Posts: 11
Joined: 24.Jul.2005
Status: offline
quote:
Originally posted by MaZo:
Hi,

I'm trying to monitor our MS SQL Server 2000, but I am unable to login. The SQL Server runs in mixed mode (Windows & SQL login).
[Wink]

(in reply to MaZo)
Post #: 9
RE: Problems checking SQL Server 2000 - 27.Jul.2005 8:33:00 PM   
Calin Ghibu

 

Posts: 1194
Joined: 15.Dec.2002
Status: offline 		Hi,

The issue occurs only when you specify alternate credentials on the folder containing the check.
The issue is that the check details wrongly specify that it does not use the folder credentials. This will be fixed.

In case alternate credentials are provided, the engine will try to conenct with Windows authentication to the sql server, using those credentials, and will not parse the connection string to determine the authentication type to be used.

This problem will be fixed and the authentication types will be made more clear to the user.

Did you manage to get get your check working?

The workaround would be to either use another folder which does not have alternate credentials, or to make the necessary changes to the connection string so that windows authentication is used.

Since you are running in mixed mode, I think the latter option is best because you only need to change the connection string for the check, provided that you use an user member of the Administrators group as alternate credentials on the folder containing the check, as the Adminnistrators group have by default perissions on the sql server.
An example of connection string whihch uses windows authentication would be :

Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=yourdatabase;Data Source=sqlserver;

Let us know how it went.

Thanks and regards,
Calin

[ July 28, 2005, 02:35 AM: Message edited by: Calin Ghibu ]

(in reply to MaZo)
Post #: 10
RE: Problems checking SQL Server 2000 - 28.Jul.2005 9:14:00 PM   
MaZo

 

Posts: 11
Joined: 24.Jul.2005
Status: offline 		Yes, I managed to get the check working by putting it in a seperate folder (and use the sa credentials).

Thanks for helping!

Edit:

Your second method doesn't work for me:
quote:
Queuing check...
The check is being loaded by the engine...

Result: Failed
Explanation: ERROR: Opening connection to database, ADO error: Unspecified error Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.
Adding the 'Trusted_Connection=true' parameter didn't solve this problem.

[ July 29, 2005, 03:29 AM: Message edited by: MaZo ]

(in reply to MaZo)
Post #: 11
RE: Problems checking SQL Server 2000 - 28.Jul.2005 11:37:00 PM   
Calin Ghibu

 

Posts: 1194
Joined: 15.Dec.2002
Status: offline 		hi,

The second option works in your initial setup: when the check was in the folder which had credentials. The connection string I gave as an example is for windows authentication, the engin will use the windows credentials provided in order to connect to the SQL server. This solution is good in case , due to licensing or other reasons, you do not want to have your SQL check in a targetless , no credentials folder.

Best regards,
Calin

(in reply to MaZo)
Post #: 12
RE: Problems checking SQL Server 2000 - 29.Jul.2005 3:03:00 AM   
MaZo

 

Posts: 11
Joined: 24.Jul.2005
Status: offline 		Hi,

I tested your solution in my initial setup (the parent folder was using the domain admin account to login).
Unfortunately it didn't work.

(in reply to MaZo)
Post #: 13
RE: Problems checking SQL Server 2000 - 29.Jul.2005 3:55:00 AM   
Calin Ghibu

 

Posts: 1194
Joined: 15.Dec.2002
Status: offline 		hmm,

You still got the logon failure error?

Normally, by default, domain admin is member of the local admins group on the SQL machine (provided it is in the domain)who have rights to connect to the database.

Can you check the logons available on the SQL Server?

Best Regards,
Calin

(in reply to MaZo)
Post #: 14
RE: Problems checking SQL Server 2000 - 29.Jul.2005 10:47:00 AM   
MaZo

 

Posts: 11
Joined: 24.Jul.2005
Status: offline 		Yep, still got the error.
I also checked the SQL logins right after the error, but the DOMAIN\Domain Admins group has enough rights.

(in reply to MaZo)
Post #: 15
Page:   [1] 2   next >   >>
All Forums >> [Networking & Security] >> GFI Network Server Monitor >> Problems checking SQL Server 2000 Page: [1] 2   next >   >>
Jump to:





New Messages No New Messages
Hot Topic w/ New Messages Hot Topic w/o New Messages
Locked w/ New Messages Locked w/o New Messages
 Post New Thread
 Reply to Message
 Post New Poll
 Submit Vote
 Delete My Own Post
 Delete My Own Thread
 Rate Posts