Remember each thread defined (Fast, List, and Private) is a connection to the database.
If you only have defined Fast (min 5, max 15); List (min 5, max 15) then you are using more than 10 at the initial startup. You would be using at least: Admin (1), Alert (1), Escalation (1), Fast (5), List (5) There are probably others that I can't think of off hand. Fred -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of brooksm Sent: Wednesday, December 12, 2007 10:04 PM To: [email protected] Subject: Re: Cannot log in to Remedy after Windows Server SP2 Install This has been resolved! First of all, a big thanks to Dane Huish and Juan at Denali Advanced Integration. They saved may bacon. If you ever need Remedy consulting work, these guys are top notch and don't screw around. As usual Remedy tech support hasn't even replied eventhough I submitted my request as critical. I'm sure they will get around to calling me by the end of the week. It seems like nowadays it takes a couple days just to get the email notification after ticket submission. Very sad. So, here's what went down. I upgraded to Windows Server SP2 and during the normal reboot, my server hung, so I manually shut the server down and rebooted. No one could log in, including via the Admin tool. Turns out that after the SP2 upgrade, the SQL Server connections were reduced to 10. Well it looks like ARadmin immediately ties up all 10 upon starting the AR Server process. We couldn't really verify whether this was typical behavior or not. Can someone confirm? All we ended up doing was increasing the # of allowed connections to unlimited (0). Thanks again, Dane an Juan! Brooks strauss wrote: > > Sp2 for Windows 2003 (could affect the firewall) or Sp2 for SQL Server > 2005 (could affect the surface area configuration)? > > Christopher Strauss, Ph.D. > Call Tracking Administration Manager > University of North Texas Computing & IT Center http://itsm.unt.edu/ > >> -----Original Message----- >> From: Action Request System discussion list(ARSList) >> [mailto:[EMAIL PROTECTED] On Behalf Of brooksm >> Sent: Wednesday, December 12, 2007 6:25 PM >> To: [email protected] >> Subject: Cannot log in to Remedy after Windows Server SP2 Install >> >> Help!!! >> I just updated my ARS 7.0 on Windows 2003 SQL Server 2005 system to >> SP2. >> Now, after rebooting the system, I cannot login to the system. >> >> Cannot login to remedy1 as a preference server. >> >> user: brooks, server: remedy1 >> >> >> Unable to successfully log in to any server. >> >> >> I'm sure it's an easy fix, but I have no idea how to fix this. I'm >> not able to log into the Admin tool either. >> >> >> Help!!! >> >> -- >> View this message in context: >> http://www.nabble.com/Cannot-log-in-to-Remedy-after-Windows-Se > rver-SP2-Install-tp14307282p14307282.html >> Sent from the ARS (Action Request System) mailing list archive at >> Nabble.com. >> >> ______________________________________________________________ >> _________________ >> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum >> Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" >> >> > > ______________________________________________________________________ > _________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" > > -- View this message in context: http://www.nabble.com/Cannot-log-in-to-Remedy-after-Windows-Server-SP2-I nstall-tp14307282p14309577.html Sent from the ARS (Action Request System) mailing list archive at Nabble.com. ________________________________________________________________________ _______ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
