Problem restarting SQL Server Agent

We're running SQL Server 2000. Apparently the servers were restarted after
maintenance over the weekend (without telling me :-) and the SQL Server Job
Agent failed to restart. The option to 'AutoRestart SQL Server Agent if it
stops unexpectedly' is NOT set (and I'm not sure I have the authority to
change this option).
There were two messages in the Agent Error Log that appear relevant and
happened at about the same time..
[240] 1 engine thread(s) failed to stop after 30 seconds of waiting
[311] Thread 'JobInvocationEngine' (ID 3812) is still running
Can anyone explain to me what I'm seeing here? (Shouldn't the agent restart
automatically during a normal server startup? Also please define
'unexpectedly'. Does 'Unexpectedly' include server shutdowns?)
Hi
"B. Chernick" wrote:

> We're running SQL Server 2000. Apparently the servers were restarted after
> maintenance over the weekend (without telling me :-) and the SQL Server Job
> Agent failed to restart. The option to 'AutoRestart SQL Server Agent if it
> stops unexpectedly' is NOT set (and I'm not sure I have the authority to
> change this option).
> There were two messages in the Agent Error Log that appear relevant and
> happened at about the same time..
> [240] 1 engine thread(s) failed to stop after 30 seconds of waiting
> [311] Thread 'JobInvocationEngine' (ID 3812) is still running
> Can anyone explain to me what I'm seeing here? (Shouldn't the agent restart
> automatically during a normal server startup? Also please define
> 'unexpectedly'. Does 'Unexpectedly' include server shutdowns?)
These errors look like they have occurred during shutdown and not startup!
Check on the server properties in the general tab for Autostart policies
when the Operating System starts that Autostart SQL Agent is set to start.
John
|||My apologies. It looks like I appended too soon. I am not a full time DBA.
The agent option was unchecked.
(Looks like the problem is administrative, not technical.)
"John Bell" wrote:

> Hi
> "B. Chernick" wrote:
>
> These errors look like they have occurred during shutdown and not startup!
> Check on the server properties in the general tab for Autostart policies
> when the Operating System starts that Autostart SQL Agent is set to start.
> John
sql

Problem restarting SQL Server Agent

We're running SQL Server 2000. Apparently the servers were restarted after
maintenance over the weekend (without telling me :-) and the SQL Server Job
Agent failed to restart. The option to 'AutoRestart SQL Server Agent if it
stops unexpectedly' is NOT set (and I'm not sure I have the authority to
change this option).
There were two messages in the Agent Error Log that appear relevant and
happened at about the same time..
[240] 1 engine thread(s) failed to stop after 30 seconds of waiting
[311] Thread 'JobInvocationEngine' (ID 3812) is still running
Can anyone explain to me what I'm seeing here? (Shouldn't the agent restart
automatically during a normal server startup? Also please define
'unexpectedly'. Does 'Unexpectedly' include server shutdowns?)Hi
"B. Chernick" wrote:
> We're running SQL Server 2000. Apparently the servers were restarted after
> maintenance over the weekend (without telling me :-) and the SQL Server Job
> Agent failed to restart. The option to 'AutoRestart SQL Server Agent if it
> stops unexpectedly' is NOT set (and I'm not sure I have the authority to
> change this option).
> There were two messages in the Agent Error Log that appear relevant and
> happened at about the same time..
> [240] 1 engine thread(s) failed to stop after 30 seconds of waiting
> [311] Thread 'JobInvocationEngine' (ID 3812) is still running
> Can anyone explain to me what I'm seeing here? (Shouldn't the agent restart
> automatically during a normal server startup? Also please define
> 'unexpectedly'. Does 'Unexpectedly' include server shutdowns?)
These errors look like they have occurred during shutdown and not startup!
Check on the server properties in the general tab for Autostart policies
when the Operating System starts that Autostart SQL Agent is set to start.
John|||My apologies. It looks like I appended too soon. I am not a full time DBA.
The agent option was unchecked.
(Looks like the problem is administrative, not technical.)
"John Bell" wrote:
> Hi
> "B. Chernick" wrote:
> > We're running SQL Server 2000. Apparently the servers were restarted after
> > maintenance over the weekend (without telling me :-) and the SQL Server Job
> > Agent failed to restart. The option to 'AutoRestart SQL Server Agent if it
> > stops unexpectedly' is NOT set (and I'm not sure I have the authority to
> > change this option).
> >
> > There were two messages in the Agent Error Log that appear relevant and
> > happened at about the same time..
> >
> > [240] 1 engine thread(s) failed to stop after 30 seconds of waiting
> > [311] Thread 'JobInvocationEngine' (ID 3812) is still running
> >
> > Can anyone explain to me what I'm seeing here? (Shouldn't the agent restart
> > automatically during a normal server startup? Also please define
> > 'unexpectedly'. Does 'Unexpectedly' include server shutdowns?)
> These errors look like they have occurred during shutdown and not startup!
> Check on the server properties in the general tab for Autostart policies
> when the Operating System starts that Autostart SQL Agent is set to start.
> John

Problem restarting SQL Server Agent

We're running SQL Server 2000. Apparently the servers were restarted after
maintenance over the weekend (without telling me :-) and the SQL Server Job
Agent failed to restart. The option to 'AutoRestart SQL Server Agent if it
stops unexpectedly' is NOT set (and I'm not sure I have the authority to
change this option).
There were two messages in the Agent Error Log that appear relevant and
happened at about the same time..
[240] 1 engine thread(s) failed to stop after 30 seconds of waiting
[311] Thread 'JobInvocationEngine' (ID 3812) is still running
Can anyone explain to me what I'm seeing here? (Shouldn't the agent restart
automatically during a normal server startup? Also please define
'unexpectedly'. Does 'Unexpectedly' include server shutdowns?)Hi
"B. Chernick" wrote:

> We're running SQL Server 2000. Apparently the servers were restarted afte
r
> maintenance over the weekend (without telling me :-) and the SQL Server Jo
b
> Agent failed to restart. The option to 'AutoRestart SQL Server Agent if i
t
> stops unexpectedly' is NOT set (and I'm not sure I have the authority to
> change this option).
> There were two messages in the Agent Error Log that appear relevant and
> happened at about the same time..
> [240] 1 engine thread(s) failed to stop after 30 seconds of waiting
> [311] Thread 'JobInvocationEngine' (ID 3812) is still running
> Can anyone explain to me what I'm seeing here? (Shouldn't the agent resta
rt
> automatically during a normal server startup? Also please define
> 'unexpectedly'. Does 'Unexpectedly' include server shutdowns?)
These errors look like they have occurred during shutdown and not startup!
Check on the server properties in the general tab for Autostart policies
when the Operating System starts that Autostart SQL Agent is set to start.
John|||My apologies. It looks like I appended too soon. I am not a full time DBA.
The agent option was unchecked.
(Looks like the problem is administrative, not technical.)
"John Bell" wrote:

> Hi
> "B. Chernick" wrote:
>
> These errors look like they have occurred during shutdown and not startup!
> Check on the server properties in the general tab for Autostart policies
> when the Operating System starts that Autostart SQL Agent is set to start.
> John

Problem registering a remote server

Hey all...
We have several websites running SQL server back ends and we have
successful registrations for each in SQL Servers Enterprise Manager.
We also have a client who hosts their own SQL Server Database and we
used to have a good registration for their SQL Server.
Our client has moved their website and SQL Server to a new server as
the machine they were running on had an unknown fault, and since they
have moved everything we can no longer see the database or register
the server in Enterprise Manager.
We can still register servers from other clients and the client we are
having trouble with can register their server using standard dial up
connections and the admin guy did it from his cable modem account from
home. We have tried using the VPN tunnel they prepared for us as well
as trying to register after they put the server outside the firewall.
The only firewall changes that were made wer after our first being
unable to connect, then they allowed all traffic from our IP in.
To summerize, They can register SQL Server externally (from home etc)
and we cannot, but we can register all other SQL Servers except
theirs.
Any Ideas?What error do you get when you try to connect?
Rand
This posting is provided "as is" with no warranties and confers no rights.|||The error dialog reads:
==========
SQL Server registration failed because of the connection failure
displayed below. Do you wish to register anyway?
SQL Server does not exist or access denied
ConnectionOpen(Connect())
==========
I think it may be some sort of firewall problem, but they assure us
that the server has been placed outside their firewall during some
attempts to connect and our firewall is definately working OK as we
can connect to other, ISP hosted SQL Servers.
rboyd@.onlinemicrosoft.com (Rand Boyd [MSFT]) wrote in message news:<NGHck8z7DHA.1812@.cpmsftngx
a07.phx.gbl>...
> What error do you get when you try to connect?
> Rand
> This posting is provided "as is" with no warranties and confers no rights.sql

problem pushing subscriber updates to publisher in transactional replication -

I have a primary and secondary servers both running Windows 2000 SP3 with SQL 2000 SP3. I have set up transactional replication with the primary server as publisher and the secondary server has the distributor and subscriber DB. I am testing the scenerio where my primary server goes down and I have to make updates to the secondary server until my primary server comes back up. I am able to update my subscriber database and the transactions go into the MSreplication_queue table to be pushed back to the primary when it comes back up. When I bring the primary server back up and start the queue agent job it starts pushing the transactions over and then stops after 4 or 5 transactions with the error "Failed while applying queued message to publisher". I have attached part of the log file for the agent below

dbserver2.Old_Processing: {? = call dbo.sp_getsqlqueueversion (?, ?, ?, ?)}
dbserver2.Old_Processing: {? = call dbo.sp_replsqlqgetrows (N'DBSERVER', N'Old_Processing', N'Old_Processing')}
[4/15/2004 3:59:47 PM]dbserver2.distribution: exec dbo.sp_helpdistpublisher @.publisher = N'DBSERVER'
Connecting to DBSERVER 'DBSERVER.Old_Processing'
DBSERVER.Old_Processing: {? = call dbo.sp_getqueuedarticlesynctraninfo (N'Old_Processing', 21)}
SQL Command : <exec [dbo].[sp_MSsync_ins_IQ2KProcSystem_1] N'dbserver2', N'Old_Processing', '072175', '2004-03-19 00:00:00.000', 1>
DBSERVER.Old_Processing: {? = call dbo.sp_getqueuedarticlesynctraninfo (N'Old_Processing', 15)}
SQL Command : <exec [dbo].[sp_MSsync_ins_NightlyProcess_1] N'dbserver2', N'Old_Processing', '072175', '2004-03-19 00:00:00.000', '2004-04-15 15:56:44.623000000', 'Begin ProcessIQ2KSystem', 'AB14E5D7-C81D-4A39-A8F5-51F1C48227B0', '17E5D98F-EDF0-41D0-9991-97511B850720', 1>
SQL Command : <exec [dbo].[sp_MSsync_upd_IQ2KProcSystem_1] N'dbserver2', N'Old_Processing', '072175', '2004-03-19 00:00:00.000', 1>
DBSERVER.Old_Processing: {? = call dbo.sp_getqueuedarticlesynctraninfo (N'Old_Processing', 7)}
SQL Command : <exec [dbo].[sp_MSsync_upd_TheatreProcess_1] N'dbserver2', N'Old_Processing', '072175', 1, '2004-03-19 00:00:00.000', 1, NULL, '79A114D6-FF31-4E37-AC2D-90C0A0114F40', '072175', 1, '2004-03-19 00:00:00.000', 0, NULL, 'AF61A098-44A3-45D7-B25B-E8EA9CD464A1', 0x2800, 1>
Failed while applying queued message to publisher
Disconnecting from DBSERVER 'DBSERVER'
Worker Thread 692 : Task Failed
Disconnecting from dbserver2 'dbserver2'
Processed 3 queued trans, 3 cmds, 0 conflicts
Queue Reader aborting

In the sql server logs I am getting this message:
Replication-Replication Transaction Queue Reader Subsystem: agent Repl Queue Reader failed. Failed while applying queued message to publisher.
Error: 14151, Severity: 18, State: 1

Any help would be greatly appreciatedFew suggestions:
Refer to SQLAgent log for further information.
Meanwhile, stopping and restarting SQLServerAgent may allow you to temporarily resolve the problem that you are experiencing.

Did you try to forcefully terminate any replication agents in task manager by any chance?

Finally, running the snapshot agent from the command line may allow you to determine whether it was the snapshot agent that crashed unexpectedly.|||Originally posted by Satya
Few suggestions:
Refer to SQLAgent log for further information.
Meanwhile, stopping and restarting SQLServerAgent may allow you to temporarily resolve the problem that you are experiencing.

Did you try to forcefully terminate any replication agents in task manager by any chance?

Finally, running the snapshot agent from the command line may allow you to determine whether it was the snapshot agent that crashed unexpectedly.

The SQLAgent log did not have any errors in it

Stopping and restarting SQLServerAgent did not allow me to temporarily resolve this problem. I still get the same error.

I did not forcefully terminate any replication agents in task manager.

Should I run the snapshot agent from the command line or the queue agent since the queue agent is what is failing?

I tried running the queue agent from the command line and it failed with the same error as above|||Check whether the KBA [http://support.microsoft.com/default.aspx?scid=kb;EN-US;294970] is any good to you.|||I don't think that is my problem. The only way I have been able to get the queue agent to work again is to either drop and readd the subscription or reinitialize the subscription. Of course when I do this it wipes out any updates that have been done to the subscriber.

Problem of Permissions for Linked Servers in .net page

I searching using Keywords in MS Word and pdf documents for which i
have used the Index Server and linked with SQL Server but when i am
running the stored procedure thro my webpage i'm getting these errors.
And when i run this code in Query Analyzer its giving expeceted
results. I dont know where the problem is can anyone help please . I'm
really badly stuck. Thanks in Advacne
User does not have permission to perform this action. Line 3: Incorrect
syntax near '@.searchstring'. Invalid object name 'FileSearchResults'.
And my stored procedure is given below
CREATE PROCEDURE SelectIndexServerCVpaths
(
@.searchstring varchar(100)
)
AS
Exec sp_addlinkedserver FileSystem,
'Index Server',
'MSIDXS',
'Web',
'c:\inetpub\wwwroot\sap-resources\Uploads'
IF EXISTS (SELECT TABLE_NAME FROM INFORMATION_SCHEMA.VIEWS
WHERE TABLE_NAME = 'FileSearchResults')
DROP VIEW FileSearchResults
EXEC ('CREATE VIEW FileSearchResults AS SELECT * FROM
OPENQUERY(FileSystem,''SELECT Directory, FileName,
DocAuthor, Size, Create, Write, Path FROM
SCOPE() WHERE FREETEXT(''@.searchstring'')'')')
SELECT * FROM FileSearchResults F, CVdetails C WHERE C.CV_Path = F.PATH
AND C.DefaultID=1
GONext time print out the strings you build before executing them.
See if this helps:
exec ('CREATE VIEW FileSearchResults AS SELECT * FROM
OPENQUERY(FileSystem,''SELECT Directory, FileName,
DocAuthor, Size, Create, Write, Path FROM
SCOPE() WHERE FREETEXT(' + @.searchstring + ')'')')
ML
http://milambda.blogspot.com/|||Thanks for your reply
its not working out.
I modified the stored procedure as shown below
its giving no errors but no results but if i execute the same without
the stored i'm gettting the expected results
Thanks in Advance
IF EXISTS (SELECT TABLE_NAME FROM INFORMATION_SCHEMA.VIEWS
WHERE TABLE_NAME = 'FileSearchResults')
DROP VIEW FileSearchResults
EXEC ('CREATE VIEW FileSearchResults AS SELECT * FROM
OPENQUERY(FileSystem,''SELECT Directory, FileName,
DocAuthor, Size, Create, Write, Path FROM
SCOPE('''' "c:\inetpub\wwwroot\sap-resources\Uploads" '''') WHERE
FREETEXT(''''@.searchstring'''')'')')
SELECT * FROM FileSearchResults F, CVdetails C WHERE C.CV_Path = F.PATH
AND C.DefaultID=1