August 25, 2008 at 8:05 am
i have created a system DSN for my local machine and have created a performance counter log to log some processor info. when i try to start the log i get the following error in the event log:
The service was unable to open the log file SQL:perf data!test_000006 for log test and will be stopped. Check the log folder for existence, spelling, permissions, and ensure that no other logs or applications are writing to this log file. You can reenter the log file name using the configuration program. This log will not be started. The error returned is: The returned data is valid.
Anyone got any idea why i am getting this error?
August 25, 2008 at 8:38 am
If you're using the SQL Native Client try using the older SQL client in your DSN.
Also, make sure the counter is set to run with a Windows username/password that has a corresponding login on the SQL server.
Another option you might want to look at is using the RELOG utility to move the counters into a database periodically.
August 26, 2008 at 7:47 am
I tried this but no joy. I found in the error logs an error saying "Login failed for NT Authorityetwork service". I added this account as a logon with admin privileges, and although the error went away, i still get the error:
The service was unable to open the log file SQL:OldNativeClient!TestLog1 for log test and will be stopped. Check the log folder for existence, spelling, permissions, and ensure that no other logs or applications are writing to this log file. You can reenter the log file name using the configuration program. This log will not be started. The error returned is: The returned data is valid.
i then ran MMC/perfmon under the my credentials, and the credentials of the account that the sql server serivce run under, but get teh same error. any ideas?
August 26, 2008 at 8:14 am
I've always had to store locally as a CSV and then import with DTS.
August 26, 2008 at 8:21 am
When you configured the Perfmon Counter there's a section named "Run As", use your credentials for that.
August 26, 2008 at 8:30 am
Todd Engen (8/26/2008)
When you configured the Perfmon Counter there's a section named "Run As", use your credentials for that.
one of the first things i tried, under my credentials, and the credentials of the sql server service account. didnt work.
August 26, 2008 at 9:22 am
Not sure then.
How does your setup differ from following example?
Server1 running Windows 2003 has a local user account named User1 which is a member of the local administrators group. Server1 has SQL 2005 installed. When User1 is logged-on to the console at Server1 they open SSMS and create a Database named PerformanceData. User1 then opens the ODBC control panel and creates a System DSN that uses the "SQL Client", specifies the PerformanceData database as the default and chooses Windows authentication; testing the DSN passes. User1 opens Perfmon, then creates a new Counter log and specifies Processor:% Processor Time for the local system, in the Run As they put Server1\User1, then set the password. The Log file type is changed to 'SQL Database' and configured to use the new DSN. The counter is then started manually. Checking the PerfmonceData database in SSMS shows three new tables.
August 26, 2008 at 9:55 am
it doesnt. ive tried this exactly with the sql server service account and my account, both of which have admin access in this case. even tried it with Domain\servername$ but with no luck
August 26, 2008 at 10:12 am
Going on one of your other posts, are you still using a version of the SQL Native Client? Try using the one labeled "SQL Server" (SQLSRV32.DLL), not "SQL Native Client" (SLQNCLI.DLL).
I'm able to get that same error when switching to the SQL Native Client, with the other driver it seems to work fine.
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply