Hello, I've packaged two applications.

The first application is already deployed to over 5000 machines.

Now, if I deploy the second application, it cuases at every start of it a configuration "reapir" of the first application.

If I start the second application as administrator, the repair action does not occure! Can somebody tell me why it not occurs when I run as admin?

I think it's a conflict of the registered components of the packages..

Is there a way to resolve the problem, without repackaging and deploying the first application again?

Thank you very much!

0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Answers

1
answer already given to exact the same question...
Answered 01/22/2013 by: jaybee96
Red Belt

  • But you removed the correct answer ....WHY??!
  • You completely removed the question as well... ;-)
Please log in to comment
1

Check your Eventviewer and search for the error .. You will see which component is causing the repair and you can solve the issue in the second application without touching the first app. 

Answered 01/22/2013 by: jaybee96
Red Belt

Please log in to comment
1

Sry, I removed the last question because it wasn't defined clearly..
I find out which component is causing the repair. It's a dll-file in "C:\Windows\microsoft.net\assemblys\GAC_MSIL\". My problem is that I don't really know what I have to do in the second application-package, because there is no same component represent in the second package.

Thank you very much.

Answered 01/22/2013 by: kleynpackager
Orange Belt

  • Did you repackage the application?
  • This content is currently hidden from public view.
    Reason: Removed by member request
    For more information, visit our FAQ's.
Please log in to comment
1

I repackaged the first application. The second acpplication (which causes te repair) is a vendor MSI.

Answered 01/22/2013 by: kleynpackager
Orange Belt

Please log in to comment
1

Use ProcMon..

There could be some permission realated issues in registry or Files and Folders

Answered 01/22/2013 by: jagadeish
Red Belt

Please log in to comment
0

The component that is causing the repair is from the first app ( because it is repairing..)

This means that somehow your first package includes .net info that you repackaged with the app?

You could create a Patch / upgrade for the first package to clean up .. but I would know for sure when I could see your repackaged MSI (no.1)

 

Answered 01/22/2013 by: jaybee96
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity