Author: Elliot Bonilla
CATEGORY: Tutorials
September 5, 2019

Was Your Maximo Installed By Another User? Here’s How I Solved That “Issue”

Author: Elliot Bonilla
CATEGORY: Tutorials
September 5, 2019

Was Your Maximo Installed By Another User? Here’s How I Solved That “Issue”

You may notice that this article is shorter than usual– but that’s OK. When you run into a problem, all you want is another idea to try to resolve your issue. So, let’s cut to the chase.

Not sure how many people have been in this situation, but back in my day, there were multiple cooks in the kitchen making the Maximo pie – installing, patching, and configuring. We all logged into the system with our own individual accounts and we got the job done.

The catch here was that many times, when we tried to install a Fix Pack, Feature Pack, or Interim Fix, we ran into an error similar to this one:

“No current installation was found at the requested location. Initiating a base installation of Maximo Asset Management”

And to be honest, I ran into it more than once. Even though best practices recommend you install enterprise applications using administrative accounts rather than individual accounts, at this particular site, that was not an option.

So, when Maximo was installed by one of my colleagues, a parameter called Maximo.InstallUser was written to the Install.Properties file. Then, when I tried to patch Maximo, I got the error mentioned above, due to the mismatch of the user.

As always, there’s a solution for almost every problem you encounter and this what we did to fix it.

Look for the Maximo Install.Properties file. It has a default location of C:\IBM\SMP\etc\install.properties

Maximo CMMS Installed Properties File

In that file, you will find the Property Maximo.InstallUser.

Here it is in Maximo 7.6

IBM Maximo 7.6 CMMS Install User

And for those of you on Maximo 7.5, here’s how it looks:

Maximo IBM CMMS 7.5

It is as simple as updating the entry in the file to the correct user that will be installing the Fix Pack, Feature Pack, or Interim Fix, and re-running the installation process.

Now, this was enough to fix the issue every time I encountered it, but this might not always work, and you will be asking yourself, “Why?”. Well, in some cases, the Installer also writes a property to the maxpropvalue table, and this property also needs to be updated to match the correct user.

To find this property, use the script below:

select  propname, propvalue from  maxpropvalue where  propname =  ‘Maximo.InstallUser’

And since I already gave you the script to find your record, I’ll give you the script to update it too.

update maxpropvalue set propvalue=<correct_user> where propname =  ‘Maximo.InstallUser’

Like I mentioned before, this was a short article, but I hope that it helps somebody in their Maximo quest.

Latest Resources

Similar Posts

Offices
Headquarters - Raleigh, NC
4601 Six Forks Rd Ste 220
Raleigh, NC 27609
Phone: +1 (888) 317-2397
San Antonio, TX
18880 Stone Oak Pkwy
San Antonio, TX 78258
Phone: (210)-201-8189
Gateshead, UK
Baltic Place, S Shore Rd. Gateshead
NE8 3AE, United Kingdom
Phone: +44 191 201 7777
Leeds, UK
1 York Pl, Leeds
LS1 2DR, United Kingdom
Phone: +44 113 827 0080
Melbourne, AU
16 Kirk St, Moe VIC
3825, Australia
Phone: +61 3 5132 2600
Brisbane, AU
8A/36 Agnes St, Fortitude Valley
QLD 4006, Australia
Phone: +61 7 3188 5264
Hamilton, CA
50 Dundas St E, Dundas, ON
L9H 7K6, Canada
Phone: +1 905-544-4144
Dordrecht, NL
Burgemeester de Raadtsingel 67, 3311 JG
Dordrecht, Netherlands
Phone: +31 78 614 6288
Kerkrade, NL
Eurode-Park 1, Kerkrade, Limburg 6461
KB, Netherlands
Phone: +31 78 614 6288
São Paulo, BZ
R. Olimpíadas, 205, 4. Andar
Vila Olimpia, São Paulo, SP, CEP 04551-000
Phone: +55 11 3728-9372
Pretoria, SA
1 Pegasus Building 210 Amarand Ave
Waterkloof Glen, Pretoria, 0181
South Africa
Phone: +27 12 003 2916