k3rri
12-13-06, 10:32 AM
Hi,
We have a Windows Server 2003 setup. Employees connect through terminal server and use programs. New users added to terminal sever now cannot print a certain thing off which is used with macros through excel. All old users can. I think it may be the permissions.
When Reporter starts two dll files ae launched, a4wapi.dll and a4wmem32.dll. These files will establish the link to the database for Excel, if the link fails then will result in error 30. The profile would require rights to execute these dll's as well as sufficient rights to odbc dsn's to establish the links.
How can we check if there are any limitation on rights to ODBC keys so they do not have a limitation on the domain policies. Or how can I change permissions on a registry key level.
Does anyone have any suggestions please.
We have a Windows Server 2003 setup. Employees connect through terminal server and use programs. New users added to terminal sever now cannot print a certain thing off which is used with macros through excel. All old users can. I think it may be the permissions.
When Reporter starts two dll files ae launched, a4wapi.dll and a4wmem32.dll. These files will establish the link to the database for Excel, if the link fails then will result in error 30. The profile would require rights to execute these dll's as well as sufficient rights to odbc dsn's to establish the links.
How can we check if there are any limitation on rights to ODBC keys so they do not have a limitation on the domain policies. Or how can I change permissions on a registry key level.
Does anyone have any suggestions please.