14 replies
by stillatit
The problem is that Office 97 apps do not share well under W2k. You get the same problem installing Office on a user machine which will be used by multiple users.
When you installed Outlook, it put some files in places and with protections that block normal users. You can find these files by turning on failure auditing for a user and for the Windows directory, then logging in as that user and running Outlook. Then log back in as the admin and check the event viewer to find the file(s) which the user could not access. Change the protection on those files. Note that if any of these are .pst or .pab, you need to individualize these for the user and you should move them to the user's home directory.
Good luck.
by technews
by dklippert
There is probably a profile conflict. Here's a MS suggestion:
"Rename the Ntuser.dat file while you are logged on as the administrator on the
Terminal Server console, and then restart the Terminal Server. This creates a
default Ntuser.dat file that does not contain any profile information."
For more details see:
http://support.microsoft.com/support/kb/articles/Q254/3/33.asp(There are no spaces in the URL)
by technews
Check if they have the appropiate permissions in the registry.
When you try to run Microsoft Outlook 97, you may receive the following error message:
The Program is not registered properly. Please run Setup again. You don't have appropriate permission to perform this operation.
This behavior can occur if you are a local user or a domain user. Local and domain administrators can run Outlook 97 correctly.
CAUSE
When you start Outlook 97 as a local user or a domain user, you musthave permission to write and modify the following registry key:
HKEY_LOCAL_MACHINE\Software\Microsoft\Office
RESOLUTION
WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.
For information about how to edit the registry, view the "Changing Keys and Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Note that you should back up the registry before you edit it. If you are running Windows NT or Windows 2000, you should also update your Emergency Repair Disk (ERD).
To resolve this issue:
Log on to the system as a local or domain administrator.
Start Registry Editor (Regedt32.exe).
Click the following key:
HKEY_LOCAL_MACHINE\Software\Microsoft\Office
On the Security menu, click Permissions.
Add the Local Users group or Domain Users group.
In the Permissions box, give the appropriate user group Full Control access rights.
by technews
I have already given the user(s) permissions to that key in the registry.
In fact, I searched the directory and gave them rights to everything that came up for office and outlook and it still didn't work. That is when I tried admin rights and that works, although I obvioulsy don't want to give all my users admin rights.
Thanks
by technews
The Ntuser.dat file, which is the default set of registry keys that load each time a Terminal Server user logs on, contains another user's profile information. You get this error message because Outlook attempts to use the other user's profile.
This problem occurs when the administrator runs Outlook and installs Terminal Server simultaneously.
Rename the Ntuser.dat file while you are logged on as the administrator on the Terminal Server console, and then restart the Terminal Server. This creates a default Ntuser.dat file that does not contain any profile information.
For additional information about Ntuser.dat on Windows Terminal Server, click the article number below to view the article in the Microsoft Knowledge Base:
http://support.microsoft.com/directory/article.asp?ID=kb;en-us;Q146050
(REMOVE SPACES from the pasted URL)
Maxwell
by technews
by technews
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending