Are you able to ask for the list of privileges/permissions that have been granted to the resource account - both for Windows and SQL? Considering 7.6p5 and 8.1 are both giving you grief, there is most likely something missing.
For SQL these are the steps I use when having to manually create the user or datafile. Perhaps your DBAs will check if the resource account has the role and privileges attached. 1. In a SQL*Plus window, create the tablespace. For example: create tablespace *arsys* datafile '/path/arsys.dbf' size 500M reuse; 2. Create a user. For example: create user *aradmin* identified by *AR#Admin#* default tablespace *arsys*temporary tablespace temp quota unlimited on *arsys*; 3. Create a role for the user you created in step 2 above. For example: create role *ARole_arsys* not identified; 4. Set the privileges for the role. For example: grant alter session, create cluster, create database link, create sequence, create session, create synonym, create table, create view, create procedure, create trigger, query rewrite to *ARole_arsys*; 5. Grant the role to the user. For example: grant *ARole_arsys* to *aradmin*; A long time ago, I remember seeing 5 things that a non-administrator account had to have for Windows. I'll see if I can find that. Or maybe if someone else has it, they can chime in. I remember it specifically had to do with running the ARServer service with a user account or domain account that was not the administrator. Is the installation completing though? This KB is older, KA289521, but I wonder if your DB objects need to have dbo ownership applied... Janie On Fri, Nov 1, 2013 at 6:23 AM, Reiser, John J <[email protected]>wrote: > ** > > Shawn,**** > > We are required to use what we call a resource account and it must be a > windows authenticated account. Local SQL accounts are read only.**** > > ** ** > > Thank you,**** > > --- > John J. Reiser > Remedy Developer/Administrator **** > > Senior Software Development Analyst > Lockheed Martin - MS2 > The star that burns twice as bright burns half as long. > Pay close attention and be illuminated by its brilliance. - paraphrased by > me **** > > ** ** > > *From:* Action Request System discussion list(ARSList) [mailto: > [email protected]] *On Behalf Of *Pierson, Shawn > *Sent:* Friday, November 01, 2013 9:20 AM > *To:* [email protected] > *Subject:* Re: EXTERNAL: Re: Installation problems with ARS 8.1.00**** > > ** ** > > ** **** > > I haven’t sorted through all the emails, but have you tried using the > default ARAdmin SQL Server account instead of the domain account?**** > > ** ** > > Thanks,**** > > * * > > *Shawn Pierson * > > Remedy Developer | Energy Transfer**** > > ** ** > > *From:* Action Request System discussion list(ARSList) [ > mailto:[email protected] <[email protected]>] *On Behalf Of *Reiser, > John J > *Sent:* Friday, November 01, 2013 8:05 AM > *To:* [email protected] > *Subject:* Re: EXTERNAL: Re: Installation problems with ARS 8.1.00**** > > ** ** > > ** **** > > Janie,**** > > Thanks for the reply. I’ve also had no luck installing a clean ARS7.6.04 > SP5 as directed by BMC Support.**** > > The installer runs very quickly until it comes to the part about starting > the services. Then it hangs for 20 -30 minutes and ends with a failure.*** > * > > Always the same message in the logs; ARSystem did not start in a timely > fashion. **** > > ** ** > > I download and unzip the install suite to the VM. The SQL Server DB is on > a SAN that is required even for development databases. **** > > I am only installing the ARSystem Server. This is a non-ITSM system. I > don’t even install Approval or Assignment servers.**** > > ** ** > > I seem to remember something about using a local admin account instead of > being a member of the Administrators group but I can’t find anything that > differentiates the two in the documentation.**** > > ** ** > > Thank you,**** > > --- > John J. Reiser > Remedy Developer/Administrator **** > > Senior Software Development Analyst > Lockheed Martin - MS2 > The star that burns twice as bright burns half as long. > Pay close attention and be illuminated by its brilliance. - paraphrased by > me **** > > ** ** > > *From:* Action Request System discussion list(ARSList) [ > mailto:[email protected] <[email protected]>] *On Behalf Of *Janie > Sprenger > *Sent:* Thursday, October 31, 2013 7:52 PM > *To:* [email protected] > *Subject:* EXTERNAL: Re: Installation problems with ARS 8.1.00**** > > ** ** > > ** **** > > Hi John, **** > > **** > > I had a really hard time completing the upgrades from 7604. Everything > had to be patched to 7604 SP4 first. That wasn't really hard. The main > trouble was that we also ran into an issue because the system that I was > upgrading had a failed RKM installation in 7604 that I didn't know about. > That failed install caused problems in the upgrade, we manually redid the > ITSM installation about 3 times, fixing problems as we went and then > resetting the installer and temp folder, etc. Ultimately it installed > successfully; however, once we really started reviewing the apps, we had > more problems with RKM than we could deal with and ultimately opted to > build a new 8.1 environment and port the customizations and data. **** > > **** > > My experience with installing 8.1 was on Windows 2012/SQL 2012 with a > Windows administrator account. Both are VMs on the same physical host and > SQL was a local account. To be honest, the clean installs were super easy > and fast. I made sure any hardware pre-req that I could think of was met. > There was plenty of disk space and memory for the servers. **** > > **** > > One thing I have noticed is that the Core and ITSM installers need quite a > large amount of disk space to unpack everything. While the ultimate > product isn't insane for disk space, the installation temporarily uses a > lot of disk space. **** > > **** > > Another item I've noticed with the installers also prior to 8.1 is that > SQL databases that have transaction logging on will take longer for the > installer to run because it's of course logging all of those changes. *** > * > > **** > > **** > > I would lean towards looking at where that DB is running, if it's in a > shared SQL environment and there isn't enough juice to run, the install > will just dog. I had that happen once, turns out that SQL admin had > something like 2GB ram allocated to the db, I talked them into jumping it > up to 12gb (since it was shared) and the install completed. **** > > **** > > The other thing to investigate is network latency as I'm sure you know. * > *** > > **** > > Oh, and are you doing any of the installs with the installers on shared > drives? The installers on shared drives tend to be a problem.**** > > **** > > **** > > HTH**** > > Janie**** > > ** ** > > On Thu, Oct 31, 2013 at 2:56 PM, Reiser, John J <[email protected]> > wrote:**** > > ** **** > > Hello Listers,**** > > ARS 8.1.00**** > > MS SQL Server 2008 R2 (remote)**** > > OS Windows Enterprise 2003**** > > **** > > I am having the worst time trying to get a bare bones Remedy ARSystem > server installed.**** > > I have admin rights for the user running the setup.exe file. That windows > user also is the db_owner of the ARSystem_test database which was created > during the installation process.**** > > It takes forever to complete, the starting services time is the longest. > When it does complete the install is flagged as failed because the ARSystem > would not start in a “timely fashion”.**** > > I have a ticket open with BMC Support and they have given me some things > to check that was pulled out of the installation logs.**** > > The settings that they questioned were supposedly confirmed by the DBA but > all I can tell is that the MS SQL Server DB is “owned” by the windows > account.**** > > **** > > Because of all of these oddities I dare not touch my production system > (7.6.03) or my sandbox (7.6.04 SP3) for fear of breaking them too. They > were upgraded from earlier versions and have a legacy sql account as the > owner but the services run on the ARS machine with the same domain account > as the one I’m using for the test.**** > > **** > > System policy does not allow for giving the sa account out and local SQL > accounts are discouraged so I am using a windows domain account to run the > install, own the DB and run the services on the ARSystem server machine.** > ** > > **** > > Has anyone seen any gotchas like file system permission restrictions on a > windows server or some other idiosyncrasy that could prevent the > installation from completing successfully?**** > > **** > > **** > > Thank you,**** > > --- > John J. Reiser > Remedy Developer/Administrator **** > > Senior Software Development Analyst > Lockheed Martin - MS2 > The star that burns twice as bright burns half as long. > Pay close attention and be illuminated by its brilliance. - paraphrased by > me **** > > **** > > **** > > **** > > _ARSlist: "Where the Answers Are" and have been for 20 years_ **** > > ** ** > > _ARSlist: "Where the Answers Are" and have been for 20 years_ **** > > _ARSlist: "Where the Answers Are" and have been for 20 years_ **** > > Private and confidential as detailed > here<http://www.energytransfer.com/mail_disclaimer.aspx>. > If you cannot access hyperlink, please e-mail sender. **** > > _ARSlist: "Where the Answers Are" and have been for 20 years_ **** > _ARSlist: "Where the Answers Are" and have been for 20 years_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
