Shawn, Start the server in a startup debug mode. That way you would be able to see more finer logs a startup log file that will be created in the server directory..
To do this you need to add the flag –d to the AR Server startup line in the armonitor.cfg file. Hopefully you’ll have more on there.. Joe From: Pierson, Shawn Sent: Monday, June 20, 2011 5:14 PM Newsgroups: public.remedy.arsystem.general To: [email protected] Subject: Weird issue with ARS 7.5 ** Good afternoon, Our disaster recovery location recently changed, and as a result our backup servers were all moved. As I tested ARS to see if it is working correctly after the move, AR System would not start correctly. In the arerror.log everything looked fine, it gave the normal startup message, but then suddenly died with no error message appearing there. However, when I look in Event Viewer I see the message, “AR System Server unable to create (390600, 0) for TCP.” I’ve tried comparing everything I can to the production box this mirrors and it seems all correct, nothing has changed as far as I can tell software-wise. I looked for hard drive problems, and I compared the database to my production database and the settings are identical. If anyone has any suggestions, I would greatly appreciate it. I am on ARS 7.5 p4, Windows Server 2003, SQL Server 2005. Thanks, Shawn Pierson Remedy Developer | Southern Union _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
