I've set up transactional replication with queued updating. If I stop the queue reader agent through EM, I can't start it again. Agent's history says "Queue Reader aborting. The step failed."
All servers are SQL Server 2000 SP3.
Help is greatly appreciated!
Hello,
by mistake I added an queue reader agent to a distribution database. But how can I drop the queue agent. There isn't a stored proc 'sp_dropqreader_agent'.
The only way I found (apart from dropping the whole distribution databse) is to stop and disable the generated job!
Is there any other way to get rid of the queue reader agent ?
Wolfgang
Hi All,
I would appreciate any help here at all. I am pulling my hair out!
I am unable to start the snapshot agent or log reader agent from within SQL management studio. it fails on executing step 2 with unknown username or bad password.
I have checked all account details and they are correctly using my domain admin account. I can connect to SQL using teh same account and it also has sysadmin permissions.
If i copy the step 2 paramters and start from the cmd prompt (again logged in using the same domain account) they both start fine.
Any ideas would be gratefully received.
I am testing peer to peer replication in our environment. I simulated a three node peer to peer topology and a local distributor.
For some wierd reason I cannot get the Log Reader Agent and snapshot agent to start. The domain account under which SQL Server Agent runs has administrator previlage on the box. I also use a domain account for SQL Server Service. (none of the passwords changed).
This is the error I am getting - "Executed as user: abc. A required privilege is not held by the client. The step failed"
Any ideas???
Also this domain account is a member of
SQLServer2005MSSQLUsers$ServerName$MSSQLSERVER
SQLServer2005MSAgentUser$ServerName$MSSQLSERVER
We restored a database with replicated tables. Now, the Log Reader Agent will not run. This displays:
"The process could not execute 'sp_repldone/sp_replcounters' on 'ourservername'."
In Error Details for the agent:
"The process could not set the last distributed transaction."
And, from the logs:
"ForwardLogBlockReadAheadAsync: Operating system error 998(Invalid access to memory location.) encountered."
Does anyone know how we get the Distribution database and the Log Reader running again?
It is only affecting Transactional replication (not snapshot or merge).
I'm trying to set up SQL 7 for replication, so I set SQLAgent to start automatically, same as SQL Server itself. SQL Server starts fine, but SQL Agent "fails to connect in a reasonable time" according to the Event log (3000 milliseconds).
Can you suggest how I go about fixing this? They both are using valid logins, so I don't know what else could be wrong.
Advice appreciated!
Arthur
Two NT accounts have been created on the server.
MSSQLSERVER
MSSQLSERVERAGENT
These accounts have been given:
a. logon rights
b. unchangeable passwords
c. passwords which never expire
d. NT admin rights
Questions:
a. Do I have to create a login account within SQL Server 7 itself for these accounts?
b. Must the properties for "this account' box on the general tab include the domain name?
c. If the answer to (b) is yes, then can I use ".MSSQLSERVERAGENT" in the "this account"
box on the general tab?
d. Does the SQL Server Agent function require the "BUILTINadministrators" login in order
to work?
Any help in figuring out why I can't get my SQL Server Agent to startup will be appreciated!!
Hi again!
I would like to thank the 2 persons which I had an answer from my previous question first. Thanks a lot !
But, it didn't quite answer my question so I'll give a bit more info.
I would like to know if I can make a batch file, that excutes or starts an active script in SQL Server Agent (that is in SQL Enterprise Manager).
If I can, can you give me more info on how to do it (command line, parameters), a web site, anything that can help me to that.
If I cannot do that, let me know please.
Thanks a lot!
I recently restored my database from a backup and it seems that something in my service broker setup has stopped working, no messages now appear.
I checked that the broker was enabled (it wasnt and i had to use NEW_BROKER because of the 'same id' message)
The database is still set to trustyworthy.
There are also no messages in sys.transmission_queue
I used profiler with all the broker events enabled and the result was as follows:
Broker:Conversation Group
Broker:Conversation STARTED_OUTBOUND
Broker:Conversation CONVERSING
Broker:Message Classify
Broker:Conversation CLOSED
Broker:Conversation Group
Broker:Message Classify
But i'm not sure whether this highlights a problem or not? Any help gratefully appreciated!!
Thanks,
Andy
Guys,
I get the error message: Queue reader aborting. The steps failed...in queue reader agents of SQL 2000 replication. Could any one give me a hint of how to troubleshoot this problem? Thanks a lot in advance.
I'm creating an app that could potentially send thousands of messages to a Service Broker queue in a matter of seconds. The stored proc that reads records off the queue will call a remote stored procedure for each message to save data in a remote database.
My question is this. How does Service Broker determine how quickly to read those messages off the queue it was sent to? Ideally I'd like Service Broker to do most of its work when SQL Server isn't busy doing other things instead of contending with SQL Server while it's doing perhaps more important work. Is there any way to control this? How does this work?
Thanks very much - Amos
I have just started getting the following error from the queue reader but I can't see why.
The Queue Reader Agent has encountered the error ''Row handle is invalid.'' when connecting to ''Database'' on ''ServerName''. Ensure that the publication and subscription are defined properly and that both servers are running.
Does anybody know what it means / how I can fix the problem?
Thanks
I am having a real problem opening a database on a SQL server through EM. The DB is on the machine as I can use EM on another machine and login from there. However, when I try to login to the DB via EM on the actual server I cannot and get an error saying 'Connection failed. Check SQL Server registration properties'.
Even if I change the reg properties it still will not let me access the database, it just keeps giving the same error.
Has anyone seen something like this before?
Hi, I have setup a replication between two servers. And sometimes due to network connection problem, I get error message like :
The subscription to publication 'pub_1' is invalid.
After 10 retries, if connection cannot be made successfully, the Merge Agent will stop running.
How can I start the Merger Agent automatically after it has been stopped?
Hi All,
I was working on some reports on SSRS. Now I cant view those reports coz I can not open report manager.
I noticed that SQLSERVER and SQL Server agent has stopped running in my local machince. But Other services are running properly (SSIS, SSRS, SSAS). When I go to SQL Configuration manager and try to run them, I get the following error massege.
" The request failled or the service did not respond in a timely fashion. Consult the event log or other applicable error logs for details. "
So now I can not connect database engine in my local machine through management studio. When I try to do that, I get the following error massage.
"An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (.Net SqlClient Data Provider)"
Also I can not access reportserver data base and reportservertemDB.
If I reinstall SQL Server again, what would happen? Would I still be able to use and view my old reports?
Please can anyone help me to get this worked again correctly?
Thanks
HELP>>> I am getting desperate
we recently had a failure which ended up wrecking my replication. The basic layout is from a source server -> Distribution Server then out to several other servers. Long story short the distribution database had to be moved to a new drive and I am now getting the following error message
The specified LSN (0003d4f0:0000721e:001b) for repldone log scan occurs before the current start of replication in the log (0003d63a:00002803:0001).
(Source: fsdpdcis (Data source); Error number: 18768)
---------------------------------------------------------------------------------------------------------------
The process could not set the last distributed transaction.
(Source: fsdpdcis-DPDDATA-1 (Agent); Error number: 22017)
I have reinitialized all subscriptions on the fsdpdcis server and run subscription validation (with no response). The data did re-load during the reinitialization but does not seem to be getting updated. This is driving me crazy and I am desperate. Any suggestions would be greatly appreciated. I have search MS knowledge base with no results and BOL has not been any help so far.
Thanks
Steve
Unable to start log reader agent after being manually stopped.
Any ideas.
I recently set up transactional replication from one server database to another server database. I keep getting a Log Reader Agent error: An access violation occurred.
The SQL Server agent starts under one Windows account but the Server is registered under the system account. The log reader agent is using the system account.
I'm not sure what else to check or what database permissions or roles should be set. Can somebody help? Thanks.
hi,
among our server-agent jobs is one for the log-reader-agent and its run status is displayed as error though the log-reader is working correctly, replication is working fine.
it had hit an error some days ago after an unexpected shutdown - but it has been auto-restarted correctly on restart of the sql-server agent.
now - what can i do to get back to a sensible run-status report?
i have already deleted the job-history with the hope that this might help - but it didn't. should i just stop and restart the job again?
can i somehow delete the status in the jobhistory?
i would gladly appreciate any ideas because it's making me just mad to have a 'failed' job status on the monitor *g*
thank you,
kerstin
Question:
I am unclear what syntat to use to stop (suspend) the log reader agent.
Things I Understand:
I understand how to manually stop the reader agent using the enterprise manager.
I understand how to schedule the load reader frequency (properties of the agent)
My Intention:
to stop the log reader agent, execute another scheduled job, then restart the log reader
Any suggestions are appreciated: comment here or send to:fglomb@crtincbc.com
Thanks!
I'm using our development ID to set up peer-to-peer replication. I am following the steps outlined in the BOL using SQL Studio 2005. When I created the initial publication, I read the section on permissions and assigned the development login ID db_owner. Indeed, to eliminate any possible issues (I thought), I gave it db_datareader, db_datawriter, and all the db admin rights and made very sure the db_denydatareader and db_denydatawriter roles were not checked. I did this through the Logins section of the Security folder and applied the same rights to both the distribution and the publication database. Nevertheless, when I run the LogReader agent job, it fails with the message for step 2 that:
Executed as user: ourdomsqldev. A required privilege is not held by the client. The step failed.
The dev ID essentially has sa rights to the server and all the databases. It is also a domain authenticated ID. Any ideas what's causing this problem? I really need to get the replication going reliably before the weekend is out.
Thanks.
Randy
I did a small package with only one ODBC connection (Merant 3.70 32-Bit Progess). This package runs well in Visual Studio and fails when runs by SQL Server Agent.
Configuration:
SQL Server Agent on a 32Bit server.
The ODBC connection configuration in available on System DSN on this server.
The user of Server Agent have full access (Admin).
Connect Manager Provider: ".Net ProvidersOdbc Data Provider"
SQL Server version: 9.0.3042
Error Message:
Executed as user: TEKCON cadmin. ...ion 9.00.3042.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 16:50:33 Error: 2007-06-11 16:50:33.62 Code: 0xC0047062 Source: Data Flow Task DataReader Source [1] Description: System.Data.Odbc.OdbcException: ERROR [HYC00] [MERANT][ODBC PROGRESS driver]Optional feature not implemented. ERROR [HY000] [MERANT][ODBC PROGRESS driver]msgOpen: unable to open message file: PROMSGS ERROR [IM006] [MERANT][ODBC PROGRESS driver]Driver's SQLSetConnectAttr failed. ERROR [HYC00] [MERANT][ODBC PROGRESS driver]Optional feature not implemented. ERROR [HY000] [MERANT][ODBC PROGRESS driver]msgOpen: unable to open message file: PROMSGS ERROR [IM006] [MERANT][ODBC PROGRESS driver]Driver's SQLSetConnectAttr failed. at System.Data.Odbc.OdbcConnection.HandleError(OdbcHandle hrHandle, RetCode retcode) at System.Data.Odbc.OdbcConnectionHandle..ctor(OdbcConnection connection, OdbcCon... The package execution fa... The step failed.
I created a .bat file with this instruction and It's run well:
dtexec /f "C:Program FilesMicrosoft SQL Server90DTSPackagesIntegration Services Project estcom.dtsx"
pause
Why it's not running with SQL Server Agent???
[I originally posted this in the General Tools forum, but perhaps I'll get better response here...]
I am wondering if this is a bug or a (strange) feature: when a SQL Server Agent job step is a CmdExec job (properly configured for owner/proxy, etc), the step is invoked with the proper user credentials (of the 'Run As' account); HOWEVER, the job step doesn't ever seem to be logged in and thus the step does not pick up the critical local group membership(s) such as BATCH (my preference) or SERVICE, etc. Provided that the command consists solely of built-ins or specifically-permissioned executable invocations (permissioned to the specific 'Run as' account), all is well. However, if the command attempts to invoke general OS exe's (cmd.exe as a sub-shell, whoami, ftp, etc -- anything that is generally permissioned via a local group such as BATCH or SERVICE), such invocations fail with access denied. Specifying a CmdExec step with 'whoami /all' as the command demonstrates the missing group memberships.
(The only workaround seems to be to either crawl through the OS exes and assign permissions, or to grant administrator membership to the proxy credentials account.)
So, design feature or major annoyance?
[Additional info I left out: SS05 (same behavior on SP2 and SP1); on WS03R2-x64; in an Active Directory domain; 'Run as' account granted log on as service, log on as batch, etc.]
Thanks,
-frank
Hi All,
We have transactional replication between two SQL Server 2000, SP4 and database is in simple recovery.
Occassionally Logreader agent fails with error 9003 (The LSN (164051:119090:22) passed to log scan in database 'ReportDB' is
invalid).
But in April 2007 this error has occurred multiple times. We have opened the case with PSS in April 2007 but till now there
is no concrete solution.
Error details in ErrorLog:
2007-04-24 16:49:09.79 spid59 Error: 9003, Severity: 20, State: 1
2007-04-24 16:49:09.79 spid59 The LSN (164051:119090:22) passed to log scan in database 'ReportDB' is invalid..
Error details in Log reader agent:
Repl Agent Status: 3
Publisher: {call sp_repldone ( 0x000280d30001d1320016, 0x000280d30001d1320016, 0, 0)}
Publisher: {call sp_replcmds (100, 0)}
Status: 0, code: 0, text: 'The process could not execute 'sp_replcmds' on 'BR14D135R17'.'.
The process could not execute 'sp_replcmds' on 'BR14D135R17'.
Repl Agent Status: 6
Status: 0, code: 9003, text: 'The LSN (164051:119090:22) passed to log scan in database 'ReportDB' is invalid.'.
From above error details it can be seen that sp_repldone is already called for LSN 164051:119090:22 (0x000280d30001d1320016)
which means it is distributed.
Since LSN is distributed, transaction log of publisher for that LSN can be truncated by checkpoint process. And afterward if
logreader issues sp_replcmds for that LSN, we will get 9003 error.
So, question is why Logreader is looking for LSN if that is already distributed.
When checked "DBCC Opentran", it also reflect oldest distributed LSN as 164051:119090:22.
We tried changing the recovery model to FULL but that has only delayed the occurrence.
Once we have noticed that LSN mentioned in Error 9003 was already backed up one day before. And we don't think replication latency to be more than 3 hrs
(maximum).
After PSS recommendation, we have applied the hotfix 2187 but error has occurred again after one month.
Other recommendation is to disable read cache of hardware controller to avoid stale read(that we are working on). Current
setting is 100% read and 0% Write.
Other Details:
SQL Server 2000 Enterprise Edition SP4 with Hotfix 2187
Window 2000 Advanced Server.
RAID 5 with array controller as HP Smart Array 641 Controller
Please let me know if you have faced such issue and have any idea on this problem.
Thanks,
Ramesh
Hi!I have Microsoft SQL Server 2005 on My Computer, but i don't have SQL Server menager. All I have is:Start > All Programs > Microsoft SQL Server 2005 > Configuration Tools > Notification Services Command Prompt > Reporting Services Configuration > SQL Server Configuration Manager > SQL Server Error and Usage Reporting > SQL Server Surface Area Configuration > SQL Server 2005 Upgrade Advisor How can I install SQL Server menager (I have CD)Thanx!!!
View 1 Replies View RelatedHello, experts!
On Sunday, as part of routine maintenance, we had to shut down our clustered servers. When we tried to bring them back up, they would not recognize our array unless we disabled the cluster service. It was agreed that we should disable the cluster service (it's caused nothing but problems due to poor implementation and vendor software support), but now we're having difficulties with SQL Server. We're having several "small" problems (i.e. unable to remove our old instance of SQL Server), but the main issue is that our client cannot connect to our server. They are able to ping us and connect to our development database (not affected by the failure), but cannot connect to the production database. Currently, the most obvious difference between production and development is that development displays a green icon (running) for both Distributed Transaction Coordinator and Full-Text Search in Support Services (Enterprise Mgr), whereas production has a red (stopped) icon for both. Also, we previously identified that MSDTC was not running and that it was inaccessible in Component Services, so we uninstalled and reinstalled. We were then able to access MSDTC in Component Services. That said, when I attempt to start DTC or Full-Text Search in Support Services, I receive the following error message:
An error 1722 - (The RPC server is unavailable) occurred while performing this service operation on the MSDTC service.
I've troubleshot this error message and verified that both RPC and DTC are started in the Services menu, that both services are set to start automatically and that both are using "Network Service" login. At this point, I have no idea what could possibly be causing this problem or if this could even be related to our client's inability to connect to our SQL database. We're running SQL Server 2000 SP4 on Win Server 2003 Dell machines. Any assistance is much appreciated.
Thanks!
Hello everyone,
Any ideas of how to start a SQL Agent job, from OTHER-THAN Enterprise Manager !!!
Does Microsoft provide any stored procs, extended procs or any SDK that can help me force-start a scheduled task ?
There has got to be a way, coz' Enterprise Manager is doing it !!!!..
Any help is greately appreciated.
Thanks..
I changed my server's service account to Domainsqladmin and the service started successfully.
I did the same for SQL Agent but the service starts and stops. In Event Viewer saw this error:
SQLServerAgent could not be started (reason: SQLServerAgent must be able to connect to SQLServer as SysAdmin, but '(Unknown)' is not a member of the SysAdmin role).
I checked Logins under under security in SSMS and the Domainsqladmin is a member of SysAdmin roles. What's wrong?
Canada DBA
I have a problem with a server where for some reason when it is rebooted the SQLAgent service does not start automatically. You have to go into control panel, services and start it, even the it is set to Automatic.
Thanking in advance for any ideas??
hi
when i try to start sql agent hang then mmc
i look the log and the problem is the mail profile
i try remove it from the property of sql agent but this hang the mmc too
can i remove this with tsql?
thanks
In attempt to run the SQLServer Job Agent, the following error occurs:
An error 1068 (the dependency service or group failed to start) occured while performing this service opertion on the SQLServer Agent Service.
An user a/c with Administrator rights is assigned to the SQLServer Agent Service upon setup.
Any idea what is causing it?
Thanks in advance,
Ben
Hi guys,
I'm trying to set up merge replication between a SQL Server 2000 SP4 / Win2k box and a MSDE SP4/WinXP box and I'm finding that the initial snapshot isn't being produced.
The SQL Agent runs as a windows user that has admin privileges, the snapshot agent impersonates the SQL Agent. The SQL Server login for the agent account has the server role "System Administrators" and database access to all db's.
When I turn on logging and try to start the agent, the following is written to the log:
Microsoft SQL Server Snapshot Agent 8.00.760
Copyright (c) 2000 Microsoft Corporation
Microsoft SQL Server Replication Agent: SVRName-POS-POS_Test_Suburb-1
Connecting to Distributor 'SVRName'
SourceTypeId = 5
SourceName = SVRName
ErrorCode = 18456
ErrorText = Login failed for user 'SVRNameSQLAgent'.
The process could not connect to Distributor 'SVRName'.
Most of the posts I've seen regarding problems like this are due to subscriber authentication issues (not up to that, this is the initial snapshot) or windows/domain user permissions.
Any ideas what else it might be?
Hi,
I have installed the MSDE and use mixed mode authenticaton.
The SQL Server Agent will not start due to login failures.
Normally, I would use the Enterprise Manager Managment wizard to
correct the System Account and Connection Credentials.
Can anyone tell me how to achieve this using OSQL?
Thanks