RMS

I am not familiar with RMS, but it sounds like it is not supported by the vendor on terminal services. This is true of many applications and has to do with file locations and profiles, as well as file and registry permissions. If there is no documentation available as to the necessary changes, usually it involves using tools provided by Sysinternals (now Microsoft) such as Process Monitor to determine what files, and registry keys are being access and denied. In some case you may find the files are not present such as in a user profile and have to be copied to each users profile from a common folder.
http://technet.microsoft.com/en-us/sysinternals/bb842062.aspx

Thanks rob

You may be correct on this one ,  it seems that access to this program stopped working after a password change or permission change to a directory

can u advise which tool i need to use to troubleshoot this

thanks

We used to use RegMon and FileMon, but they have been replaced by Process Monitor.
It is a very tedious process as thousands of entries are logged every minute. Basically install Process Monitor, start it up, then start recording and start your problematic app. As soon as it hangs, stop recording and start going through the logs line by line looking for failures due to permissions or any other problems. Many of the errors are often unimportant so it takes a lot of time. Better if you can find documentation, but if you have the patience it can usually be solved.

Hi rob,

the application dosnt really hang it just prompt me with user login screen when i try to run a few particular reports,  will thsi still apply ?

thanks

Its should. Try and stop the recording as soon as it prompts for the user name. Then in the report start from the end and work back. You want to run Process Monitor on the terminal server.

ok additonal information ,  the user has been running this on sbs  server  and not terminal server. they use a terminal sessions for one remote user

i think they had a GPO  setup but GPO manager is not workign either and i have since disabled the RDP  policy they had in a effort to fix

cheers

Running on the SBS is not a great option:
1) major security risks
2) permissions are much tighter by default
3) server is not optimized for running applications

However, the same procedure should work. Run Process monitor on the SBS.
As a simpler test, try making the user a domain administrator temporarily and see if it works. If it does you know it is a permissions issue for sure.

Yes i agree

this is what i have advised

I will try this and get back to you

cheers

I have actually logged in as administrator and i get the same error when running the report

should this rule out permissions ?

Probably, but there are some restrictions on a domain controller (SBS) that do not exist on server 2003 such as a terminal server.
Sorry I am not a lot of help where I a not familiar with the application.

Unable to resolve issue,  however rob will was accurate in answer.

Thanks fdran. Sorry we were not able to find a final resolution.
Cheers!
--Rob