After installing a server with Terminal Services and Office 2000 on the Terminal Server, users logged in locally here to the network (no longer through terminal services) and they get windows installer popping up everytime at logon to configure office 2000 small business and then afterwards they cannot double click an office document to open it. They get an error saying to make sure all required libraries are available and that the document could not be found. Yet, if they open the corresponding office application, they can do the file, open and then open the document. We use roaming profiles, so I believe something happened when they logged in remotely to terminal services and now that they are logged in locally in the office some path is incorrect. Please help!!!! I'm very frustrated.

Eventhough it is not supposed to, the roaming profile for regular windows networks and terminal services WILL overwrite each other. If the users still log onto the terminal server then make sure, while they are logged into the terminal server that you make their profile local. We had an application that would not work unless this was done. I use office 2K pro, and i noticed that the same thing happens to me only when using access, not with any other programs. Also, try logging in locally as the administrator and see if the same thing occurs.