MSXML4.DLL, MSXML4A.DLL and MSXML4R.DLL
Hi!
I have some trouble with a application.
When i´m repackageing it and are about to check it in the ConflictManager.
These 3 dll files are in conlict with other versions of the dll.
I have triied to isolate them an move them and replace them.
Still i recive the same error:
No valide licnes key found. Application name will not run without a valid licens key.
You may have to repair the installation or reinstall the product.
The application works just fine if i don´t do anything.
But some how i have to fix this conflict.
Is there anybody that can help me?
I have some trouble with a application.
When i´m repackageing it and are about to check it in the ConflictManager.
These 3 dll files are in conlict with other versions of the dll.
I have triied to isolate them an move them and replace them.
Still i recive the same error:
No valide licnes key found. Application name will not run without a valid licens key.
You may have to repair the installation or reinstall the product.
The application works just fine if i don´t do anything.
But some how i have to fix this conflict.
Is there anybody that can help me?
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
brenthunter2005
18 years ago
These files are part of the Microsoft XML redistributable. The Merge Module should really be added to your MSI instead of the actual files.
Posted by:
Jts71
18 years ago
I solved it.
The original .msi was over writeing the changes i was doing in the .wsi. I had to do the following after the ConflictManager:
Rewrite the licence.ini and in the Property table i added the following:
NM_USERNAME (â€ÂUserâ€Â),
NM_COMPANYNAME (â€ÂCompany nameâ€Â) och
NM_LICENSEKEY (â€Âxxxx-xxxx-xxxx-xxxxâ€Â).
Then i compiled and checked for any conflicts.
No conflicts and the package is now up and running.
The original .msi was over writeing the changes i was doing in the .wsi. I had to do the following after the ConflictManager:
Rewrite the licence.ini and in the Property table i added the following:
NM_USERNAME (â€ÂUserâ€Â),
NM_COMPANYNAME (â€ÂCompany nameâ€Â) och
NM_LICENSEKEY (â€Âxxxx-xxxx-xxxx-xxxxâ€Â).
Then i compiled and checked for any conflicts.
No conflicts and the package is now up and running.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.