Our current environment consists of an ePO 4.0 server (on a VM running W2K3) that we use to manage all VSE 8.7 clients in an environment consisting of approximately 300 workstations/servers/laptops. The database resides on a dedicated SQL server running 2008 (specifically, 10.50.4000.0).
We will be implementing HIPS and Application Control over the next several months, and in preparation for these additions, I've been working on upgrading our ePO server to 5.1
Prior to making changes to production, I set up a test environment to familiarize myself with the upgrade process.
Then I run the 5.1 upgrade and when it gets to the point of starting the new services, it "hangs" for a long time, then reports "Rolling back action", and the entire install backs out.
When I enabled debugging, I see the following error:
FAILURE: In LaunchAppAndWait while trying to run the following program:
Return code: 1
Error message: Incorrect Function.
When I investigated the logs in %temp%, I see the same error. It attempts this 45 times before rolling back.
Unfortunately, it seems like this error is somewhat common, and most of my searches have revealed that this occurs when upgrading/migrating prior revisions. Either way, I've double-checked settings. DB is in simple recovery mode. I'm not seeing any errors on the SQL side. I even re-tried the entire upgrade process without first importing upgraded packages into the repository.
I also tried the 'upgradecompatibility' method (exporting/importing file) and I get the same error.
Debugging installer errors can become quite involved given the amount of work the installer has to achieve. This message may merely be a symptom rather than cause for example.
You may be best served by opening a support case here tbh.
Hi Michael, as you have already upgraded ePO 4.0 to 4.6 I would propose something different.
As you now have the "transfer system" option you can install a fresh new ePO 5.1 to a new server then import the system tree from the old server,policies, tasks, policy assignments and task assignments and finally transfer computers from old epo server to new epo server (Before doing this you have to register the new epo server into the old one).
With this you may avoid any problems coming from previous epo version
I got the same error yesterday when trying to migrate from 4.6.6 to 5.1 the same way you did (first moving 4.6.6 to new server, move db to new server, upgrade to 5.1).
Well - I do not excactly now if the error occures in LaunchAppAndWait - but I guess its the same (server 2008 r2, too).
Did you got any news?
I wonder if the 5.1 installer already migrated / converted the db?
Yep, I strongly suspected that I'd need to open a support case. Problem is that our parent company holds all the "keys" to be able to do this, but I have a contact that should be able to help me out with this.
I might try the "transfer system" method suggested above, in my test environment.
meforum: no new news.
I might also try to get a hold of the 5.0 install and see if that works.
hi - any news on this issue? I still have it on one server and will try it again the following days ...
Nope, unfortunately, no new news. This sorta stalled over the holidays. I'm going to try going from 4.6->5.0 then if that works, 5.0->5.1. I'm not optimistic, but it is worth a shot. Failing that, I will be opening an issue.
So about a week ago I ended up contacting support, and learned that a resolution was recently issued:
The tech and I went through the directions on the call and it works! Problem resolved.