SQLSERVERAGENT - error 1068

Question

SQLSERVERAGENT - error 1068

vinitjain

Mr or Mrs. 500

Points: 579
More actions
March 22, 2005 at 2:40 pm

#92639

Hi,
I am trying to start the sql server aganet from services and its giving me an "1068 - the dependency service or group failed to start"
I have read numerous posts on this error and everyone suggests that chaing the logon to local system account will solve the purpose. I have tried that many times buts its working.
When i click the start button from sql server agant interface, it gives me an error "%1 is not a valid win32 application "
Any takers of this problem ??
One more thing .. when i run the mssqlserver service i get -error 193 -ocx1
Pls help
Thanks
Vinit
March 25, 2005 at 8:00 am

This was removed by the editor as SPAM

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply

Jim P. SSCrazy Eights Points: 8725 More actions · Answer 1

Is the MSSQLSERVER service running?

The SQLSERVERAGENT service will not start unless the MSSQLSERVER is running. When you fire SQLSERVERAGENT, by default, it tries to start MSSQLSERVER.

In this post 9/21/2004 10:00:44 AM Re: Error starting Windows service created in c# States:

Sorry no good news here, but we have seen similar issues with .Net

based services that are running under a non-priviledged account. Is the service running under a non-priv account, or as LocalSystem?

One thing to try would be to run sysinterals Filemon utility during start up and see if there are any file permissions problems detected (access denied, file not found, etc.).

You need to check the account on the MSSQLSERVER service as well as the SQLSERVERAGENT. And if using a domain account, just double check it to make sure it isn't locked out.

One I've done just for testing - try changing the services to your admin account and password and see what happens. Note that you want adminsitrator rights on the server. You wouldn't need them if you could do it from the front end. (I jsut hashed this out in this Test server thread.)

Let us know.

----------------
Jim P.

A little bit of this and a little byte of that can cause bloatware.

vinitjain Mr or Mrs. 500 Points: 579 More actions · Answer 2

Thanks everyone. i serahced for the cause of "error 193 " and i found the reason.

There was a unidentidied file named "program" on root of my sytem drive which created all the problem.

I renamed the file to "program.old" and everything started working fine

Thanks

dgcraig SSC Enthusiast Points: 178 More actions · Answer 3

Thanks vinitjain!

I came accross the same problem. I had recently patched to SQL Server SP4. I had this new program file (no extension) located in the root of my D drive, which is where I have the SQL Server program files. The date on this file was 4/6/05, which corresponds to about the release date of SP4 (May 05), so I think that SP4 may be involved in the cause. I was able to move the problem file and start SQL Server.

Thanks again!

emmadiamond2k-875356 SSC Journeyman Points: 87 More actions · Answer 4

Hi,

This is a logon issue.

You have to start the MSSQLSERVER before you can run the SQLSERVER agent

Follow the steps below:

Click on start on the taskbar

click on run

type in: services. msc, then ok

On the servies pane look for MSSQLSERVER and double click on it.

Click on the log on tab

on the Log on as deselect This account and select Local System account option button

click on apply.

click on the general tab and click on start.

click on ok

that starts your MSSQLSERVER

Thereafter you can start your SQLSERVERAGENT.

I hope this sorts your problem

tosscrosby SSCoach Points: 18045 More actions · Answer 5

Ummmm - I believe a resolution was attained 4 months ago (and your suggestion was more or less proposed 6 months ago!).....but that's just me 😀

-- You can't be late until you show up.