08-31-2016 09:18 AM
I am fairly new to SAS and have developed a VB.NET UI for users to have the ability to run ad hoc reports from SAS.
I don't want the users to have to install SAS EG. The IOM Provider dll is required for this. I tried to update the local registry of the user and use the SAS Deployment Wizard to install the SAS Providers for OLEDB but I am getting an error.(see below)
2016-08-26 12:20:29 WindowsRegistry - could not create registry key: HKEY_LOCAL_MACHINE\SOFTWARE\SAS Institute Inc.
2016-08-26 12:20:29 SSNResource - No localization resources defined for key #RegistryEditor.execute. Skipping Resolution.
2016-08-26 12:20:29 Controller - An error occurred during processing:
2016-08-26 12:20:29 Controller - There is a problem that seems to be related to the system running the install: error occurred modifying Windows Registry: addKey: HKEY_LOCAL_MACHINE\SOFTWARE\SAS Institute Inc.\Common Data\Shared Files\SAS OLE DB Solution\null null
2016-08-26 12:20:29 Controller - com.sas.tools.installs.it.InstallException: No localization resources defined for key #RegistryEditor.execute. Skipping Resolution.
Any ideas or experience granting non SAS users the ability to run Ad Hoc reports through .NET? We are on SAS 9.4.
08-31-2016 09:53 AM
For the error, contact SAS tech support.
Ways of calling SAS on the server, includes IOM and OLEDB which you already mention.
ODBC (may need addition server licenses) also possible.
Web Services is another option.
If it's acceptable with http calls you can use SAS stored processes.