terminal server and Access 2003 runtime

[Guest jay]

Setup: Windows SBS 2003 as domain controler, Windows Server Standard 2003 as

terminal server. Application to run is an Access mdb running under Access

runtime 2003. Terminal server locked down by group policy

(http://www.microsoft.com/windowsserver2003/techinfo/overview/lockdown.mspx)

Problem: Runs like a champ when I log in as Administrator in a console

session. Other users logging in as a terminal server session have Access

crash (with the "Send / Don't send to Microsoft" window popping up).

I've checked to make sure that the users have rights to the programs involved.

Any help???

Thanks in advance.

Jay

[Guest Patrick Rouse]

RE: terminal server and Access 2003 runtime

 

1. Temporarily disabe the GPOs to see if they are the cause of the problem

2. Try using Regmon & Filemon to determine why the app is not launching or

failing.

 

 

 

--

Patrick C. Rouse

Microsoft MVP - Terminal Server

Provision Networks VIP

Citrix Technology Professional

President - Session Computing Solutions, LLC

http://www.sessioncomputing.com

 

 

 

"jay" wrote:

> Setup: Windows SBS 2003 as domain controler, Windows Server Standard 2003 as

> terminal server. Application to run is an Access mdb running under Access

> runtime 2003. Terminal server locked down by group policy

> (http://www.microsoft.com/windowsserver2003/techinfo/overview/lockdown.mspx)

> Problem: Runs like a champ when I log in as Administrator in a console

> session. Other users logging in as a terminal server session have Access

> crash (with the "Send / Don't send to Microsoft" window popping up).

> I've checked to make sure that the users have rights to the programs involved.

> Any help???

> Thanks in advance.

> Jay

>

[Guest jay]

RE: terminal server and Access 2003 runtime

 

Thanks for the quick response. I disabled the terminal server group policy

and Access still crashes when a non-administrator runs it. I downloaded

Processmon in lieu of Filemon and RegMon but there are thousands of lines for

MSACCESS.EXE with results not = "Successful" with both successful runs logged

in as administrator and crashes when logged in as non-administrator.

I've given extended rights to my database users security group to MSACCESS

and to the mdb folder. Have you got any further hints for me?

 

Thanks.

Jay

 

"Patrick Rouse" wrote:

> 1. Temporarily disabe the GPOs to see if they are the cause of the problem

> 2. Try using Regmon & Filemon to determine why the app is not launching or

> failing.

>

>

>

> --

> Patrick C. Rouse

> Microsoft MVP - Terminal Server

> Provision Networks VIP

> Citrix Technology Professional

> President - Session Computing Solutions, LLC

> http://www.sessioncomputing.com

>

>

>

> "jay" wrote:

>

> > Setup: Windows SBS 2003 as domain controler, Windows Server Standard 2003 as

> > terminal server. Application to run is an Access mdb running under Access

> > runtime 2003. Terminal server locked down by group policy

> > (http://www.microsoft.com/windowsserver2003/techinfo/overview/lockdown.mspx)

> > Problem: Runs like a champ when I log in as Administrator in a console

> > session. Other users logging in as a terminal server session have Access

> > crash (with the "Send / Don't send to Microsoft" window popping up).

> > I've checked to make sure that the users have rights to the programs involved.

> > Any help???

> > Thanks in advance.

> > Jay

> >

[Guest jay]

RE: terminal server and Access 2003 runtime

 

Patrick,

I've got more follow-up. I found out that the non-administrator users

were crashing at a VBA statement like this:

imageControl.Picture = strFullPathToBmpFile

The bmp file is located in the mdb directory (C:\PProgram Files\Company

Name\Application Friendly Name\Application.mdb). I removed all references to

this statement and it seems to work. I emphasize that it worked before our

system crash, which necessitated a reinstallation, with those statements in

place. Seems crazy, doesn't it? I'd love to hear your comments.

Jay

 

"jay" wrote:

> Thanks for the quick response. I disabled the terminal server group policy

> and Access still crashes when a non-administrator runs it. I downloaded

> Processmon in lieu of Filemon and RegMon but there are thousands of lines for

> MSACCESS.EXE with results not = "Successful" with both successful runs logged

> in as administrator and crashes when logged in as non-administrator.

> I've given extended rights to my database users security group to MSACCESS

> and to the mdb folder. Have you got any further hints for me?

>

> Thanks.

> Jay

>

> "Patrick Rouse" wrote:

>

> > 1. Temporarily disabe the GPOs to see if they are the cause of the problem

> > 2. Try using Regmon & Filemon to determine why the app is not launching or

> > failing.

> >

> >

> >

> > --

> > Patrick C. Rouse

> > Microsoft MVP - Terminal Server

> > Provision Networks VIP

> > Citrix Technology Professional

> > President - Session Computing Solutions, LLC

> > http://www.sessioncomputing.com

> >

> >

> >

> > "jay" wrote:

> >

> > > Setup: Windows SBS 2003 as domain controler, Windows Server Standard 2003 as

> > > terminal server. Application to run is an Access mdb running under Access

> > > runtime 2003. Terminal server locked down by group policy

> > > (http://www.microsoft.com/windowsserver2003/techinfo/overview/lockdown.mspx)

> > > Problem: Runs like a champ when I log in as Administrator in a console

> > > session. Other users logging in as a terminal server session have Access

> > > crash (with the "Send / Don't send to Microsoft" window popping up).

> > > I've checked to make sure that the users have rights to the programs involved.

> > > Any help???

> > > Thanks in advance.

> > > Jay

> > >