Reply to Thread

Re: Error 52 when installer runs

I Googled and found quite a few "Runtime Error 52: Bad file name or number" error messages that are related to Visual Basic and/or Word. Perhaps you are running a VB tool as part of your installation?

https://msdn.microsoft.com/en-us/lib...(v=vs.60).aspx

http://bytes.com/topic/access/answer...le-name-number

As far as I know, there is no "error 52 bad file or name" error message defined in SetupBuilder. But a screenshot can tell if it comes from the installer engine. IMO, it is not a SB error code.

Friedrich

Re: Error 52 when installer runs

Hello,

Do you have a screenshot? I can't find any reference to "error 52 bad file or name" in the installer runtime nor in the text resources. Are you sure it is a SetupBuilder error message?

Friedrich

Error 52 when installer runs

Hi,
I have used SB for a long time.

First time I have seen an error 52 bad file or name.

Machine is Windows 7 Pro.

The PATH in the popup on client computer says //server01 but that server was retired and replaced with //svr2014

I used regedit to search the registry and could not find anything.

The install path of the software is to the C: drive.

My only guess is that the installer is looking for an old version of the software to Update and gets the path and that path somehow is related to //server01

I searched registry for the UpgradeGUID in the installer as well and couldn't find it.

The tech guy who set up the new server is clearly not too bright because there are tons of references to server01 still on the computer even though it no longer exists.

Has anyone seen this error? My client cannot install my app or even re-install it because of this error.