Video Screencast Help

Applying TECH179526 error "No object file was specified"

Created: 27 Jan 2012 • Updated: 31 Jan 2012 | 1 comment
This issue has been solved. See solution.

We just acquired the PCAnywhere hotfix TECH179526.

http://www.symantec.com/business/support/index?page=content&id=TECH179526&key=52418

When applying this patch to our test clients, we're running into an issue.
Error message: "No object file was specified." is displayed after installing the patch.

It seems not to be an MSI error, but rather when the patch restarts the host service, it's causing this error to display.

We're silently appling the patch with the MSI using this syntax:
msiexec.exe /i PCAnywhere_12.5_Tech179526.msi /QN

But still, the error message dialogue is displayed:
 

pcAnywhere Host
--------------------------
No object file was specified. This may have ocurred beacuse you are starting the host for the first time, using Services Control Panel Applet.
To start the host, you may try one of the following:

1) Specify the name of a Be Host File (*.BHF) in the Start Parameters for the host using Services Control Panel Applet,
2) Start the host from the pcAnywhere Manager,
3) Open a Be Host File (*.BHF) in Explorer.

 

We're using a mix of AD and PCAnywhere authentication in our environment.
Our current pcAnywhere AWHLogon.dll version is 12.5.0442.
The patch applies, and the DLL is changed to 12.5.0.480, however the error message above is still displayed, even with hidden options set and deployed hidden with Altiris.

We don't want our end users seeing this message, and want to be sure functionality is 100%.

This is a critical patch for our enviornment, and any assistance in avoiding this error message would be greatly appreciated.

Thanks!

Comments 1 CommentJump to latest comment

Imfusio's picture

I figured out the answer to our problem:

The reason we were seeing that error was because the registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\pcAnywhere\CurrentVersion\Host
"Connection"

Did not exist. I created a script for deploying the patch that will check if that registry key exists, and populate it with the value of "AutoStart" registry key (adding quotes around it), if it exists.

If AutoStart ALSO doesn't exist, the script will search for the two most common BHF files ("Network, Cable, DSL.bhf" or "pcANSHost.bhf") in the appropriate locations (WinXP/Win7 respective).

It'll populate AutoStart registry key, then populate the Connection key, and continue applying the patch.

Once Connection registry key is all set, applying the patch works perfectly without displaying that error.

SOLUTION