Hi all,

Our guy out on site is experiencing a problem -- Installs as an Admin, when another user logs on (supposedly also an Amdin) and initiates the app, the expected repair runs to write some user 'stuff'. The problem is he's receiving a 1308 error and the file indicated is a 64 bit file that shouldn't have even been installed on a 32 bit Vista system.

I wouldn't expect the file to be there, but we're checking on site.

We've never run into the 1308 error before and I really don't know what this could be so fire some questions that might lead me somewhere.

I guess I could try copying the indicated file to the indicated location, but that would be a bandaid if it would even work at all.

I'm waiting on a log now also to see what the stated state of the problematic component is.

Thanks SOOOO MUCH for any help!
0 Comments   [ + ] Show Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.


You have 32-bit and 64-bit components in the same MSI?!?

My guess is that the file's component isn't conditioned for 64-bit only. As you say, the log will tell all.
Answered 10/22/2010 by: VBScab
Red Belt

Please log in to comment
The component is conditioned for 64 bit and during the initial install, it is no placed on the problematic 32 bit machine. I have no idea why a repair install to place some user stuff would be looking for that file. Its no there nor should it be.

I'm still waiting on a log to arrive from the site too.

We only hit the one snag on the 64 bit file that shouldn't even be installed. If one ignores, the reconfiguration completes successfully. We have other 64 bit files included in the install and they are not installed or causing any problems during repair. I wonder what in the heck is going on.
Answered 10/22/2010 by: Superfreak3
Black Belt

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