File is not marked for installation - Advanced Installer Community
pbauer@softfolio.de
Posts: 2
Joined: Wed Feb 13, 2019 12:34 pm

File is not marked for installation

Ich habe ein Problem, was schon mehrmals hier in Forum besprochen worden ist. Aber es gibt keine Punkte wo man sagen kann, dass es davon abhängig ist.
Bei meinem Setup Projekt tritt der Fehler "Fehler 2753. Die Datei 'REG_DotNetWrapperDMS_.bat' ist nicht für die Installation markiert." bei einer Bat-Datei in einer Custom Action, aber nur auf bestimmten Maschinen. Auf meiner VM oder auch Lokal auf dem Laptop tritt es nicht auf. Auf dem Komputer von meinem Kollegen tritt es auch nicht auf. Aber bei einem Kunde tritt es auf jedem Terminalserver auf.
Was kann ich dagegen tun?

I have a problem which has already been discussed several times here in the forum. But there are no points where you can say that it depends on it.
In my setup project the error "Fehler 2753. Die Datei 'REG_DotNetWrapperDMS_.bat' ist nicht für die Installation markiert." occurs in a bat file in a Custom Action, but only on certain machines. On my VM or also locally on the laptop it does not occur. It doesn't occur on my colleague's computer either. But for a customer, it occurs on every terminal server.
What can I do about it?
Attachments
MSIB95C.LOG
(472.65 KiB) Downloaded 266 times
Softfolio DMS.aip
(289.59 KiB) Downloaded 292 times
Catalin
Posts: 7852
Joined: Wed Jun 13, 2018 7:49 am

Re: File is not marked for installation

Hello and welcome to our forums,

First of all, thank you for the sent log and AIP files. After investigating them, this is what I have discovered so far:

I could notice that you are trying to launch a BAT through a "Launch Installed File" custom action. As you may already know, the "Launch Installed File" custom action must be scheduled after the files have been deployed on the computer. The problem here is that your BAT file is not installed on the target computer as it can be seen in the following line:

Code: Select all

MSI (c) (04:50) [11:25:36:055]: Disallowing installation of component: {B0B48542-C4CF-48AE-BEEE-D2ED5CE52F88} since the same component with higher versioned keyfile exists
Where the {B0B48542-C4CF-48AE-BEEE-D2ED5CE52F88} is the GUID of your BAT file. To check this first hand, you can proceed as it follows:

"Files and Folders" page --> "SAGEINSTALLPATH" --> "Shared" --> select "REG_DotNetWrapperDMS_" --> right click --> "Go to component"

As the following condition:

Code: Select all

As you may already know, the "Launch Installed File" custom action must be scheduled after the files have been deployed on the computer.
is only specific to the "Launch Installed File" custom action, a possible workaround would be to use a "Launch File" custom action instead.

Another workaround would be to apply the "Always overwrite existing file" attribute to your BAT file. To do so, please go to the following path (in your project):

"Files and Folders" page --> "SAGEINSTALLPATH" --> "Shared" --> select "REG_DotNetWrapperDMS_" --> right click --> "Properties" --> "Operations" tab --> "Always overwrite existing file"

Hope this helps.

All the best,
Catalin
Catalin Gheorghe - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
pbauer@softfolio.de
Posts: 2
Joined: Wed Feb 13, 2019 12:34 pm

Re: File is not marked for installation

Hello Catalin,

thank you for the answer. The "Always overwrite existing file" didnt help for my issue. But after some trys and Errors I finaly found the caurse and the solution.
In my case I had to generate a new GUID for the component, becaurse this component is used in other applications that are also installed on the target machine.


best regards
Paul
Catalin
Posts: 7852
Joined: Wed Jun 13, 2018 7:49 am

Re: File is not marked for installation

Hello Paul,

Thank you for your followup on this. I am glad you got this working.

All the best,
Catalin
Catalin Gheorghe - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”