Program wont Run on server 2008 R2 (64) but ran on Server 2008 (32)

We have a custom program that runs on anything except in the scenario.

I upgraded to Server 2008 64 bit from 32 bit. Everything fuctions great except this one custome program. Now I can run it on an administrator account, but I cant run it on a standard users account.

From what I can tell the Group Plicies are the same on both my old server to this server.

I compared teh local policies as well and they are all the same even in the UAC area.

Anyone have any ideas where else to look? It is obviously a permission issue (I think)
Keef400Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Alan HardistyCo-OwnerCommented:
If you right click the program shortcut and choose run as administrator - does it work?
0
Keef400Author Commented:
It doesnt give me an option to run as an administrator. The installer does, but when I click that option nothing happens. I already have it installed though. If I just give admin rights to the user it runs just fine, but as soon as I take it away I recieve an event type clr20r3 error.
0
Alan HardistyCo-OwnerCommented:
Have you disabled User Account Control?
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

Keef400Author Commented:
Yes, i've tried it off and with a combinaion of different levels. I still recieve the same error at all levels.
0
Alan HardistyCo-OwnerCommented:
Is the program being run on the server or on a client computer?
0
Keef400Author Commented:
On the server. It is a terminal server.
0
Alan HardistyCo-OwnerCommented:
I'm not familiar with TS I'm afraid, so will bow out here.  Would have been useful to know this at the outset.

Sorry

Alan
0
Keef400Author Commented:
I should have added TS. Overlooked that aspect as I was focused on the Security being the issue, but maybe its something else.
0
Alan HardistyCo-OwnerCommented:
If no-one else pops up to assist you after 24 hours, please use the Request Attention button and the Moderators can try to get other experts to help you.

Good luck - sorry but TS isn't my thing.

Alan
0
Rob WilliamsCommented:
Best bet would be to download and run Microsoft's "Process Monitor", then try again as a problematic user. It very quickly creates huge logs, so start Process Monitor running just before trying to start your app and stop as soon as it fails. Then start combing through the log file. There will be lots of unrelated errors but try to find a related file, process, or registry entry that is denied, probably due to permissions. There may be more than one. It is a time consuming process but often necessary especially on terminal servers where profiles are handled differently than PC's.
http://technet.microsoft.com/en-us/sysinternals/bb896645
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Keef400Author Commented:
I have a few errors associated to the program on the following files.

file Locked With Only readers. there are a number of these will files associated to them. Mostly .dll's and all the files seem to be located in System32 directory.

It doesnt indicate that permissions are needed. I have never used this tool before. Is there something else specific that im suppose to see?
0
Keef400Author Commented:
Oh I found some End Of File results for that related application as well.
0
Rob WilliamsCommented:
Are these files related to your "custom program"?
0
CoralonCommented:
Process Monitor is the right tool, but it will generate far more information that you need if you don't filter it.  Set the filter to use process name is nameofyour.exe.  That will limit the amount of data on the screen. (It will still be captured, but you won't have to slog through it.).  

Produce the error (or the refusal to run) and then stop Process Monitor.  Do a Search (Ctrl+F or the binoculars) and look for "access denied".  That will show you what it is trying to access but cannot.  (There may well be several entries).  You can correct the permissions from there.  

Another possibility is to set the program to run in Windows XP SP3 compatibility mode.  (This can be set by login script for the users).  

Now that I have typed everything out -- it occurs to me that you upgraded.  Was it a true upgrade or a migration?  If it is an upgrade, then try reinstalling it.

Coralon

0
Keef400Author Commented:
I have tried XP compatibility mode with no luck.

The change over was a migration. I did a fresh install of 2008 64 bit then just recreated and reinstalled everything. Again the program worked on 2008 32 bit. I didnt set it up on the first server though so for all i know they did something to get it to run.

I will play around with the process monitor some more.

Robwill- I'm not sure if the program uses those dlls and what not. There are a lot on there more than I would think there would be it s a very small program.
0
Keef400Author Commented:
I get an access denied on the following

HDLM\SYSTEM\CurrentControlSet\Services\WinSock2\Parameters
0
CoralonCommented:
Interesting.. try granting authenticated users the ability to write to that key.  (Strange though.. that's a pretty important key to Windows networking.. I don't know why it would try to write there).

That may resolve the issue.. But do it on a test box.. the wrong paramaters in that key could make your server unreachable/unable to communicate.

Coralon
0
Keef400Author Commented:
Great, Using the process monitor I found out what file it was trying to access. I was able to give all domain users access to the file directory and now it is able to run on anyones profile. It was a file located in the Windows directory underneith my profile (admin) profile to which the supporting applications installed a few dll's too. Thank you for all your help.
0
CoralonCommented:
If the file is in *your* profile, then the program was not installed in Install mode properly.  (Install mode turns *off* the redirection of the Windows directory.  

As a bandaid, copy those files from your profile to %systemroot%\system32 (typically c:\windows\system32) and that should fix it permanently without worrying about your profile.

As a permanent fix, reinstall the application in Install mode (change user /install at the cmd prompt) and that will do the trick :-)

Coralon
0
Keef400Author Commented:
Sweet thank you for the further update. I will note that for future installations.
0
Rob WilliamsCommented:
Glad to hear you were able to resolve. Sorry I wasn't around earlier to answer your questions.
Thanks Keef400.
Cheers!
--Rob
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server OS

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.