Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

SQL Server Active Directory Helper on Local Computer...will not start Expand / Collapse
Author
Message
Posted Tuesday, December 9, 2008 12:08 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, December 9, 2008 4:02 PM
Points: 2, Visits: 6
To ALL, we had a power bump over the weekend, since then I cannot start this service.
It fails on start-up and I can't start thru the "Services"
I am sure this has been covered previously, but as a Noob I welcome any and all help.
Also I have a Access Control database that is dependent on this SQL, so If I have to reload......
I hope someone has a solution.
Thanx
Post #616397
Posted Tuesday, December 9, 2008 1:26 PM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Yesterday @ 9:41 AM
Points: 1,147, Visits: 1,942
What is your event viewer telling you? Usually this happens due to running a service under an account which has had a password changed, but I doubt you did that for this server, but perhaps.

Still, check your event viewer to find the actual error message.


---
SQLSlayer
Making SQL do what we want it to do.

Post #616467
Posted Tuesday, December 9, 2008 2:52 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, December 9, 2008 4:02 PM
Points: 2, Visits: 6
I have a couple different ones:
The most recent is;

Error. "0" is an invalid number of start up parameters. this service takes two start up parameters.

Failure Audit. Login failed for user "Velocity\VelocityServices" [Client :

Error. The log scan number (396831:16:2) passed to log scan in database 'Velocity' is not valid. This error may indicate data corruption or that log file (.ldf) does not match the data file (.mdf) If this error occured during replication, re-create the publication. Otherwise, restore from backup if the problem results in a failure during startup.

Error. Report Windows Service (MSSQLSERVER) cannot connect to the report server database.

No password has been changed, something hosed during it's power bump.
Is this simply a quick fix....replace corrupted file? or is this Major surgery?
Also when I try to pull up my database under the 'Databases' it has a caution symbol and has (Suspect) after it.
Just tring to throw everything in
Post #616541
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse