package failed to install rmcc4

[Hadleigh]

Hi eveyone,

 

I am quite new to the job and the school I work in so I guess I am doing something silly, but I am at my wits end with this problem....

 

I have been asked to upgrade target tracker from v14 to v14.1. I have made a package which shows on the rm console, as a test before deploying to many pc, I started be testing it on a couple first. I unassigned the previous version and assigned the new version on the pc that I was testing it on. On all of the pc it says that it is installing then suddenly it uninstalls then I get a message on the console saying the package had failed to install. In my desperation I have made the previous version unassignable with the option of being able to assign if I need to. I am wary of taking the previous version right off incase I can't get the latest version to work.

 

I have tried all the different ways of making the package, using the separate package builder we have and also doing it direct to the console, making sure I take off any of those that don't work off.

 

I can't understand what is wrong, I have followed all the instructions.

 

Any suggestions would be greatly appreciated

[X-13]

There should be something in RMMC about why it failed. [Or you can look through the event viewer.]

 

What does it say in the task history?

 

 

 

Also: looks like I know what I'm doing tomorrow... I didn't know there was an update.

[Hadleigh]

It says that it had been deployed then that it had failed. I can't find anymore detail.

[X-13]

It says that it had been deployed then that it had failed. I can't find anymore detail.

 

When I get back into the office, i'll find out exactly where it is.

 

I've had to use it a few times to figure out why packages failed.

Edited March 19, 2014 by X-13

[Hadleigh]

Thank you

[supawat1]

What I did

 

1. Extract Target Tracker.exe using winrar software to get its MSI file.

2. Use RM Application Wizard to package it up

3. Deploy the software using RM CC4 Management console

 

I am sure it will never fail again.

[X-13]

What I did

 

1. Extract Target Tracker.exe using winrar software to get its MSI file.

2. Use RM Application Wizard to package it up

3. Deploy the software using RM CC4 Management console

 

I am sure it will never fail again.

 

You can skip step 2.

 

I just import it as a CC3 package. Works fine every time.

[Hadleigh]

What I did

 

1. Extract Target Tracker.exe using winrar software to get its MSI file.

2. Use RM Application Wizard to package it up

3. Deploy the software using RM CC4 Management console

 

I am sure it will never fail again.

 

 

 

I have tried it that way, but not used winrar, I will have another go using that. Thanks for your help:)

[Hadleigh]

I tried that way too, and although it made the package and quoted that it was a cc3 auto converted, it said it was invalid format, I think. Thanks for your help:)

[GeekyPete]

Have you still only tried it on the one station? Do you have a clean station to try it on? If you go to tasks in RMMC, find the install task, and open it up you should be able to drill down to the target device and there may be more detail on the error there. Can't remember the exact buttons to click on but I can let you know when I get into work tomorrow. There is also a log file on the computer itself, again I'll let you know where to look when I get into work.

 

If you are building packages you should always have a clean station for testing. Clean is a relative term, but it should be a close to OS Only as you can get on an RM computer. Keep your AV, essential plug ins, and IE or browser of your choice. But nothing else, unless it is a dependency of the app you are working on. Make sure it is in the Build folder in locations as this blocks inheritance. Once you have this set up, take a restore image. You can now allocate what ever you like to it and use it as a normal computer if you want but if you restore it, you have a test platform in 20 minutes. You can trail whatever modifications you like knowing you can get it back to a clean state in the time it takes to have a coffee break.

[Techykev]

In the RMMC under Assignment overview right click the failed package and select properties - this should give you a reason why the package failed. You can check this error against the RM Knowledge base on the RM Website, the most common error we get is "Root element is missing" the fix for this is documented on the RM website Tech Article TEC1395295.

[Hadleigh]

Hi,

I have tried it on a few different stations, all coming back with the same thing. I have a dedicated clean package builder machine that is restored everytime it is used.I use it to build the package but I have never tried to assign it to that computor, would that be worth a try as a test ? I have tested the app on the package builder before building it to check that it works.

 

I have looked at the target devices but all I can get when I interrogate it, is failed package. Would the package builder, build a package that has errors ? or is there something on the stations stoppping it. I have unassigned the previous version, is that all I needs to do ?

[Hadleigh]

In the RMMC under Assignment overview right click the failed package and select properties - this should give you a reason why the package failed. You can check this error against the RM Knowledge base on the RM Website, the most common error we get is "Root element is missing" the fix for this is documented on the RM website Tech Article TEC1395295.

 

Sorry, I can't see where assignment overiew is, is it in history ?

[Techykev]

In the L/H Navigation Pane expand Software, Packages and products, Assignment Overview.

[Edu-IT]

Try and run the MSI manually on the machine and see what happens? You'll probably find this is the quickest way to see whether the package actually works.

[X-13]

Sorry, I can't see where assignment overiew is, is it in history ?

 

Software > Packages & Products > Assignment Overview

 

Click "Select Items" and choose the computer you pushed Target Tracker to and Target Tracker itself.

 

If you double click on the icon that shows if it installed or not, it'll tell you why it failed. [sometimes... other times it just says "failed package" which means nothing.]

[Hadleigh]

In the RMMC under Assignment overview right click the failed package and select properties - this should give you a reason why the package failed. You can check this error against the RM Knowledge base on the RM Website, the most common error we get is "Root element is missing" the fix for this is documented on the RM website Tech Article TEC1395295.

 

Sorry bit of a blonde moment, I found it and this is what it says for one of the machines

 

Status: InstallFailed

Time: 19/03/2014 10:54:40

Error: Failure Type: MSI error, check Event Viewer on machine for more detail: Could not complete the operation because a fatal error occurred during installation.

[Edu-IT]

So run the MSI and see what it says?

[bossman]

@Hadleigh:

 

I would download the MSI again seems to me it could be a corrupted download,

[X-13]

Sorry bit of a blonde moment, I found it and this is what it says for one of the machines

 

Status: InstallFailed

Time: 19/03/2014 10:54:40

Error: Failure Type: MSI error, check Event Viewer on machine for more detail: Could not complete the operation because a fatal error occurred during installation.

 

Run it manually. That should show you what's going on.

 

I've had that happen with a piece of software, and all it was was an ignorable message saying a DLL failed to register. [Also; "was was" God dangit, English language...]

[Techykev]

You could try copying the package to c:\drive of a failing PC and run the MSI manually and see if it gives any error messages during the install, failing this I would suggest raising a call with RM on their support line 0845 1201351. EDIT-looks like I'm repeating X-13!! Edited March 20, 2014 by Techykev

[Hadleigh]

O.k, where is event viewer ?

[X-13]

O.k, where is event viewer ?

 

...If you're on Windows 7, login with your sysadmin level account. WinKey > Event Viewer.

 

If you're on a different computer than the one you want to look at click "action" then "connect to another computer"

[Hadleigh]

Thank you so much for your help guys, I have raised a call with R.M and will try what you have suggested.

[Edu-IT]

RM won't help you unless it's a deployment issue with their software. I.e the RMMC refuses to deploy any software. You need to run the MSI manually and report back what happens.