Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

pcAnywhere Diagnostic and Connect Tool v1.0014

Created: 21 Mar 2011 • Updated: 06 Apr 2011 | 36 comments
Screenbert's picture
+16 16 Votes
Login to vote

pcAnywhere Diag Features

  • Encrypts and stores connection and diagnostic credentials
  • Remembers the last PC connected to
  • Ability to store a favorites list
  • Single click to modify, double click to set as connection PC
  • Checks the client status and repairs any issues
  • Eliminates the “Raising Encryption” message upon connect
  • Works even if the Altiris console is unavailable

(click on image to see larger view)

Because of the diagnostic features, this tool only works properly for if you are an administrator on the PC you are connecting to.

Feedback and bug reporting are always appreciated.

Comments 36 CommentsJump to latest comment

dlopes's picture

Thanks!

This tools is gonna be very usefull for troubleshooting access server and external hosts :)

Daniel Lopes de Oliveira
Technical Team Leader - Endpoint Management & Mobility

+1
Login to vote
michael cole's picture

This tool looks huge for us, however on pressing connect we got the installer error "The feature you are trying to use is on a network resource that is unavailable."

It is looking in temp files for Symantec_pcA_AutoStart_Host.msi

I did not find the file on my local PC but i found an exe by the same name on the NS.

Now to let you know it could well be because we delete the quickconnect executeable to prevent people using that to prevent insecure use. Is this error because of this?

And therefore if it relies on Quick connect does it not also use the same system for storing and hashing domain passwords which we want to stay away from?

I was hoping this was an alternative to quick connect but I would appreciate some feedback.

Mike

Michael Cole

Principal Business Critical Engineer

Business Critical Services

+2
Login to vote
Screenbert's picture

When you use the NS Console does it allow you to connect or do you get the same error? It does rely upon the PCA infrastructure which includes the quickconnect. Yes it does store the passwords encrypted if they choose to remember credentials. It is using 256 bit encryption when storing the password.

If that wouldn't work for you what would you like to see?

Screenbert

+1
Login to vote
michael cole's picture

We remove the quickconnect executeable as a policy after deployment to prevent people using it and force them through the console where the attempts are audited. Users of PCA would choose not to use the console since its more steps however there were some security issues as of last year with the CHF files that caused us to take this route.

I tested your app by putting the executeable back - it worked so I believe it to be invoking self repair when it cannot find QC. There is another error when pressing any other button than connect: I get Object reference not set to an instance of an object. I could PM the contents of the debug if it helps?

We use XP pro in case that makes a difference.

I'm still testing this app from a security point of view so i'm not going to say too much at this stage except the way it works is probably too close to the QC in the way it creates CHF files. If i was to say what i would like to see, I would like the same applpication that didnt save credentials anywhere but i'm certainly not making a request since i see that as a Symantec piece of work. 

Michael Cole

Principal Business Critical Engineer

Business Critical Services

+2
Login to vote
Screenbert's picture

Michael,

I can strip out those other pieces easily enough for a super-lite version. However I'd like to see the debug error that you get first. We use it on XP and W7. The project is built on .net framework 3.5, so if that is not loaded that could be an issue.

Screenbert

Screenbert

+1
Login to vote
michael cole's picture

The message box says unhandled exception, the message says not set to an instance of an object. The green blurb on the right gets this far:

10.8.118.120 - 15:29:19: Verifying the Symantec pcAnywhere Host Service exists.
10.8.118.120 - 15:29:19: Symantec pcAnywhere Host Service exists.
10.8.118.120 - 15:29:19: Symantec pcAnywhere Host Service is running.
10.8.118.120 - 15:29:19: Symantec pcAnywhere Port 5631 is open and accepting connections.(TECH107919)
10.8.118.120 - 15:29:19: Checking Authentication speed fix.(TECH109926)
10.8.118.120 - 15:29:19: Authentication speed fix already configured.
10.8.118.120 - 15:29:19: Checking last configuration request.

ERROR:

See the end of this message for details on invoking

just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
   at pcADiag.Form1.LastConfigurationRequest(String strPCName)
   at pcADiag.Form1.btnCheckState_Click(Object sender, EventArgs e)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

************** Loaded Assemblies **************
mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.3615 (GDR.050727-3600)
    CodeBase: file:///c:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
pcADiag
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Program%20Files/pcADiag/pcADiag.exe
----------------------------------------
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.3614 (GDR.050727-3600)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Core
    Assembly Version: 3.5.0.0
    Win32 Version: 3.5.30729.1 built by: SP
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Core/3.5.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Data
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_32/System.Data/2.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
System.Xml
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.3082 (QFE.050727-3000)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Configuration
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.ServiceProcess
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.ServiceProcess/2.0.0.0__b03f5f7f11d50a3a/System.ServiceProcess.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

hope that helps
 

Michael Cole

Principal Business Critical Engineer

Business Critical Services

+1
Login to vote
Screenbert's picture

I found the error. I'll get an updated version posted soon.

Screenbert

+1
Login to vote
Screenbert's picture

I added a fix for the issue you were seeing and I also added check to make sure a DLL is registered. Let me know if it works for you now.

Screenbert

+2
Login to vote
michael cole's picture

Yes you fixed that issue.

I feel compelled to see this out with you now! I have another issue that comes when the app attempts to reinstall PCA - it looks for a location c:\temp\~SMIF26E\SYMANT~1.MSI\ but the MSI isnt there. I spent some of the morning looking for where it might be and didnt get any results - i tried the agents cache and c:\windows\installer without luck. I wonder if you can think of a workaround for that?

Michael Cole

Principal Business Critical Engineer

Business Critical Services

+2
Login to vote
Screenbert's picture

So the app is using the OLE automation to create a CHF file. I initially used the OLE automation to launch the OLE file, but it would remain hidden in the background. So I found that I could simply launch a CHF file and that would do everything. That being said, double click a CHF file and see if you get the same behavior.

It's interesting that the console doesn't give you this error as I thought that it does the same thing. I'll do some digging on my end to see what I can find. Let me know what happens when you double click on a CHF file.

Screenbert

+1
Login to vote
michael cole's picture

The primary functions of the app all work as expected after the fix. What doesnt work is when you select any function with "repair" in the description. The app initiates an MSI repair, but fails because the source isnt available.

Yes launching CHF's and your app is fine.

Michael Cole

Principal Business Critical Engineer

Business Critical Services

+2
Login to vote
Screenbert's picture

Can you give the text from the black display window? I'm thinking this might be something with registering the pcaagent.dll if it isn't registered....

Screenbert

+1
Login to vote
michael cole's picture

Hey Screenbert,

I think you are thinking that its reinstalling my PCA when i press a button.

It's reinstalling the targets PCA when i press check and repair...which is expected results...

But that fails because it cant find the source MSI.

Screen info:

10.8.118.120 - 17:16:26: Ping Address: 10.8.118.120 bytes=32 time=0 TTL=128
10.8.118.120 - 17:16:26: Verifying the Symantec pcAnywhere Host Service exists.
10.8.118.120 - 17:16:26: Symantec pcAnywhere Host Service exists.
10.8.118.120 - 17:16:26: Symantec pcAnywhere Host Service is not running. Attempting to restart...
10.8.118.120 - 17:16:26: Service stopped successfully.
10.8.118.120 - 17:16:26: Starting service...
10.8.118.120 - 17:16:56: Unable to start service within 60 seconds.
10.8.118.120 - 17:16:56: Unable to restart Symantec pcAnywhere Host Service.
10.8.118.120 - 17:16:56: Remote Desktop is in use on this box. The Remote desktop session may have to be terminated for the PCAnywhere Service to start. (TECH109910)
10.8.118.120 - 17:16:56: Symantec pcAnywhere Port 5631 is open and accepting connections.(TECH107919)
10.8.118.120 - 17:16:56: Checking if pcAAgent.dll is registered.
10.8.118.120 - 17:16:56: pcAAgent.dll is already registered.
10.8.118.120 - 17:16:56: Checking Authentication speed fix.(TECH109926)
10.8.118.120 - 17:16:56: Authentication speed fix already configured.
10.8.118.120 - 17:16:56: Checking last configuration request.
10.8.118.120 - 17:16:56: Last configuration request was on 24/03/2011 13:55:59.
10.8.118.120 - 17:16:56: ----------------------------------------------------------------------------------------------------------------------------------

Michael Cole

Principal Business Critical Engineer

Business Critical Services

+1
Login to vote
Screenbert's picture

The tool never attempts to reinstall the agent, however it appears from the log that it did restart the service because it was not running. Everything else looks like it's probably OK. That makes me wonder if you would get that error if you manually restart the service on the remote machine. Can you check that?

Screenbert

+1
Login to vote
michael cole's picture

Sorry I would update faster but the behaviour is confusing. Right now, although i swear it didnt start like this it invokes a repair on the executing machine every time. i repaired the app by running the MSI in the x86 directory but theres no change on my machine. I've tried on another machine and that simply does nothing, it never had that repair thing but it never worked either!

So this leaves me to try on another machine and come back to you. Sorry about this.

Michael Cole

Principal Business Critical Engineer

Business Critical Services

+1
Login to vote
BigRedAV's picture

I am using version 1.0.0 and i am getting this everytime i try to connect. I have tested multipl PC with no luck. Here is what is showing in the black window, and below that is the error details.

Thoughts?

BlackWindow:

PCName - 9:09:05 AM: Ping Address: x.x.x.x bytes=32 time=6 TTL=126
PCName - 9:09:05 AM: Verifying the Symantec pcAnywhere Host Service exists.
PCName - 9:09:05 AM: Symantec pcAnywhere Host Service exists.
PCName - 9:09:05 AM: Symantec pcAnywhere Host Service is running.
PCName - 9:09:05 AM: Symantec pcAnywhere Port 5631 is open and accepting connections.(TECH107919)
PCName - 9:09:05 AM: Checking if pcAAgent.dll is registered.
PCName - 9:09:05 AM: pcAAgent.dll failed to register.
PCName - 9:09:05 AM: Checking Authentication speed fix.(TECH109926)

Error Details:

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.IO.IOException: The network path was not found.

   at Microsoft.Win32.RegistryKey.Win32ErrorStatic(Int32 errorCode, String str)
   at Microsoft.Win32.RegistryKey.OpenRemoteBaseKey(RegistryHive hKey, String machineName)
   at pcADiag.Form1.CheckRegistrySpeedFix(String strPCName)
   at pcADiag.Form1.btnCheckState_Click(Object sender, EventArgs e)
   at pcADiag.Form1.btnCheckConnect_Click(Object sender, EventArgs e)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

************** Loaded Assemblies **************
mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll
----------------------------------------
pcADiag
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Program%20Files%20(x86)/pcADiag/pcADiag.exe
----------------------------------------
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Core
    Assembly Version: 3.5.0.0
    Win32 Version: 3.5.30729.5420 built by: Win7SP1
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Core/3.5.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Data
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_64/System.Data/2.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
System.Xml
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Configuration
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.ServiceProcess
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.ServiceProcess/2.0.0.0__b03f5f7f11d50a3a/System.ServiceProcess.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

0
Login to vote
Screenbert's picture

Is the remote registry service enabled on the remote machine? Are you connecting with Administrator credentials?

Screenbert

0
Login to vote
Jason_Wilson's picture

Just downloaded - and I get an Unhandled exception when clicking the Check State and Repair button OR Check State, Repair, and Connect button.

No error or issue using the Connect button

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
   at pcADiag.Form1.CheckRegistrySpeedFix(String strPCName)
   at pcADiag.Form1.btnCheckState_Click(Object sender, EventArgs e)
   at pcADiag.Form1.btnCheckConnect_Click(Object sender, EventArgs e)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

************** Loaded Assemblies **************
mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.3615 (GDR.050727-3600)
    CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
pcADiag
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Program%20Files/pcADiag/pcADiag.exe
----------------------------------------
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.3614 (GDR.050727-3600)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Core
    Assembly Version: 3.5.0.0
    Win32 Version: 3.5.30729.1 built by: SP
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Core/3.5.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Data
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_32/System.Data/2.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
System.Xml
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.3082 (QFE.050727-3000)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Configuration
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.ServiceProcess
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.ServiceProcess/2.0.0.0__b03f5f7f11d50a3a/System.ServiceProcess.dll
----------------------------------------
PCACDLL
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Program%20Files/pcADiag/PCACDLL.DLL
----------------------------------------
Microsoft.VisualBasic
    Assembly Version: 8.0.0.0
    Win32 Version: 8.0.50727.3053 (netfxsp.050727-3000)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

0
Login to vote
BigRedAV's picture

The remote registry service is running on th remote computer. I am also connecting as an admin

0
Login to vote
Screenbert's picture

I just updated the download with version 1.0014. Instead of erroring out it should simply say that it can't complete the action if there is an issue. Try the new version.

Screenbert

0
Login to vote
BigRedAV's picture

will do. where is that download. i downloaded the link at the top of the post and installed it. its showing to 1.0.0 version

0
Login to vote
Screenbert's picture

Uninstall your current one and download the one using the same link again. The file has been updated. you can verify the file version on the PCADIAG.EXE file.

Screenbert

0
Login to vote
mike_plichta's picture

We have PCA quick connect setup to launch from the Altiris DS 6.9 console using instructions from this article.

https://www-secure.symantec.com/connect/forums/pca...

My only goal to launch PCA quick connect from the DS and have it not prompt for credentials (storing them somewhere). All the machines use the same account to connect or alternatively use the credentials of the logged on user. Your solution would help a little, but we'd still need to copy/paste the comptuer name into it to get it to work. Not only that but it doesn't seem to be working in Windows 7 SP1 with IE9. I even tried running it in XP SP3 compat mode and checked the run as admin box. Here's the error.

Unhandled exception - Cannot create ActiveX component.

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.Exception: Cannot create ActiveX component.
at Microsoft.VisualBasic.Interaction.CreateObject(String ProgId, String ServerName)
at PCACDLL.PCAC.CreateCHFFile(String strPCName, String strUsername, String strPassword, String strCHFName, String strCHFFolder)
at pcADiag.Form1.btnConnect_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5444 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50...
----------------------------------------
pcADiag
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Program%20Files/pcADiag/pcADiag.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Window...
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0....
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawin...
----------------------------------------
System.Core
Assembly Version: 3.5.0.0
Win32 Version: 3.5.30729.5420 built by: Win7SP1
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Core/3...
----------------------------------------
System.Data
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_32/System.Data/2.0...
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2....
----------------------------------------
PCACDLL
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Program%20Files/pcADiag/PCACDLL.DLL
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.Vis...
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

0
Login to vote
Screenbert's picture

Can you use the quickconnect client on the DS machine? PCA has to be installed on the PC you are running it from. If it is, what version of .net do you have installed?

Screenbert

0
Login to vote
BHASKARB's picture

Hi,

Thanku you so much Gonna this tools very usefull for the troubleshooting... 

0
Login to vote
rweiss77's picture

Can you check the code again?   The code on the link is still 1.0 not v1.0014.  I'm interested in testing the app as a workaround for an issue I'm having enterprise wide and security but I'm getting the JIT errors assocatiated with 1.0. 

 Thanks a bunch.

0
Login to vote
mlombardo's picture

Screenbert,

I can't seem to get this to work when I point it at my PCA Access server. I get a message that states "Cannot open Service Control Manager on computer '<REMOTE HOST>.'  Is there any way to use this in conjunction with SMP/PCA Access Server?

Thanks!

Mike

0
Login to vote
RickGuti's picture

Hi people.

How can I solve that? I can connect normally, but is very slow...

192.168.9.168 - 11:15:27 AM: Ping Address: 192.168.9.168 bytes=32 time=0 TTL=128
192.168.9.168 - 11:15:27 AM: Verifying the Symantec pcAnywhere Host Service exists.
192.168.9.168 - 11:15:27 AM: Symantec pcAnywhere Host Service exists.
192.168.9.168 - 11:15:27 AM: Symantec pcAnywhere Host Service is running.
192.168.9.168 - 11:15:27 AM: Symantec pcAnywhere Port 5631 is open and accepting connections.(TECH107919)
192.168.9.168 - 11:15:27 AM: Checking if pcAAgent.dll is registered.
192.168.9.168 - 11:15:40 AM: pcAAgent.dll failed to register.
192.168.9.168 - 11:15:40 AM: Checking Authentication speed fix.(TECH109926)
192.168.9.168 - 11:15:41 AM: Unable to check for speed fix.
192.168.9.168 - 11:15:41 AM: Checking last configuration request.
192.168.9.168 - 11:15:41 AM: Unable to check last configuration request.
192.168.9.168 - 11:15:41 AM: ----------------------------------------------------------------------------------------------------------------------------------

Thanks.

0
Login to vote
SeidKrvavac's picture

RickGuti,

Try this:

Check if the pcaAAgent.dll is located in:

C:\Program Files (x86)\Symantec\pcAnywhere

or

C:\Program Files\Symantec\pcAnywhere

If not a workaround to solve the problem on one computer is by copying the dll file from another computer (must be from the same OS and platform to be sure) to the pcanywhere folder and from that folder run this command:

regsvr32 pcAAgent.dll

This problem seems to happen if the "Run once ASAP" is checked for the plugin installation, so remove that  and instead create a scedule window for compliance check.

0
Login to vote
GodzFire's picture

This program is a godsent. Please don't tell me that development has stopped.

0
Login to vote
koen1's picture

Great tool!
It's too bad that Symantec doesn't provide anything with Single Sign On:
http://www.symantec.com/connect/idea/pcanywhere-authentication-can-pass-logged-user-pca-authentication

Since we only intend to use this tool as a work-around for reentering credentials, it would be great if we had a tool with only the "Connect"-option.

Also it takes some time for the pcA QuickConnect to open, is there a possibility for pcA Diag to give some feedback when the connect-button is pressed? Something like "Connecting to %hostname%..."

0
Login to vote
reto.zuerrer's picture

This tool works also with the newest pcanywhere solution 12.6.7!

Reto Zürrer | FYRE Consulting | http://www.fyre-consulting.ch

0
Login to vote
cosp's picture

We try to use pcADiag 1.0.0.0  on a Swedish client Win 7 64bit and get this error. 

 "translated log to english by google translate"

Its ok on XP and Win7 32bit

2409 - 14:40:47: Ping Address: 10.38.119.38 bytes=32 time=0 TTL=126
2409 - 14:40:47: Verifying the Symantec pcAnywhere Host Service exists.
2409 - 14:40:47: Symantec pcAnywhere Host Service exists.
2409 - 14:40:47: Symantec pcAnywhere Host Service is running.
2409 - 14:40:47: Symantec pcAnywhere Port 5631 is open and accepting connections.(TECH107919)
2409 - 14:40:47: Checking if pcAAgent.dll is registered.
2409 - 14:40:47: pcAAgent.dll is already registered.
2409 - 14:40:47: Checking Authentication speed fix.(TECH109926)
2409 - 14:40:47: Authentication speed fix already configured.
2409 - 14:40:47: Checking last configuration request.
2409 - 14:40:47: Last configuration request was on 2012-06-11 14:03:16.
2409 - 14:40:47: ----------------------------------------------------------------------------------------------------------------------------------
 

Information on enabling JIT debugging instead of the
This dialog box at the end of this message.

************** Exception Text **************
System.Exception: Could not create ActiveX component.
   at Microsoft.VisualBasic.Interaction.CreateObject (String ProgID, String ServerName)
   at PCACDLL.PCAC.CreateCHFFile (String strPCName, strUsername String, String strPassword, String strCHFName, String strCHFFolder)
   at pcADiag.Form1.btnConnect_Click (Object sender, EventArgs e)
   at System.Windows.Forms.Control.OnClick (EventArgs e)
   in System.Windows.Forms.Button.OnMouseUp (MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp (Message & m, Mouse Buttons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc (Message & m)
   at System.Windows.Forms.ButtonBase.WndProc (Message & m)
   at System.Windows.Forms.Button.WndProc (Message & m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc (Message & m)
   at System.Windows.Forms.NativeWindow.Callback (IntPtr hWnd, Int32 msg, IntPtr wParam, IntPtr lParam)

Loaded ************** compositions **************
mscorlib
    Assembly Version: 2.0.0.0
    Win32 version: 2.0.50727.5456 (Win7SP1GDR.050727-5400)
    Codebase: file :/ / / C :/ Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll
----------------------------------------
pcADiag
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    Codebase: file :/ / / C :/ Program% 20Files% 20 (x86) / pcADiag / pcADiag.exe
----------------------------------------
System.windows.forms
    Assembly Version: 2.0.0.0
    Win32 version: 2.0.50727.5456 (Win7SP1GDR.050727-5400)
    Code Base:
----------------------------------------
System
    Assembly Version: 2.0.0.0
    Win32 version: 2.0.50727.5456 (Win7SP1GDR.050727-5400)
    Codebase: file :/ / / C :/ Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
    Assembly Version: 2.0.0.0
    Win32 version: 2.0.50727.5458 (Win7SP1GDR.050727-5400)
    Codebase: file :/ / / C :/ Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Windows.Forms.resources
    Assembly Version: 2.0.0.0
    Win32 version: 2.0.50727.5420 (Win7SP1.050727-5400)
    Code Base:
----------------------------------------
System.Core
    Assembly Version: 3.5.0.0
    Win32 version: 3.5.30729.5420 built by: Win7SP1
    Codebase: file :/ / / C :/ Windows/assembly/GAC_MSIL/System.Core/3.5.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Data
    Assembly Version: 2.0.0.0
    Win32 version: 2.0.50727.5420 (Win7SP1.050727-5400)
    Codebase: file :/ / / C :/ Windows/assembly/GAC_64/System.Data/2.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
System.Xml
    Assembly Version: 2.0.0.0
    Win32 version: 2.0.50727.5420 (Win7SP1.050727-5400)
    Codebase: file :/ / / C :/ Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
PCACDLL
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    Codebase: file :/ / / C :/ Program% 20Files% 20 (x86) / pcADiag / PCACDLL.DLL
----------------------------------------
Microsoft.VisualBasic
    Assembly Version: 8.0.0.0
    Win32 version: 8.0.50727.5420 (Win7SP1.050727-5400)
    Code Base:
----------------------------------------
mscorlib.resources
    Assembly Version: 2.0.0.0
    Win32 version: 2.0.50727.5456 (Win7SP1GDR.050727-5400)
    Codebase: file :/ / / C :/ Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll
----------------------------------------
Microsoft.VisualBasic.resources
    Assembly Version: 8.0.0.0
    Win32 version: 8.0.50727.4927 (NetFXspW7.050727-4900)
    Code Base:
----------------------------------------
System.Configuration
    Assembly Version: 2.0.0.0
    Win32 version: 2.0.50727.5420 (Win7SP1.050727-5400)
    Code Base:
----------------------------------------
System.ServiceProcess
    Assembly Version: 2.0.0.0
    Win32 version: 2.0.50727.5420 (Win7SP1.050727-5400)
    Code Base:
----------------------------------------

************** JIT debugging **************
To enable the JIT debugging (just-in-time) must. Config file
this application or computer (machine.config) must have
jitDebugging value set in the system.windows.forms section.
The application must also be compiled
with debugging enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</ Configuration>

When JIT debugging is enabled, any exceptions that do not
handled will be sent to the JIT debugger registered on
computer rather than be handled by this dialog.

 
 
 
 
 
Klicka om du vill visa och redigera alternativa översättningar
 
 
Ändra ordning genom att dra med Skift-tangenten.
 
 
0
Login to vote
CygnusX-1's picture

We are also getting an error on Win 7 x64

Unhandled exception has occurred in your application.  If you click Continue, the application will ignore this error and attempt to continue.  If you click Quit, the application will close immediately.

Cannot create ActiveX component.

----------------------------------------------

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.Exception: Cannot create ActiveX component.
   at Microsoft.VisualBasic.Interaction.CreateObject(String ProgId, String ServerName)
   at PCACDLL.PCAC.CreateCHFFile(String strPCName, String strUsername, String strPassword, String strCHFName, String strCHFFolder)
   at pcADiag.Form1.btnConnect_Click(Object sender, EventArgs e)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

************** Loaded Assemblies **************
mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5466 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll
----------------------------------------
pcADiag
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Program%20Files%20(x86)/pcADiag/pcADiag.exe
----------------------------------------
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5468 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Core
    Assembly Version: 3.5.0.0
    Win32 Version: 3.5.30729.5420 built by: Win7SP1
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Core/3.5.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Data
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_64/System.Data/2.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
System.Xml
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
PCACDLL
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Program%20Files%20(x86)/pcADiag/PCACDLL.DLL
----------------------------------------
Microsoft.VisualBasic
    Assembly Version: 8.0.0.0
    Win32 Version: 8.0.50727.5420 (Win7SP1.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

0
Login to vote
Screenbert's picture

This error happens when the PC Anywhere host isn't installed on the machine you are running the tool from.

Screenbert

0
Login to vote
CygnusX-1's picture

Must be a version change because I can see the Symantec pcAnywhere Host Service running in Services and I still get this error.

0
Login to vote