Francisco Tapia
fhtapia at gmail.com
Fri Aug 18 15:16:48 CDT 2006
On a hunch I thought that maybe the DLL's were removed when BackupExec was removed (as you know Backupexec will install MSDE for it's purposes of tracking backups). I checked for the default DBNETLIB.DLL (TCP/IP) and then DBNMPNTW.DLL (Named Pipes) but found that they were still in the system, the next thing I thought was that possibly the client network utility didn't have them enabled, so I poped it open and sure enough they were "not" enabled. A quick enable and my agent was back online On 8/18/06, Mohammed Uddin <MohammedU at autobytel.com> wrote: > Thanks for sharing... > How did you find the protocols removed? > > Mohammed. > > -----Original Message----- > From: listbounces at sswug.org [mailto:listbounces at sswug.org] On Behalf Of > Francisco Tapia > Sent: Friday, August 18, 2006 11:04 AM > To: sql2k at ls.sswug.org; dba-sqlserver at databaseadvisors.com > Subject: Re: [SQL2K] My Agent was assasinated!! - Revived > > Mohammed, > And others, (follow-up) It turns out that the fix was a lot easier > than that, I opened up the client network utility and found that the > TCP/IP and Named Pipes protocols were removed on the uninstall of > BackupExec. I re-added these protocols and the Agent was able to > start up again! > > > > On 8/18/06, Mohammed Uddin <MohammedU at autobytel.com> wrote: > > Please check SQL error log and SQL Agent Error log first for any > > possible errors. And also check for any .dmp files too in the sql > error > > log folder. > > > > Mohammed. > > > > -----Original Message----- > > From: listbounces at sswug.org [mailto:listbounces at sswug.org] On Behalf > Of > > Francisco Tapia > > Sent: Friday, August 18, 2006 8:33 AM > > To: SQL Server 2k List; dba-sqlserver at databaseadvisors.com > > Subject: [SQL2K] My Agent was assasinated!! > > > > Helpdesk guy on an instruction from our sysadmin, was instructed to > > visit one of my sql servers and "UNINSTALL" BackupExec from the > > machine as we have moved to a central backup system. After the > > install the server came up but he did not know to check in EM that the > > sql server was running and that the agent was running... > > > > ON the server you cannot use EM to see the (local) sql server status, > > remotely I can use EM and verified that the server is running, and all > > my users can access the server just fine. What is not running is the > > Sql Server Agent. And I am not able to restart it for some reason. > > Any advise would be very helpful. > > > > -- > > -Francisco > > http://pcthis.blogspot.com |PC news with out the jargon! > > http://sqlthis.blogspot.com | Tsql and More... > > > > > > ------ > > For archives, see http://www.sswug.org/archives > > For list assistance, contact members at sswug.org > > To unsubscribe, email lists at sswug.org with > > UNSUBSCRIBE SQL2K in the body of the message. > > > > > > > > > > ------ > > For archives, see http://www.sswug.org/archives > > For list assistance, contact members at sswug.org > > To unsubscribe, email lists at sswug.org with > > UNSUBSCRIBE SQL2K in the body of the message. > > > > > > > > > > > -- > -Francisco > http://pcthis.blogspot.com |PC news with out the jargon! > http://sqlthis.blogspot.com | Tsql and More... > > > ------ > For archives, see http://www.sswug.org/archives > For list assistance, contact members at sswug.org > To unsubscribe, email lists at sswug.org with > UNSUBSCRIBE SQL2K in the body of the message. > > > > > ------ > For archives, see http://www.sswug.org/archives > For list assistance, contact members at sswug.org > To unsubscribe, email lists at sswug.org with > UNSUBSCRIBE SQL2K in the body of the message. > > > > -- -Francisco http://pcthis.blogspot.com |PC news with out the jargon! http://sqlthis.blogspot.com | Tsql and More...