No problem Shrestha, I hop you don't' have any more problems. Are you running what version is your OS on your server, and the SQL Server version?
I definitely think that Microsoft has introduced a bug, since either the OS is saying that SQL Server is up before it really is, or SQL server is reporting it's up before it really is. Either way, they are both Microsoft products. It is strange, though, that remedy cannot recover, since SQL server does eventually come up, but remedy still continues to fail at connecting. Thanks, Gary Opela, Jr., RSP Remedy Engineer Leader Communications, Inc. http://www.5pointleader.com http://www.lcibest.com Best Product, Best People, Best PriceTM An ISO 9001:2000 Certified, CMMI(r) Level 3 Rated Company ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Shrestha, Manjari R. Sent: Tuesday, July 29, 2008 5:22 AM To: [email protected] Subject: Re: After server reboot the status of the Remedy service is started, but it has to be restarted in order to login to Remedy(SOLVED) Thank you Gary and Danny, I followed Gary's advice and it has solved my issue. Thanks! Manjari R. Shrestha Junior Programmer Analyst ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Gary Opela (Corporate) Sent: Monday, July 28, 2008 11:41 AM To: [email protected] Subject: Re: After server reboot the status of the Remedy service is started, but it has to be restarted in order to login to Remedy I have had this problem, and noticed that, according to the remedy logs, that remedy was unable to talk to sql server. I realized then that windows was saying sql server was up before it really was ready to receive connections. I also noticed that sql server agent had a dependency of sql server, and that sql server agent took around 10 - 30 seconds to come up. So, I set sql server agent as a dependency for remedy instead of setting sql server. This seemed to fix the problem, because it gave sql server another 10+ seconds to come up before remedy tried to connect. There is a registry key that you can use to set this up, it is as follows: HKEY_LOCAL_MACHINE SYSTEM CURRENTCONTROLSET SERVICES BMC ACTION REQUEST SYSTEM SERVER DEPENDONSERVICE SQLSERVERAGENT Thanks, Gary Opela, Jr., RSP Remedy Engineer Leader Communications, Inc. http://www.5pointleader.com http://www.lcibest.com Best Product, Best People, Best PriceTM An ISO 9001:2000 Certified, CMMI(r) Level 3 Rated Company ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Shrestha, Manjari R. Sent: Monday, July 28, 2008 10:23 AM To: [email protected] Subject: After server reboot the status of the Remedy service is started, but it has to be restarted in order to login to Remedy Hello, After upgrading Remedy to 7.1, when I reboot the server it takes almost half an hour for the server to come up and the status of Remedy service is started but I have to restart the service manually again for users to be able to login, any idea why this would happen? Thanks in advance. Windows 2003 ARS version 7.1 SQL 2005 Manjari R. Shrestha __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html_____Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
