+ Post New Thread
Page 1 of 3 123 LastLast
Results 1 to 15 of 35
Educational Software Thread, package failed to install rmcc4 in Technical; Hi eveyone, I am quite new to the job and the school I work in so I guess I am ...
  1. #1

    Join Date
    Mar 2014
    Posts
    17
    Thank Post
    5
    Thanked 0 Times in 0 Posts
    Rep Power
    0

    Unhappy package failed to install rmcc4

    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

  2. #2

    X-13's Avatar
    Join Date
    Jan 2011
    Location
    /dev/null
    Posts
    9,460
    Thank Post
    629
    Thanked 2,112 Times in 1,449 Posts
    Blog Entries
    19
    Rep Power
    881
    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.

  3. #3

    Join Date
    Mar 2014
    Posts
    17
    Thank Post
    5
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    It says that it had been deployed then that it had failed. I can't find anymore detail.

  4. #4

    X-13's Avatar
    Join Date
    Jan 2011
    Location
    /dev/null
    Posts
    9,460
    Thank Post
    629
    Thanked 2,112 Times in 1,449 Posts
    Blog Entries
    19
    Rep Power
    881
    Quote Originally Posted by Hadleigh View Post
    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.
    Last edited by X-13; 19th March 2014 at 10:35 PM.

  5. #5

    Join Date
    Mar 2014
    Posts
    17
    Thank Post
    5
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    Thank you

  6. #6
    supawat1's Avatar
    Join Date
    Nov 2012
    Posts
    86
    Thank Post
    0
    Thanked 14 Times in 14 Posts
    Rep Power
    6
    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.

  7. #7

    X-13's Avatar
    Join Date
    Jan 2011
    Location
    /dev/null
    Posts
    9,460
    Thank Post
    629
    Thanked 2,112 Times in 1,449 Posts
    Blog Entries
    19
    Rep Power
    881
    Quote Originally Posted by supawat1 View Post
    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.

  8. #8

    Join Date
    Mar 2014
    Posts
    17
    Thank Post
    5
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    Quote Originally Posted by supawat1 View Post
    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

  9. #9

    Join Date
    Mar 2014
    Posts
    17
    Thank Post
    5
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    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

  10. #10
    GeekyPete's Avatar
    Join Date
    Mar 2013
    Location
    In a cold dark server room.
    Posts
    339
    Thank Post
    23
    Thanked 78 Times in 59 Posts
    Rep Power
    27
    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.

  11. #11

    Join Date
    Jun 2013
    Posts
    34
    Thank Post
    1
    Thanked 6 Times in 5 Posts
    Rep Power
    4
    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.

  12. #12

    Join Date
    Mar 2014
    Posts
    17
    Thank Post
    5
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    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 ?

  13. #13

    Join Date
    Mar 2014
    Posts
    17
    Thank Post
    5
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    Quote Originally Posted by Techykev View Post
    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 ?

  14. #14

    Join Date
    Jun 2013
    Posts
    34
    Thank Post
    1
    Thanked 6 Times in 5 Posts
    Rep Power
    4
    In the L/H Navigation Pane expand Software, Packages and products, Assignment Overview.

  15. #15

    Edu-IT's Avatar
    Join Date
    Nov 2007
    Posts
    7,250
    Thank Post
    404
    Thanked 630 Times in 575 Posts
    Rep Power
    185
    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.

SHARE:
+ Post New Thread
Page 1 of 3 123 LastLast

Similar Threads

  1. Replies: 2
    Last Post: 8th March 2012, 02:59 PM
  2. [MS Office - 2007] SP2 Fails to Install
    By Stuart_C in forum Office Software
    Replies: 9
    Last Post: 17th August 2009, 03:57 PM
  3. [MS Office - 2003] [SOLVED] Office 2003 fails to install after XP SP3 is installed
    By link470 in forum Office Software
    Replies: 2
    Last Post: 8th May 2008, 09:42 AM
  4. R2 Printer Manager Failed to install
    By apeo in forum Windows
    Replies: 6
    Last Post: 4th July 2007, 06:57 AM
  5. Replies: 1
    Last Post: 16th February 2006, 09:57 AM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •