July 6, 2004 at 7:59 pm
Hi All,
I have 2000 server in the Active directory domain, and every time I right click on the properties of the instance, I get this error created.
I have checked with our windows admin team, and they assure me that the server is in the AD domain. All other operations are fine. I just keep getting this error below. Any ideas gratefully received.
DESCRIPTION: Error: 0, Severity: 20, State: 0
Stored function 'xp_MSADEnabled' in the library 'xpstar.dll' generated an access violation
Regards,
Rob
July 9, 2004 at 8:00 am
This was removed by the editor as SPAM
December 8, 2006 at 8:45 am
Sorry I can't answer this but thought you would take comfort inthe fact that I am also getting it whenever I click on properties for a database on one specific server. Once I click OK the properties shows up fine.
March 19, 2009 at 11:07 am
Sorry, just another "Me too!":
I got this error for the first time today (in the windows System event log, slightly different message but found exactly the same in the SQL logs later for the same event), around the time that I logged on to the server via RDP and connected to enterprise manager.
I never actually saw any error in the interface, and the error has (so far) happened only once, but exactly the same message:
Stored function 'xp_MSADEnabled' in the library 'xpstar.dll' generated an access violation.
http://poorsql.com for T-SQL formatting: free as in speech, free as in beer, free to run in SSMS or on your version control server - free however you want it.
March 20, 2009 at 11:01 am
Is your sql instance MSSQLServerADhelper service running under local account or domain account? Try an domain account with admin priveleges.
MJ
November 16, 2009 at 6:53 am
I have a SQL 2K SP 3a cluster I just inherited, for business reasons i have to put off the upgrade to SP 4 until this weekend. (yeah i know that whole sentence is sad)
I am getting this same error if we fail over to Node 2 and a little more, this started just this weekend before that looking at the logs Node 2 was functioning fine.
but if the server fails over to Node2 I get a lot of errors when trying to run extended stored procs from xpstar.dll
when Node 2 has control, in Enterprise Manager if you try to view the sql error log you get (no items listed), the scheduled jobs fail, and if you right click on a job you cannot view the properties, however you can view the job history.
From what i've read it looks like the xpstar.dll is corrupted and re-isntalling the latest service pack should fix it. but if anyone has any experience to support this i would appriceate any info. I'll paste a couple of the errors on Node 2 below. (we are running off of Node 1 since everything is working on it)
Stored function 'sp_MSgetversion' in the library 'xpstar.dll' generated an access violation. SQL Server is terminating process 999..
Stored function 'xp_sqlagent_param' in the library 'xpstar.dll' generated an access violation. SQL Server is terminating process 999..
Stored function 'xp_enumerrorlogs' in the library 'xpstar.dll' generated an access violation. SQL Server is terminating process 999..
Twitter: @SQLBalls
Blog: http://www.SQLBalls.com
Channel: https://www.youtube.com/@Tales-from-the-Field
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply