473,394 Members | 1,750 Online
Bytes | Software Development & Data Engineering Community
Post Job

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 473,394 software developers and data experts.

Win2003 won't run my application

I have a Win2003 server where I installed my VB.NET application, built
with VS.NET 2002.

My main application crashes before the first line of my code is
executed with this error: "Memory at location ... could not be read."

All my additional tools that I built for my application work fine.

When I log on as administrator everything works fine but as soon as I
log on with a normal user account the crash occurs. This looks like a
permission issue but which permission?
Does anyone have an idea why this is happening.?

Tosch
Jul 21 '05 #1
13 1944
W2K comes with .NET v1.1 preinstalled, your application is build for .NET
v1.0. Did you tested your application on v1.1 before deploying?

Willy.
"Tosch" <to**********@swissonline.ch> wrote in message
news:k8********************************@4ax.com...
I have a Win2003 server where I installed my VB.NET application, built
with VS.NET 2002.

My main application crashes before the first line of my code is
executed with this error: "Memory at location ... could not be read."

All my additional tools that I built for my application work fine.

When I log on as administrator everything works fine but as soon as I
log on with a normal user account the crash occurs. This looks like a
permission issue but which permission?
Does anyone have an idea why this is happening.?

Tosch

Jul 21 '05 #2
W2K comes with .NET v1.1 preinstalled, your application is build for .NET
v1.0. Did you tested your application on v1.1 before deploying?

Willy.
"Tosch" <to**********@swissonline.ch> wrote in message
news:k8********************************@4ax.com...
I have a Win2003 server where I installed my VB.NET application, built
with VS.NET 2002.

My main application crashes before the first line of my code is
executed with this error: "Memory at location ... could not be read."

All my additional tools that I built for my application work fine.

When I log on as administrator everything works fine but as soon as I
log on with a normal user account the crash occurs. This looks like a
permission issue but which permission?
Does anyone have an idea why this is happening.?

Tosch

Jul 21 '05 #3
Willy,
yes I did that a while ago. My application doesn't even come as far as
displaying my splash screen.

Tosch
On Mon, 3 May 2004 13:43:47 +0200, "Willy Denoyette [MVP]"
<wi*************@pandora.be> wrote:
W2K comes with .NET v1.1 preinstalled, your application is build for .NET
v1.0. Did you tested your application on v1.1 before deploying?

Willy.
"Tosch" <to**********@swissonline.ch> wrote in message
news:k8********************************@4ax.com.. .
I have a Win2003 server where I installed my VB.NET application, built
with VS.NET 2002.

My main application crashes before the first line of my code is
executed with this error: "Memory at location ... could not be read."

All my additional tools that I built for my application work fine.

When I log on as administrator everything works fine but as soon as I
log on with a normal user account the crash occurs. This looks like a
permission issue but which permission?
Does anyone have an idea why this is happening.?

Tosch


Jul 21 '05 #4
Willy,
yes I did that a while ago. My application doesn't even come as far as
displaying my splash screen.

Tosch
On Mon, 3 May 2004 13:43:47 +0200, "Willy Denoyette [MVP]"
<wi*************@pandora.be> wrote:
W2K comes with .NET v1.1 preinstalled, your application is build for .NET
v1.0. Did you tested your application on v1.1 before deploying?

Willy.
"Tosch" <to**********@swissonline.ch> wrote in message
news:k8********************************@4ax.com.. .
I have a Win2003 server where I installed my VB.NET application, built
with VS.NET 2002.

My main application crashes before the first line of my code is
executed with this error: "Memory at location ... could not be read."

All my additional tools that I built for my application work fine.

When I log on as administrator everything works fine but as soon as I
log on with a normal user account the crash occurs. This looks like a
permission issue but which permission?
Does anyone have an idea why this is happening.?

Tosch


Jul 21 '05 #5
How about a simple windows forms application with an empty form?
Did you try to remove the splash screen?

Willy.

"Tosch" <to**********@swissonline.ch> wrote in message
news:dp********************************@4ax.com...
Willy,
yes I did that a while ago. My application doesn't even come as far as
displaying my splash screen.

Tosch
On Mon, 3 May 2004 13:43:47 +0200, "Willy Denoyette [MVP]"
<wi*************@pandora.be> wrote:
W2K comes with .NET v1.1 preinstalled, your application is build for .NET
v1.0. Did you tested your application on v1.1 before deploying?

Willy.
"Tosch" <to**********@swissonline.ch> wrote in message
news:k8********************************@4ax.com. ..
I have a Win2003 server where I installed my VB.NET application, built
with VS.NET 2002.

My main application crashes before the first line of my code is
executed with this error: "Memory at location ... could not be read."

All my additional tools that I built for my application work fine.

When I log on as administrator everything works fine but as soon as I
log on with a normal user account the crash occurs. This looks like a
permission issue but which permission?
Does anyone have an idea why this is happening.?

Tosch

Jul 21 '05 #6
How about a simple windows forms application with an empty form?
Did you try to remove the splash screen?

Willy.

"Tosch" <to**********@swissonline.ch> wrote in message
news:dp********************************@4ax.com...
Willy,
yes I did that a while ago. My application doesn't even come as far as
displaying my splash screen.

Tosch
On Mon, 3 May 2004 13:43:47 +0200, "Willy Denoyette [MVP]"
<wi*************@pandora.be> wrote:
W2K comes with .NET v1.1 preinstalled, your application is build for .NET
v1.0. Did you tested your application on v1.1 before deploying?

Willy.
"Tosch" <to**********@swissonline.ch> wrote in message
news:k8********************************@4ax.com. ..
I have a Win2003 server where I installed my VB.NET application, built
with VS.NET 2002.

My main application crashes before the first line of my code is
executed with this error: "Memory at location ... could not be read."

All my additional tools that I built for my application work fine.

When I log on as administrator everything works fine but as soon as I
log on with a normal user account the crash occurs. This looks like a
permission issue but which permission?
Does anyone have an idea why this is happening.?

Tosch

Jul 21 '05 #7
All my tools (5 or 6 winform exes) run fine.

It's just my main app that crashes. I don't think it has anything to
do with the splash screen. It just displays a logo and a few labels.

My tools have more complex forms with 3rd party grids etc and they
work fine. Also sql server access works fine

I have set full control on all files on my drive and all the keys in
the registry (HKLM) for this user, no change.

I'll try and put a MsgBox() as the first line in my code and see what
happens.

Tosch
On Mon, 3 May 2004 19:37:31 +0200, "Willy Denoyette [MVP]"
<wi*************@pandora.be> wrote:
How about a simple windows forms application with an empty form?
Did you try to remove the splash screen?

Willy.

"Tosch" <to**********@swissonline.ch> wrote in message
news:dp********************************@4ax.com.. .
Willy,
yes I did that a while ago. My application doesn't even come as far as
displaying my splash screen.

Tosch
On Mon, 3 May 2004 13:43:47 +0200, "Willy Denoyette [MVP]"
<wi*************@pandora.be> wrote:
W2K comes with .NET v1.1 preinstalled, your application is build for .NET
v1.0. Did you tested your application on v1.1 before deploying?

Willy.
"Tosch" <to**********@swissonline.ch> wrote in message
news:k8********************************@4ax.com ...
I have a Win2003 server where I installed my VB.NET application, built
with VS.NET 2002.

My main application crashes before the first line of my code is
executed with this error: "Memory at location ... could not be read."

All my additional tools that I built for my application work fine.

When I log on as administrator everything works fine but as soon as I
log on with a normal user account the crash occurs. This looks like a
permission issue but which permission?
Does anyone have an idea why this is happening.?

Tosch


Jul 21 '05 #8
All my tools (5 or 6 winform exes) run fine.

It's just my main app that crashes. I don't think it has anything to
do with the splash screen. It just displays a logo and a few labels.

My tools have more complex forms with 3rd party grids etc and they
work fine. Also sql server access works fine

I have set full control on all files on my drive and all the keys in
the registry (HKLM) for this user, no change.

I'll try and put a MsgBox() as the first line in my code and see what
happens.

Tosch
On Mon, 3 May 2004 19:37:31 +0200, "Willy Denoyette [MVP]"
<wi*************@pandora.be> wrote:
How about a simple windows forms application with an empty form?
Did you try to remove the splash screen?

Willy.

"Tosch" <to**********@swissonline.ch> wrote in message
news:dp********************************@4ax.com.. .
Willy,
yes I did that a while ago. My application doesn't even come as far as
displaying my splash screen.

Tosch
On Mon, 3 May 2004 13:43:47 +0200, "Willy Denoyette [MVP]"
<wi*************@pandora.be> wrote:
W2K comes with .NET v1.1 preinstalled, your application is build for .NET
v1.0. Did you tested your application on v1.1 before deploying?

Willy.
"Tosch" <to**********@swissonline.ch> wrote in message
news:k8********************************@4ax.com ...
I have a Win2003 server where I installed my VB.NET application, built
with VS.NET 2002.

My main application crashes before the first line of my code is
executed with this error: "Memory at location ... could not be read."

All my additional tools that I built for my application work fine.

When I log on as administrator everything works fine but as soon as I
log on with a normal user account the crash occurs. This looks like a
permission issue but which permission?
Does anyone have an idea why this is happening.?

Tosch


Jul 21 '05 #9
Willy,

it turns out my application starts 'ok' but one of the first things I
do is to check if the same application already runs.

The line: p =
Diagnostics.Process.GetProcessesByName(Diagnostics .Process.GetCurrentProcess.ProcessName)

is where my application crashes, no Try/Catch help in this case.

I have now added a commandline option to bypass this check since I
could not find out what is causing this line to crash.
Any ideas?

Tosch

On Mon, 3 May 2004 19:37:31 +0200, "Willy Denoyette [MVP]"
<wi*************@pandora.be> wrote:
How about a simple windows forms application with an empty form?
Did you try to remove the splash screen?

Willy.

"Tosch" <to**********@swissonline.ch> wrote in message
news:dp********************************@4ax.com.. .
Willy,
yes I did that a while ago. My application doesn't even come as far as
displaying my splash screen.

Tosch
On Mon, 3 May 2004 13:43:47 +0200, "Willy Denoyette [MVP]"
<wi*************@pandora.be> wrote:
W2K comes with .NET v1.1 preinstalled, your application is build for .NET
v1.0. Did you tested your application on v1.1 before deploying?

Willy.
"Tosch" <to**********@swissonline.ch> wrote in message
news:k8********************************@4ax.com ...
I have a Win2003 server where I installed my VB.NET application, built
with VS.NET 2002.

My main application crashes before the first line of my code is
executed with this error: "Memory at location ... could not be read."

All my additional tools that I built for my application work fine.

When I log on as administrator everything works fine but as soon as I
log on with a normal user account the crash occurs. This looks like a
permission issue but which permission?
Does anyone have an idea why this is happening.?

Tosch


Jul 21 '05 #10
Sure, don't use this hack to check if another instance is running, it breaks
on TS as you noticed.
Use a (Global) named mutex to prevent running multiple instances.

Willy.

"Tosch" <to**********@swissonline.ch> wrote in message
news:q3********************************@4ax.com...
Willy,

it turns out my application starts 'ok' but one of the first things I
do is to check if the same application already runs.

The line: p =
Diagnostics.Process.GetProcessesByName(Diagnostics .Process.GetCurrentProcess.ProcessName)

is where my application crashes, no Try/Catch help in this case.

I have now added a commandline option to bypass this check since I
could not find out what is causing this line to crash.
Any ideas?

Tosch

On Mon, 3 May 2004 19:37:31 +0200, "Willy Denoyette [MVP]"
<wi*************@pandora.be> wrote:
How about a simple windows forms application with an empty form?
Did you try to remove the splash screen?

Willy.

"Tosch" <to**********@swissonline.ch> wrote in message
news:dp********************************@4ax.com. ..
Willy,
yes I did that a while ago. My application doesn't even come as far as
displaying my splash screen.

Tosch
On Mon, 3 May 2004 13:43:47 +0200, "Willy Denoyette [MVP]"
<wi*************@pandora.be> wrote:

W2K comes with .NET v1.1 preinstalled, your application is build for
.NET
v1.0. Did you tested your application on v1.1 before deploying?

Willy.
"Tosch" <to**********@swissonline.ch> wrote in message
news:k8********************************@4ax.co m...
>I have a Win2003 server where I installed my VB.NET application, built
> with VS.NET 2002.
>
> My main application crashes before the first line of my code is
> executed with this error: "Memory at location ... could not be read."
>
> All my additional tools that I built for my application work fine.
>
> When I log on as administrator everything works fine but as soon as I
> log on with a normal user account the crash occurs. This looks like a
> permission issue but which permission?
>
>
> Does anyone have an idea why this is happening.?
>
> Tosch

Jul 21 '05 #11
But I have the same code installed in about 70 client sites and it has
always worked fine even on Win2000 Terminal Server installations.

Tosch

On Tue, 4 May 2004 14:55:18 +0200, "Willy Denoyette [MVP]"
<wi*************@pandora.be> wrote:
Sure, don't use this hack to check if another instance is running, it breaks
on TS as you noticed.
Use a (Global) named mutex to prevent running multiple instances.

Willy.

"Tosch" <to**********@swissonline.ch> wrote in message
news:q3********************************@4ax.com.. .
Willy,

it turns out my application starts 'ok' but one of the first things I
do is to check if the same application already runs.

The line: p =
Diagnostics.Process.GetProcessesByName(Diagnostics .Process.GetCurrentProcess.ProcessName)

is where my application crashes, no Try/Catch help in this case.

I have now added a commandline option to bypass this check since I
could not find out what is causing this line to crash.
Any ideas?

Tosch

On Mon, 3 May 2004 19:37:31 +0200, "Willy Denoyette [MVP]"
<wi*************@pandora.be> wrote:
How about a simple windows forms application with an empty form?
Did you try to remove the splash screen?

Willy.

"Tosch" <to**********@swissonline.ch> wrote in message
news:dp********************************@4ax.com ...
Willy,
yes I did that a while ago. My application doesn't even come as far as
displaying my splash screen.

Tosch
On Mon, 3 May 2004 13:43:47 +0200, "Willy Denoyette [MVP]"
<wi*************@pandora.be> wrote:

>W2K comes with .NET v1.1 preinstalled, your application is build for
>.NET
>v1.0. Did you tested your application on v1.1 before deploying?
>
>Willy.
>"Tosch" <to**********@swissonline.ch> wrote in message
>news:k8********************************@4ax.c om...
>>I have a Win2003 server where I installed my VB.NET application, built
>> with VS.NET 2002.
>>
>> My main application crashes before the first line of my code is
>> executed with this error: "Memory at location ... could not be read."
>>
>> All my additional tools that I built for my application work fine.
>>
>> When I log on as administrator everything works fine but as soon as I
>> log on with a normal user account the crash occurs. This looks like a
>> permission issue but which permission?
>>
>>
>> Does anyone have an idea why this is happening.?
>>
>> Tosch
>


Jul 21 '05 #12
I would look at the local security policy and focus on items where
Administrator rights differ from the user you are trying to run this as.
Try to give the user "Debug Programs" rights.
Jul 21 '05 #13
Not sure why this fails for you. IMO No special privileges are required by
this...
Diagnostics.Process.GetProcessesByName(Diagnostics .Process.GetCurrentProcess().ProcessName)
It works for me from a Terminal session on W2K3.
Some API's in the System.Diagnostics namespace require seDebugPrivileges,
only administrators have this privilege (however, on W2K3 and W2K this
privileges was revoked by applying ms03-43), therefore it is advisable to
use a global mutex instead of searching for the name of a running program.

Willy.

"Tosch" <to**********@swissonline.ch> wrote in message
news:71********************************@4ax.com...
But I have the same code installed in about 70 client sites and it has
always worked fine even on Win2000 Terminal Server installations.

Tosch

On Tue, 4 May 2004 14:55:18 +0200, "Willy Denoyette [MVP]"
<wi*************@pandora.be> wrote:
Sure, don't use this hack to check if another instance is running, it
breaks
on TS as you noticed.
Use a (Global) named mutex to prevent running multiple instances.

Willy.

"Tosch" <to**********@swissonline.ch> wrote in message
news:q3********************************@4ax.com. ..
Willy,

it turns out my application starts 'ok' but one of the first things I
do is to check if the same application already runs.

The line: p =
Diagnostics.Process.GetProcessesByName(Diagnostics .Process.GetCurrentProcess.ProcessName)

is where my application crashes, no Try/Catch help in this case.

I have now added a commandline option to bypass this check since I
could not find out what is causing this line to crash.
Any ideas?

Tosch

On Mon, 3 May 2004 19:37:31 +0200, "Willy Denoyette [MVP]"
<wi*************@pandora.be> wrote:

How about a simple windows forms application with an empty form?
Did you try to remove the splash screen?

Willy.

"Tosch" <to**********@swissonline.ch> wrote in message
news:dp********************************@4ax.co m...
> Willy,
> yes I did that a while ago. My application doesn't even come as far as
> displaying my splash screen.
>
> Tosch
>
>
> On Mon, 3 May 2004 13:43:47 +0200, "Willy Denoyette [MVP]"
> <wi*************@pandora.be> wrote:
>
>>W2K comes with .NET v1.1 preinstalled, your application is build for
>>.NET
>>v1.0. Did you tested your application on v1.1 before deploying?
>>
>>Willy.
>>"Tosch" <to**********@swissonline.ch> wrote in message
>>news:k8********************************@4ax. com...
>>>I have a Win2003 server where I installed my VB.NET application,
>>>built
>>> with VS.NET 2002.
>>>
>>> My main application crashes before the first line of my code is
>>> executed with this error: "Memory at location ... could not be
>>> read."
>>>
>>> All my additional tools that I built for my application work fine.
>>>
>>> When I log on as administrator everything works fine but as soon as
>>> I
>>> log on with a normal user account the crash occurs. This looks like
>>> a
>>> permission issue but which permission?
>>>
>>>
>>> Does anyone have an idea why this is happening.?
>>>
>>> Tosch
>>
>

Jul 21 '05 #14

This thread has been closed and replies have been disabled. Please start a new discussion.

Similar topics

0
by: Joe | last post by:
When we run our application under win2003 it requires us to register all serviced components. The web application gets an exception either on the registry our on IComCatalog save changes when we...
2
by: Belinda | last post by:
I am trying to setup a COM+ application that runs some ASP applications. The application vendor is telling me on my Win2003 server that COM+ and ASP as not been properly setup. Can any of you...
0
by: Johanna | last post by:
Hello, Thread was being aborted exception is thrown by my asp.net application. I hope someone could help me with this error that I get in windows 2003 server. This error has not occured with...
3
by: Johanna | last post by:
Hello, Thread was being aborted exception is thrown by IIS for my asp.net application on win2003 server. This error has not yet occured with the same asp.net application on windows 2000...
1
by: Jody Gelowitz | last post by:
We are having an issue in that when trying to read a file that is on Server2 from Server1 (through our ASP.NET project), we receive the error: Access to the path "\\Server2\MyShare\MyFile.tif" is...
9
by: Tosch | last post by:
I have a Win2003 server where I installed my VB.NET application, built with VS.NET 2002. My main application crashes before the first line of my code is executed with this error: "Memory at...
0
by: ee_stevek | last post by:
hi guys, here is my problem: i have to maintain a web vb.net application developped some times ago. The application was developped on Windows2000 SP3 with Visual Studio 2003 (7.1). and the...
2
by: Don Rich | last post by:
Please share with me any ideas you may have for troubleshooting and resolving the subject problem. I can give more details as necessary. (Please advise if I should post this problem to a more...
1
Carrugar
by: Carrugar | last post by:
I'm having a major problem with an ASP application. Our ASP code has been migrated from NT4 (IIS4.0) to a Win2003 (IIS6.0) server. However, there seems to be a problem with the VB scripts. Whenever a...
0
by: Charles Arthur | last post by:
How do i turn on java script on a villaon, callus and itel keypad mobile phone
0
by: ryjfgjl | last post by:
If we have dozens or hundreds of excel to import into the database, if we use the excel import function provided by database editors such as navicat, it will be extremely tedious and time-consuming...
0
BarryA
by: BarryA | last post by:
What are the essential steps and strategies outlined in the Data Structures and Algorithms (DSA) roadmap for aspiring data scientists? How can individuals effectively utilize this roadmap to progress...
1
by: nemocccc | last post by:
hello, everyone, I want to develop a software for my android phone for daily needs, any suggestions?
0
by: Hystou | last post by:
There are some requirements for setting up RAID: 1. The motherboard and BIOS support RAID configuration. 2. The motherboard has 2 or more available SATA protocol SSD/HDD slots (including MSATA, M.2...
0
marktang
by: marktang | last post by:
ONU (Optical Network Unit) is one of the key components for providing high-speed Internet services. Its primary function is to act as an endpoint device located at the user's premises. However,...
0
Oralloy
by: Oralloy | last post by:
Hello folks, I am unable to find appropriate documentation on the type promotion of bit-fields when using the generalised comparison operator "<=>". The problem is that using the GNU compilers,...
0
jinu1996
by: jinu1996 | last post by:
In today's digital age, having a compelling online presence is paramount for businesses aiming to thrive in a competitive landscape. At the heart of this digital strategy lies an intricately woven...
0
by: Hystou | last post by:
Overview: Windows 11 and 10 have less user interface control over operating system update behaviour than previous versions of Windows. In Windows 11 and 10, there is no way to turn off the Windows...

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.