App not working

[Christopher Schlüter]

Hello NG,

on a new XP SP 3 machine, programs which are executed in user mode are not
working prob.
In Admin mode it works as it should. That's curious because on other PCs it
works fine.

Problems are i.e.:
-office 2003 SP3 does not create doc links, when i start the program
manually, the installer starts and tries to install something, when i close
the program same procedure....
However, no persistant settings are made. That means: each time i open an
office app the installer starts...

-i have no access to my MS SQL Server 2005. Provider not found etc...

On other PCs with "normal" users it works.
Do you have any idea??

Maybe modify any ACLs on %systemroot% or programs
I've no idea. This is the very first time a have this problem with XP (on a
new PC...)

Thanks....
Chris

 

[Lanwench [MVP - Exchange]]

Hello NG,

on a new XP SP 3 machine, programs which are executed in user mode
are not working prob.
In Admin mode it works as it should. That's curious because on other
PCs it works fine.

Problems are i.e.:
-office 2003 SP3 does not create doc links, when i start the program
manually, the installer starts and tries to install something, when i
close the program same procedure....
However, no persistant settings are made. That means: each time i
open an office app the installer starts...

-i have no access to my MS SQL Server 2005. Provider not found etc...

On other PCs with "normal" users it works.
Do you have any idea??

Maybe modify any ACLs on %systemroot% or programs
I've no idea. This is the very first time a have this problem with XP
(on a new PC...)

Thanks....
Chris

I'd reinstall the applications and see whether that works before looking at
anything else. A full install of Office should need no admin rights. Are you
talking about SQL or MSDE/SQL Express instances?

The Windows Installer Cleanup Utility can also be useful (if you're careful
with it) if reinstalling doesn't work.

 

[Christopher Schlueter]

Hi,

I've already reinstalled the apps.-..
We have a SQL Server 2005 SP3 Express Edition Instance.
On the client side we use the SQL native client 9.

With admin rights it works. I just don't know why this works on other PCs
having the same configuration using the same software.

Obviously, it's a security related problem, but i don't know what right i
can give a normal user....

Thx

"Lanwench [MVP - Exchange]"

 

[Lanwench [MVP - Exchange]]

Hi,

I've already reinstalled the apps.-..

Alas. And even Office doesn't work? Yank it out and reinstall it from
scratch. Do a custom install and run everything from the workstation (all
components). Log in as a new domain user (one who has never logged into the
PC before) and see.

We have a SQL Server 2005 SP3 Express Edition Instance.
On the client side we use the SQL native client 9.

With admin rights it works. I just don't know why this works on other
PCs having the same configuration using the same software.

Obviously, it's a security related problem, but i don't know what
right i can give a normal user....

Thx

You can also try downloading Sysinternal's ProcessMonitor (or is it
Explorer?) to see where the offending app is trying to write, so you can set
perms manually.

"Lanwench [MVP - Exchange]"

I'd reinstall the applications and see whether that works before
looking at anything else. A full install of Office should need no
admin rights. Are you talking about SQL or MSDE/SQL Express
instances? The Windows Installer Cleanup Utility can also be useful (if
you're
careful with it) if reinstalling doesn't work.

 

[Twayne]

Alas. And even Office doesn't work? Yank it out and reinstall it from
scratch. Do a custom install and run everything from the workstation
(all components). Log in as a new domain user (one who has never
logged into the PC before) and see.


You can also try downloading Sysinternal's ProcessMonitor (or is it
Explorer?) to see where the offending app is trying to write, so you
can set perms manually.

Note that sysinternals is now located at microsoft.com. Guess they were
bought out.

HTH,

Twayne

"Lanwench [MVP - Exchange]"

I'd reinstall the applications and see whether that works before
looking at anything else. A full install of Office should need no
admin rights. Are you talking about SQL or MSDE/SQL Express
instances? The Windows Installer Cleanup Utility can also be useful
(if you're
careful with it) if reinstalling doesn't work.

 

[Lanwench [MVP - Exchange]]

Note that sysinternals is now located at microsoft.com. Guess they
were bought out.

Yep, but the tools are still free (and very good).

HTH,

Twayne

"Lanwench [MVP - Exchange]"
im Newsbeitrag I'd reinstall the applications and see whether that works before
looking at anything else. A full install of Office should need no
admin rights. Are you talking about SQL or MSDE/SQL Express
instances? The Windows Installer Cleanup Utility can also be useful
(if you're
careful with it) if reinstalling doesn't work.

 

[Christopher Schlueter]

The program is written by us.
So there are no special permissions to run the program...

Maybe its related to the MDAC 2.8 SP1 on XP SP3 problem.
When i use a ODBC DSN Source as Connection String it works.

The Connection and the SQL prermissions are correct.

 

[Christopher Schlueter]

Hi,

problem solved.
All this had to do with the registry permissions.
HKEY_CLASSES_ROOT didn't grant read permissions to users.

The problem is easy to fix but difficult to identify....
No idea why XP hadn't set these permissions correctly during the
installtion....


you live and learn....
especially wth MS...

KR
Chris