SyncToy won't load

[Guest]

Every time I try to start SyncToy, I get a "common language debugging
services" message, "application has generated an exception that could not be
handled. process id=0xc50 (3152), thread id=0x504 (1284)." I have searched
the msft database for these error codes, but I get no response.

Does anyone have any ideas?

On my home computer, this program works well.

 

[Burgy]

Others of us have that same problem. See (synctoy won't run) thread. It
seems there are not enough of us to warrant them trying for a fix.

I just uninstalled the program.

 

[Guest]

Hello Bart,

See if this helps from a similar post under "SyncToy Won't Run"

Strong et al,

Nice call Strong! This is reproducible. I can recreate the exception by
disabling performance counters for PerfProc.dll. Enabling that perf counter
enables SyncToy to run.

We will take a look at alternative means of determining whether SyncToy is
already running for possible inclusion in a future release.

For those interested, the registry entry for PerfProc is:

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\PerfProc\Performance

As you might expect, the Disable Performance Counteres REG_DWORD = 0 for not
disabled and = 1 for disabled.

Hi Jim

Could not run it eather and apparently it's because that performance
counters are disabled on my machine. Not sure why, but the following might
help.

System.InvalidOperationException
Additional information: Process performance counter is disabled, so the
requested operation cannot be performed.

Call stack:

system.dll!System.Diagnostics.NtProcessManager.GetProcessInfos(System.Diagnostics.PerformanceCounterLib library) + 0x1a5 bytes

system.dll!System.Diagnostics.NtProcessManager.GetProcessInfos(string
machineName, bool isRemoteMachine) + 0xa4 bytes
system.dll!System.Diagnostics.ProcessManager.GetProcessInfos(string
machineName) + 0x29 bytes

system.dll!System.Diagnostics.Process.EnsureState(System.Diagnostics.Process.State state) + 0x116 bytes
system.dll!System.Diagnostics.Process.get_ProcessName() + 0x11 bytes
SyncToy.exe!SyncToyUI.SyncToyUIForm.OtherInstanceRunning() + 0x17 bytes
SyncToy.exe!SyncToyUI.SyncToyUIForm.Main(string[] args) + 0xbb bytes

Hello Burgy,

I'm Jim, one of the program managers on the SyncToy project.

We haven't seen the error you're running into in any other circumstances
yet. Do you know what version of the .NET framework you have installed? Do
other applications that use the .NET runtime work on your machine?

Thanks!

 

[Guest]

I just downloaded SyncToy and encountered this same problem, however the
"fix" made no difference.
Are there any other knwon causes?
Ken

Hello Bart,

See if this helps from a similar post under "SyncToy Won't Run"

Strong et al,

Nice call Strong! This is reproducible. I can recreate the exception by
disabling performance counters for PerfProc.dll. Enabling that perf counter
enables SyncToy to run.

We will take a look at alternative means of determining whether SyncToy is
already running for possible inclusion in a future release.

For those interested, the registry entry for PerfProc is:

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\PerfProc\Performance

As you might expect, the Disable Performance Counteres REG_DWORD = 0 for not
disabled and = 1 for disabled.

Hi Jim

Could not run it eather and apparently it's because that performance
counters are disabled on my machine. Not sure why, but the following might
help.

System.InvalidOperationException
Additional information: Process performance counter is disabled, so the
requested operation cannot be performed.

Call stack:

system.dll!System.Diagnostics.NtProcessManager.GetProcessInfos(System.Diagnostics.PerformanceCounterLib library) + 0x1a5 bytes

system.dll!System.Diagnostics.NtProcessManager.GetProcessInfos(string
machineName, bool isRemoteMachine) + 0xa4 bytes
system.dll!System.Diagnostics.ProcessManager.GetProcessInfos(string
machineName) + 0x29 bytes

system.dll!System.Diagnostics.Process.EnsureState(System.Diagnostics.Process.State state) + 0x116 bytes
system.dll!System.Diagnostics.Process.get_ProcessName() + 0x11 bytes
SyncToy.exe!SyncToyUI.SyncToyUIForm.OtherInstanceRunning() + 0x17 bytes
SyncToy.exe!SyncToyUI.SyncToyUIForm.Main(string[] args) + 0xbb bytes

Hello Burgy,

I'm Jim, one of the program managers on the SyncToy project.

We haven't seen the error you're running into in any other circumstances
yet. Do you know what version of the .NET framework you have installed? Do
other applications that use the .NET runtime work on your machine?

Thanks!

Every time I try to start SyncToy, I get a "common language debugging
services" message, "application has generated an exception that could not be
handled. process id=0xc50 (3152), thread id=0x504 (1284)." I have searched
the msft database for these error codes, but I get no response.

Does anyone have any ideas?

On my home computer, this program works well.

 

[Guest]

Update - the PerfStringBackup.ini fix from the other thread did work.
(the correct file was already on the PC, just running lodctr was enough)
Ken.

I just downloaded SyncToy and encountered this same problem, however the
"fix" made no difference.
Are there any other knwon causes?
Ken

Hello Bart,

See if this helps from a similar post under "SyncToy Won't Run"

Strong et al,

Nice call Strong! This is reproducible. I can recreate the exception by
disabling performance counters for PerfProc.dll. Enabling that perf counter
enables SyncToy to run.

We will take a look at alternative means of determining whether SyncToy is
already running for possible inclusion in a future release.

For those interested, the registry entry for PerfProc is:

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\PerfProc\Performance

As you might expect, the Disable Performance Counteres REG_DWORD = 0 for not
disabled and = 1 for disabled.

Hi Jim

Could not run it eather and apparently it's because that performance
counters are disabled on my machine. Not sure why, but the following might
help.

System.InvalidOperationException
Additional information: Process performance counter is disabled, so the
requested operation cannot be performed.

Call stack:
system.dll!System.Diagnostics.NtProcessManager.GetProcessInfos(System.Diagnostics.PerformanceCounterLib library) + 0x1a5 bytes
system.dll!System.Diagnostics.NtProcessManager.GetProcessInfos(string
machineName, bool isRemoteMachine) + 0xa4 bytes
system.dll!System.Diagnostics.ProcessManager.GetProcessInfos(string
machineName) + 0x29 bytes

system.dll!System.Diagnostics.Process.EnsureState(System.Diagnostics.Process.State state) + 0x116 bytes
system.dll!System.Diagnostics.Process.get_ProcessName() + 0x11 bytes
SyncToy.exe!SyncToyUI.SyncToyUIForm.OtherInstanceRunning() + 0x17 bytes
SyncToy.exe!SyncToyUI.SyncToyUIForm.Main(string[] args) + 0xbb bytes


:

Hello Burgy,

I'm Jim, one of the program managers on the SyncToy project.

We haven't seen the error you're running into in any other circumstances
yet. Do you know what version of the .NET framework you have installed? Do
other applications that use the .NET runtime work on your machine?

Thanks!

Every time I try to start SyncToy, I get a "common language debugging
services" message, "application has generated an exception that could not be
handled. process id=0xc50 (3152), thread id=0x504 (1284)." I have searched
the msft database for these error codes, but I get no response.

Does anyone have any ideas?

On my home computer, this program works well.

 

[Guest]

Apparently there is no "1 solution fits all" for this problem. I also have
the PerfStrignBackup.ini file on a notebook that SyncToy won't run on. I
tried running lodctr from the System32 Windows directory where it is located
and it didn't make a bit of difference. I had also tried enabling performance
counters in the registry, but it didn't help either.
--
Larry

Update - the PerfStringBackup.ini fix from the other thread did work.
(the correct file was already on the PC, just running lodctr was enough)
Ken.

I just downloaded SyncToy and encountered this same problem, however the
"fix" made no difference.
Are there any other knwon causes?
Ken

Hello Bart,

See if this helps from a similar post under "SyncToy Won't Run"

Strong et al,

Nice call Strong! This is reproducible. I can recreate the exception by
disabling performance counters for PerfProc.dll. Enabling that perf counter
enables SyncToy to run.

We will take a look at alternative means of determining whether SyncToy is
already running for possible inclusion in a future release.

For those interested, the registry entry for PerfProc is:

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\PerfProc\Performance

As you might expect, the Disable Performance Counteres REG_DWORD = 0 for not
disabled and = 1 for disabled.


:

Hi Jim

Could not run it eather and apparently it's because that performance
counters are disabled on my machine. Not sure why, but the following might
help.

System.InvalidOperationException
Additional information: Process performance counter is disabled, so the
requested operation cannot be performed.

Call stack:
system.dll!System.Diagnostics.NtProcessManager.GetProcessInfos(System.Diagnostics.PerformanceCounterLib library) + 0x1a5 bytes
system.dll!System.Diagnostics.NtProcessManager.GetProcessInfos(string
machineName, bool isRemoteMachine) + 0xa4 bytes
system.dll!System.Diagnostics.ProcessManager.GetProcessInfos(string
machineName) + 0x29 bytes

system.dll!System.Diagnostics.Process.EnsureState(System.Diagnostics.Process.State state) + 0x116 bytes
system.dll!System.Diagnostics.Process.get_ProcessName() + 0x11 bytes
SyncToy.exe!SyncToyUI.SyncToyUIForm.OtherInstanceRunning() + 0x17 bytes
SyncToy.exe!SyncToyUI.SyncToyUIForm.Main(string[] args) + 0xbb bytes


:

Hello Burgy,

I'm Jim, one of the program managers on the SyncToy project.

We haven't seen the error you're running into in any other circumstances
yet. Do you know what version of the .NET framework you have installed? Do
other applications that use the .NET runtime work on your machine?

Thanks!


:

Every time I try to start SyncToy, I get a "common language debugging
services" message, "application has generated an exception that could not be
handled. process id=0xc50 (3152), thread id=0x504 (1284)." I have searched
the msft database for these error codes, but I get no response.

Does anyone have any ideas?

On my home computer, this program works well.