.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Top 5 Contributors of the Month
Gaurav Pal
Post New Web Links

Log Reader Agent fails to restart when server restarts

Posted By:      Posted Date: September 24, 2010    Points: 0   Category :Sql Server

when our server reboots and by way of that, SQL Server restarts, the Log Reader Agent fails to restart despite appearing to be set to do so (restart when SQL Server Agent starts).  SQL Server Agent does restart, but the LRA needs manual intervention.



View Complete Post

More Related Resource Links

SQL Server Express 2008 Setup fails. Support Rule "Restart Computer" Failed

Hi, I have been trying to install SQL Server Express for most of the day now without any luck.  Whatever I do setup fails at the stage of Setup Support Rules, Rule "Restart Computer" - Failed.  Needles to say I have restarted (several times!) and I have tried downloading  and installing the "Advanced", "Tools" and "Basic" versions, all give the same error.  Trying a repair does the same.  I have been searching the net for an answer without success, any help would be MUCH appreciated. Further info: I am trying to install a stand-alone installation on to a single PC running under XP SP 3 with .NET 3.5 SP1 installed.  The PC did have some earler versions of SQL server installed but I (?hopefully?) removed all of these through Control Panel.  Before trying the first SQL install I installed Windows installer 4.5 and PowerShell 1.0 as per the Microsoft Instructions. Running SQL Server Configuration Manager results in an error (MMC could not create the snap-in. The snap in might not have been installed correctly).  A directory structure for SQL server exists in "Program Files".  Services MSC shows SQL Server (SQLEXPRESS) as Automatic Statup (not running).  Trying to start this manually gives error 14001: "application configuration incorrect - re-install to fix" .......... Which is precisely what I'm trying to do.........:(

SQL Server 2008 Agent Fails to start in a Win 2008 Cluster

When I try to bring SQLAGENT Online, I get the following errors: EventID:53 [sqagtres] StartResourceService: Failed to start SQLSERVERAGENT service.  CurrentState: 1 [sqagtres] OnlineThread: ResUtilsStartResourceService failed (status 435) [sqagtres] OnlineThread: Error 435 bringing resource online.   I just did a fresh SQL Cluster install as well.  When I installed the cluster, the service account was good to go.  I cant figure out what is going on.  SQL Server Engine starts fine.  Any ideas?

SSIS package fails under SQL Server Agent job


Hi All

I have designed a SSIS package to encrypt a file using Cipher (EFS) it works fine from BIDS & Package Execution Utility.

But SQL Server Agent job is failing to do this. I am getting the error as

" In executing C:\Windows\System32\Cipher.exe /e /a C:\Test.txt at "",The Process Exit code was 1 while the expected was 0." 


Please help me.




SSIS package which reads excel files fails on SQL Server Agent



I have a SSIS package which reads an excel file and loads data into a table using script component(C#) as a source. The package runs without any errors when I manually run it on my machine and on the server. But the package fails when run as a SQL Server Agent job.

I tried all the possible fixes I found on the web but still can't get it to work.

Could you shed some light on it?



Restart SQL Server Agent on Distributor

Can we Restart  SQL Server Agent on Distributor during the transactional replication?
Will the replication pick it up once the SQL Servernt agent service is brought up?

SQL Server Agent: Job fails when all steps complete successfully


I have a SQL Server 2005 database with a job which contains several steps.  Each of these steps completes without issue but the overall job fails.  I believe this has to do with a NULL value generating a warning so I set SET ANSI_WARNINGS OFF; on the step I thought was generating the warning but the job still fails as a whole.

How can I either get the job as a whole to ignore warnings OR determine what is the root cause of this issue.  I don't see anything in the error logs.

sql server agent - job schedule 22022 error


Hi ! I have scheduled a job in sql server 2008 to send birthday e-mails. I run the script and it looks wroking but in agent schedule it doesn't. I am getting the below error; what is the problem?

TITLE: Microsoft.SqlServer.Smo
Start failed for Job 'Sending_transferdb_birthdate_e-mails'. 
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=10.50.1447.4+((KJ_RTM).100213-0103+)&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Start+Job&Link

Error while executing a package through SQL Server Agent

Hi All,   I have a ssis package. It has 3 tasks, first task updates a record in Oracle database to set an Indicator to “Y”, second task process SSAS Cube and the third again updates the same record and sets the indicator to “N”. This package has 2 data sources, one is Oracle and the other is Analysis Services. I gave the credentials for the Oracle and use NT Authority for Analysis services.   When I am executing from BIDS package is executing successfully. But when I am calling the job to execute this package its throwing me the error. Below is the error.     Message Executed as user: User\Username. ...ion 9.00.4035.00 for 64-bit  Copyright (C) Microsoft Corp 1984-2005. All rights reserved.    Started:  10:57:46 AM  Error: 2010-08-27 10:57:46.79     Code: 0xC0016016     Source:       Description: Failed to decrypt protected XML node "DTS:Password" with error 0x8009000B "Key not valid for use in specified state.". You may not be authorized to access this information. This error occurs when there is a cryptographic error. Verify that the correct key is available.  End Error  Error: 2010-08-27 10:57:47.16     Code: 0xC0202009     Source: Ord_test Connection manager &q

sql server agent roles and permissions

hi does any one have idea of what kind of roles are needed for creating a SQL server agent job and why those roles are needed?? Please Reply ASAP Because i don't have sysadmin rights.........so that other developers can use the same login for creating the jobs Thanks in advance

Error starting SQL Server Agent - Could not load the DLL xpstar90.dll. Reason: 126

AD Service account password was changed.  Now the SQL Server Agent (MSSQLSERVER) will not start even after updating the password.  Have no access into the databases.  Log files say "Could not load the DLL xpstar90.dll, or one of the DLLs it references. Reason: 126(The specified module could not be found.)."  Service Account has Full rights on system.  Any help in solving the problem would be great.

SQL Server 2008 installation fails There was an error generating the XML document. Error code 0x84B

My system config: window XP - SP3 4 GB RAM, I have VS2008 with SP1, VS2010 Ultimate installed First when I tried to install SQL 2008 R2 Dev edition I got an error saying vs2008 SP1 was not installed, infact I had the SP1 installed in my m/c.  I did reinstalled the SP1 and tried to install SQL again. while in the final installation process I got the error  "Setup has encountered the following error: There was an error generating the XML document. Error code 0x84B10001." I uninstall the SQL server again to remove the files which were created from Unsuccessful installation I removed the register entry as suggested by this forum. reinstalled but no chance, I have tried all the option which I can get know in web. Please help me. here is the log files details  Exception type: Microsoft.SqlServer.Chainer.Infrastructure.ChainerInfrastructureException 2010-08-26 14:54:53 Slp:     Message: 2010-08-26 14:54:53 Slp:         There was an error generating the XML document. 2010-08-26 14:54:53 Slp:     Stack: 2010-08-26 14:54:53 Slp:         at Microsoft.SqlServer.Chainer.Infrastructure.DataStoreService.SerializeObject(String rootPath, Object objectToSerialize, Boolean saveToCache) 2010-08-26 14:54:53 Slp:   &nb

SQL Server 2008 R2 fails after Windows XP Pro SP3 install

We recently encountered an issue with SQL Server 2008 R2 failing to run after the upgrade from Windows XP Pro SP2 to SP3. This was tested and reproduced (with varying results) on more than one computer. Steps to reproduce this. On a Windows XP Pro machine with Service Pack 2 installed, install SQL Server 2008 R2. Next upgrade Windows to Service Pack 3. Now upon opening SSMS or trying to start the SQL server service you receive the following message: "This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem". In some instances reinstalling/repairing SQL Server 2008 R2 does fix the issue.  In other cases the installer crashes and you need to use msizap to clean it up before you can reinstall.  In other cases you do not receive any errors at all. After testing in multiple virtual machines it looks like the cleaner the Windows install the more likely you are to run into this issue.  On machines with most or all windows updates (prior to SP3) installed you do not necessarily even get the failure.  On machines with just Windows XP Pro SP2 installed with no additional updates you get the failure every time. Obviously the SQL Server 2008 R2 prerequisites are installed in all cases in order to be able to install SQL server to begin with. Any help with this would be appre

Install on New Windows7 - Getting Invalid SQL Server Agent credentials

Hi: I have a Developer License for MSSQL Server 2008.  Have just upgraded to Windows 7 Professional Edition.  When installing MS SQL Server, the setup shows that I have an instance of SQL Server Express already installed.  I am given a choice between Default Instance and Named Instance.  First time I chose named instance and then used the name of my machine - RBS1.  I received the following message:  The credentials you provided for the SQL Server Agent service are invalid. To continue, provide a valid account and password for the SQL Server Agent service. Went back and tried Default instance and got same answer.  Can't proceed to install.  Any help in this greatly appreciated. roger  

Connection to SQL server 2008 fails randomly

I'm sure a lot of you have seen this error: "A network-related or instance-specific error occurred while establishing a connection to SQL Server" Normally I would assume that this would mean that there's a problem connecting to the SQL server, but currently I'm having a hard time figuring out what the problem is and how to fix it The problem only occours randomly, but mostly it is when I from the same computer calls the server several times for example like this: For i as integer = 0 to 500 OpenConnectionToSqlServer(Bla bla) ReadData() CloseConnection() next I always makes sure to close the connection again. The more often I connect to SQL server in a row, the higher is the percentage of errors I have created my code so that if the above error happens, the program will wait for a second, then try again (after 3rd try it will stop trying)   I have several times been monitoring the SQL server at the same time, but I can't seem to see anything from there :(

Force SQL job to succeed even after a step fails in SQL server 2008

All, We are trying to force some jobs to succed even though one step in the job fails randomly. Now,we choose the property of the job succeed on failure, it still shows up as warning. How do we ignore the warning thrown by the job SQL job?? Any suggestions??   Thanks Kay

SQL Agent - service account permissions - SQL Server 2008

Hi @ all   I installed two SQL Server 2008 on Server 2008 R2 Std (principal and mirror) and an AD Server 2008, with sperate service accounts, connect as SA, localy all works fine. I created some agent tasks (PowerShell, T-SQL), but I get some Error massages in the history, that service account of SQL Agent didn't have the permission to query a remote machine(access denied for wmi (HRESULT: 0x80070005 (E_ACCESSDENIED)) and linked database(SQLSTATE 42000 Error(7314)). The simple query with SA permissions on the remote machine works and the powershell scripts with the local domain user works too. But not with the SQL Agent. WHY?? Where ist the different between the user account permisions and service account permissions? Which settings are needed? Example: get-wmiobject -class win32_service -computername 192.168.xxx.xxx| where {$_.name -like '*SQL*'} Powershell Console: works                                     SQL Agent Job: access denied I tried some solutions with user rights, group policies and security permissions but nothing works. like: Configuration -Service Accounts, SQL Server or SQL Server Agent service account http://support.microsoft.com/kb/283811/en-us http://msdn2.microsoft.com/

Sql Server Job Agent vs Web Services

I've been tasked with coming up with a way to query our RS6000 and using the results to update records in the SQL Server 2005 db. Our RS6000 vendor has created an xml query which we call from an url. We query a table, loop through the results and call the xml query for each record. Then we check for a certain status in the xml results and, if we find it, update the db record. My question is which route would be better; building a web service in .Net or running a vb script from the SQL Server Agent? I normally do such things from a Web Service or an .exe setup under scheduled tasks on the server, but someone suggested SQL job agent route and I was wondering which would be more effiecient?Thanks in advance.
ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend