Anyone seen some of these problems on Win2K + SP5?

[numerous instabilities in deploying VB]

I have been working on a VB product It is working beautifuly on my XP dev box and my windows 2000 test machines in the lab.

When I install at the customer site, I get all kinds of wacky problems that I CANT reproduce in the lab.
1) Some customer PC's can't use ANY functions related to Process = Process.GetProcessById(ProcessID) !!!! - I am resorting to using a 3rd party product to kill process.
2) Sometimes applications will just die before starting up and generate a DR. Watson error in the Application Log.

Has anyone seen anything similar? Plugging into the customers network to debug could be rolls and rolls of red tape. I am getting really stuck trying to figure out what to try next.

[solex]

What is the security set to in the client's pc?
"numerous instabilities in deploying VB"
<an*******@discussions.microsoft.com> wrote in message
news:1E**********************************@microsof t.com...

I have been working on a VB product It is working beautifuly on my XP dev box and my windows 2000 test machines in the lab.
When I install at the customer site, I get all kinds of wacky problems that I CANT reproduce in the lab. 1) Some customer PC's can't use ANY functions related to Process = Process.GetProcessById(ProcessID) !!!! - I am resorting to using a 3rd
party product to kill process. 2) Sometimes applications will just die before starting up and generate a DR. Watson error in the Application Log.
Has anyone seen anything similar? Plugging into the customers network to debug could be rolls and rolls of red tape. I am getting really stuck
trying to figure out what to try next.

[Greg]

Wich security setting are you refering too

[ritchie]

> When I install at the customer site, I get all kinds of wacky problems
that I CANT reproduce in the lab.

1) Some customer PC's can't use ANY functions related to Process =

Process.GetProcessById(ProcessID) !!!! - I am resorting to using a 3rd
party product to kill process.

I had similar problems (i.e. not being able to access Process methods) in
machines were
the perfomance counters were corrupted or missing.
You can check that by launching Perfomance Monitor from the Control
Panel/Administrative Tools.

A fix is here:
http://support.microsoft.com/default...&Product=win20
00

[solex]

The dot net security settings. In the control panel look at the "Microsoft
..NET Framework 1.1 Wizards" and make sure that the .NET Security for "My
Computer" is set to "Full Trust"

Dan

"Greg" <an*******@discussions.microsoft.com> wrote in message
news:93**********************************@microsof t.com...

Wich security setting are you refering too?