4 replies to this topic

[Superfreak3]

Hi All,

I hope someone can help me quickly. We have an old web app which was installed via a 32 bit package. It really didn't matter what architecture of the package was because everything in the package was directed to c:\inetpub\wwwroot, where there is no redirection of any kind.

Since I've had the problem I'll describe I've read that it may be problematic to upgrade software delivered via a 32 bit package with a 64 bit package (x64 in Template Summary Property). However, our initial release of our new product was delivered via a 64 bit package and there were no issues. The old app was removed and the new web app actually had some utilities sent to Program Files, which is the desired location.

Now we get to the problem. Our latest release, when used to upgrade the initial (32 bit package) application, has the above mentioned utility files redirected to Program Files (x86). There are also some new file that were supposed to go to a different area under Program Files, but end up in Program Files (x86).

WIN64DUALFOLDERS shows up in the log, but I do not know why. The package has x64 in the Template Summary Property in the template and all of the above mentioned components are marked as 64 Bit in the template as well. I've attached the log if anyone wishes to take a peek.  It's in two parts so if you need to see the second half, let me know as it would exceed upload limit.

What is triggering or why is dual folders coming into play. What can I check between our first release of the x64 package and this latest package to see what might might have changed. I am totally stumped. I hope someone can lead me toward the light!!

Thanks in advance for any info or tips you can provide!

Attached Files

•  MSILogPart1.zip   482.51KB   43 downloads

[Superfreak3]

UPDATE:  This problematic scenario only seems to play out on Server 2012.  The test run on Server 2008 does not encounter the same redirection and everything lands on the target machine as intended (Program Files).

 

The earlier, 32 bit packaged version of the software was not supported on Server 2016, but I might try there as well.

[Superfreak3]

Can anyone tell anything from the attached log?

[Stefan Krueger]

I don't see that WIN64DUALFOLDERS is interfering with your inetpub path, only with other paths like tomcat.

Please name one component and file name that gets installed in the wrong location, so I can look for it in the log.

[Superfreak3]

I don't see that WIN64DUALFOLDERS is interfering with your inetpub path, only with other paths like tomcat.

Please name one component and file name that gets installed in the wrong location, so I can look for it in the log.

 

All of the stuff in the Tomcat folders is being directed to the wrong architecture file system.  The wsclient.war file in the DND_wsclient.war component can be checked as problematic.  

 

Thanks Stefan and sorry for the late reply!