This is a completely standalone server with no contention issues. I and Remedy are the only users of the database.
Rick On Oct 7, 2010 2:53 PM, "Joe Martin D'Souza" <[email protected]> wrote: > Rick, > > You mean you cannot log into your SQL Server 2008 Management Studio itself? What error do you get? Unavailable connections? > > Maybe that is the problem where your SQL admins have limited the number of SQL connections to the database for security reasons.. > > If that is the case, you will need to shut down all applications that use the SQL server, so that you free up connections, and raise the user connections limit. This is done through the stored proceedure sp_configure. There are several parameters you can set using that, one of which is Advanced Options, and when you set Advanced Options to 1, you will see additional options, one of them being User Connections.. > > Hope this helps... > > Joe > > > > > From: Rick Cook > Sent: Thursday, October 07, 2010 2:46 PM > Newsgroups: public.remedy.arsystem.general > To: [email protected] > Subject: Re: CMDB 7.6.03 installation error > > > ** Well, I can't test that step, because the install process appears to have removed my ability to even log into SQL Server 2008 Management Studio by any means. I'll try a reboot and see if that helps... > > Rick > > > On Thu, Oct 7, 2010 at 2:41 PM, Joe Martin D'Souza <[email protected]> wrote: > > ** > How about when you create the database for it, with pre-allocated data and log files.. Does it go past the database creation step? > > I do agree some of the install scripts off late haven't been the best we have seen or have been used to seeing.. > > Joe > > > > > From: Rick Cook > Sent: Thursday, October 07, 2010 2:34 PM > Newsgroups: public.remedy.arsystem.general > To: [email protected] > Subject: Re: CMDB 7.6.03 installation error > > > ** Anyone who got past the AR System installation has my envy. I have taken the easiest paths possible, and still it fails because the DB user name that the install script allegedly validated doesn't have permission to create a new database from 'master'. > > > Why can't BMC understand that when you make install scripts basically uneditable that they have to be *Bulletproof*? These don't even appear to have been sufficiently tested to be reliable. > > Are we at patch 1 yet? (sigh) > > Rick > > > On Thu, Oct 7, 2010 at 11:35 AM, strauss <[email protected]> wrote: > > Make sure that you are logged in during the installation with an account (preferably a domain account, based on the preconfigured stack installer notes) that is in the local Administrators group, and has explicit permissions to the directories that you are installing in. Windows Server 2008 R2 is like Windows 7 (and Windows 2008 like Vista), notorious for having problems with permissions where the logged in account can have no ability to write files or update the registry when an installer running under that account needs to do that. Some people report having to run the installer as an admin (right-click Run as administrator) but that just means that you may have permission problems later, after the install, and changing something in an AR Form may fail to update a cfg file unless the AR Server service account has permission to write to the file system. > > > > On my two 7.6.03 systems upgraded from 7.5.00.006 (and the third one that is actually upgrading Atrium Core as I write), there are four copies of the arimportcmd.exe present (different dates but all 2010). This is on BOTH Windows Server 2003 x64 and Windows Server 2008 R2 x64. > > D:\Program Files (x86)\BMC Software\ARSystem\ arimportcmd.exe > > D:\Program Files (x86)\BMC Software\ARSystem\approval\bin\ arimportcmd.exe > > D:\Program Files (x86)\BMC Software\BMC Service Level Management\rik\ arimportcmd.exe > > D:\Program Files (x86)\BMC Software\BMC Service Level Management\rik\upgrade\ arimportcmd.exe > > > > Other problems with the Atrium Core installer: > > On any OS – the Atrium Core installer has problems with existing records from 7.6.00 in the AIS:Global Preferences form > > On the one I am doing this morning, there were already three entries in the form from previous installs, the first with the server short name (alias), then two more with the server FQDN, all for port 1825 and ais. The installer refused to run until I removed the one with short name so that the FIRST record in the form was one with the FQDN. On my 2008 R2 server on a weird VMware host, I had to add the IP address instead of the server name when patching Atrium 7.6.00.001 to 002, then had to add the short name (alias) when I upgraded to 7.6.03. Basically, whatever the installer says it wants to see (short name, FQDN, IP address) in the AIS:Global Preferences form, you have to make the FIRST entry in that form match the value indicated, or it won’t run. Apparently it has some sort of problem resolving the name of the server that it is running on, and you have to provide whatever it has picked in the data. Only one of the three servers I have upgraded from 7.5/7.6 (on 2003) has NOT hung up on the values in the AIS:Global Preferences form. > > > > On 2008 R2 but not 2003 server(s) > > On a system where the 32-bit ARS 7.5 has been upgraded to 64-bit ARS 7.6.03, the Atrium Core installer is unable to restart the AR Server services properly and the installation hangs. > > Had to manually kill the process (kill the 32-bit ones too) in Task Manager then restart the service before the Atrium installer could go on > > The Atrium Core installer restarts the AR Server as many as 4 times during an upgrade! > > This is on a VM, and is NOT in a domain due to being on a weird private network, and had issues when installing 7.5 / 7.6, so this problem may be isolated to this machine; it’s the only 2008 host I have left – I put my other 2008 servers all back on 2003 because of all the permissions issues that kept cropping up. > > > > The Atrium Core 7.6.03 upgrade on my pre-production 2003 server just completed successfully, so it’s time to go look at the logs. > > > > Christopher Strauss, Ph.D. > Call Tracking Administration Manager > University of North Texas Computing & IT Center > http://itsm.unt.edu/ > > From: Action Request System discussion list(ARSList) [mailto: [email protected]] On Behalf Of Mahendra Mahalkar > Sent: Thursday, October 07, 2010 9:04 AM > To: [email protected] > Subject: CMDB 7.6.03 installation error > > > > ** > > Hi All, > > I installed ARS 7.6.03 successfully on Windows 2008 64 bit, MS SQL 2005, but CMDB 7.6.03 installation is failed with rpc program not registered (ARERR 90) in arerror.log, whenever the installer tries to import BMC%CMDB.def from workflow directory through rik command, this error is ocurring. If I run this command through command prompt it import the def properly but throws an error of not finding arimportcmd.exe. Where should I find this arimportcmd.exe? So all arx import are failing at that time. Again I import all the arx files through Dataimport tool except cmdbroles-uid.arx as it throws an error of required field (Application Name)could not be null. What should be correct application name ? Also does anyone know any regisrty creation at the time of Atrium Core installation? The same above happening for AIE installation also. Need help. > > > > Mahendra > > _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_ > > _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_ > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
