topic Re: .NET: SASObjectManager COMException from OMRInterface when connecting to remote Metadata Server in Developers

.NET: SASObjectManager COMException from OMRInterface when connecting to remote Metadata Server

meiacopeland — Wed, 13 Jul 2022 18:28:35 GMT

I am trying to build a solution that involves connecting to our Metadata server hosted on an AWS Red Hat instance through C# .NET, and am using Chris Hemedinger's C# example for .NET as an example. When I try to run the code, I immediately get a COMException from OMRInterface. Usually this results in a message of

"Could not connect: <connectionAttempts></connectionAttempts>"

and

System.Runtime.InteropServices.COMException (0x80042002): <connectionAttempts></connectionAttempts>
   at SASObjectManager.ObjectFactoryMulti2Class.CreateObjectByServer(String Name, Boolean synchronous, ServerDef pIServerDef, String LoginName, String Password)
   at SAS.BI.Itconfig.Library.ServerTests.SASServerTest.CreateConnectionWithObjectFactoryMulti()
   at SAS.BI.Itconfig.Library.ServerTests.SASServerTest.CreateConnection()

I have installed the SAS Integration Technologies Client, and have tried using the ITConfig.exe to test the connection, and will get this message every time

Function Name:CreateObjectByServer
0x80042002 - <connectionAttempts>
<connectionAttempt>
<description>Invalid pointer
</description>
<status>0x80004003</status>
<saslogin></saslogin>
<sasmachinednsname>[machine DNS name here]</sasmachinednsname>
<sasport>8561</sasport>
<sasclassid>2887E7D7-4780-11D4-879F-00C04F38F0DB</sasclassid>
<threadid>31556</threadid>
</connectionAttempt>
</connectionAttempts>
There is no additional error information available.

It does not matter what Machine DNS name I use, or whether or not I use a username and password when testing the IOM Bridge to our Metadata Server. I have run other tests to check that I do have access to the port, so that shouldn't be the issue. I think the issue is on my machine. I think it has something to do with the initial creation of

SASObjectManager.IObjectFactory2 obObjectFactory = new SASObjectManager.ObjectFactoryMulti2();

As this results in an OMRInterface exception. I have also tried connecting to Workspace instead (port 8591), but get the exact same error.

Does anyone have an idea of what the Invalid Pointer in the error message is referring to? Are there other SAS libraries/programs/clients I need to install besides Integration Technologies Client?

Re: .NET: SASObjectManager COMException from OMRInterface when connecting to remote Metadata Server

AlanC — Wed, 13 Jul 2022 19:21:40 GMT

I am not at my machine right so winging it a bit. Check your dcom config for permissions.

Re: .NET: SASObjectManager COMException from OMRInterface when connecting to remote Metadata Server

meiacopeland — Wed, 13 Jul 2022 20:15:52 GMT

Thanks for the quick response! In the ITConfig, it says

An error occurred while trying to gather information about SAS. SAS may not be installed on this machine.
DCOM is enabled.
dcomcnfg Settings:
Default Authentication Level: Not Specified
Default Impersonation Level: Identify

The first part, I've been assuming it's because I don't have any SAS programs aside from the ITClient.

I also checked my DCOM permissions, and there doesn't seem to be anything wrong there. Although I have never played around with those kinds of settings before, so not sure what to do.

Re: .NET: SASObjectManager COMException from OMRInterface when connecting to remote Metadata Server

AlanC — Wed, 13 Jul 2022 21:10:03 GMT

I believe you are hitting a security issue, but that is the case in almost all circumstances with the IntTech connection. I know this is old (26056 - Microsoft Visual Studio 2005 C# Code Snippets (sas.com)) but look at the IOM section and see if that helps you isolate the wrong parm. The CLSID is the best search term, not the error. You may need to call tech support or see if Chris picks up on it.

I never use IOM. I tend to put a web service on the server and call into SAS that way. Much, much easier.

It depends on what you need to do as well. If the goal is to submit code or read a dataset.

Re: .NET: SASObjectManager COMException from OMRInterface when connecting to remote Metadata Server

AlanC — Wed, 13 Jul 2022 21:23:23 GMT

I found some old code. I am sending a few snippets which you can piece together:

       internal static SAS.Workspace ConnectToSAS()
        {
            SASObjectManager.ObjectFactoryClass objFactory = new SASObjectManager.ObjectFactoryClass();
            SASObjectManager.ServerDefClass serverDef = new SASObjectManager.ServerDefClass();
            // ************************************************
            // Configure the SAS server information.
            // ************************************************
            serverDef.BridgeEncryptionAlgorithm = "SASProprietary";
            serverDef.BridgeEncryptionLevel = SASObjectManager.EncryptionLevels.EncryptUserAndPassword;
            serverDef.MachineDNSName = "client.dnsexample.local";
            serverDef.MachineDNSName = "172.88.111.22";
            serverDef.MachineDNSName = "skycutter";
            serverDef.Port = 8592;
            serverDef.Port = 8591;
            serverDef.Protocol = SASObjectManager.Protocols.ProtocolBridge;
            // ************************************************
            // Create the connection.
            // ************************************************
            SAS.Workspace sasWorkspace = null;
            sasWorkspace = (SAS.Workspace)objFactory.CreateObjectByServer("BridgeConnection", true,
                serverDef, "uid", "password");
            // Add the SAS object to the ObjectKeeper. If the object is not
            // in the ObjectKeeper, it cannot be used by the IOM Data Provider.
            SASObjectManager.ObjectKeeperClass objKeeper = new SASObjectManager.ObjectKeeperClass();
            objKeeper.AddObject(1, "BridgeConnection", sasWorkspace);
            return sasWorkspace;
            // objKeeper.RemoveObject(sasWorkspace);
        } // connectToSAS()


        /// <summary>
        ///     Submits SAS code using the IOM interface
        /// </summary>
        /// <param name="sasCode">The SAS statements to be submitted</param>
        public SasRunObject SubmitSasCode(string sasCode)
        {
            try
            {
                Workspace ws = CreateWorkspace();
                SasCore.StepError = false;
                SasCore.SasLanguageService.Reset();
                SasCore.SasLanguageService = ws.LanguageService;
                SasCore.SasLanguageService.Submit(sasCode);
                SasCore.SasLanguageService.StepError += SasLanguageService_StepError;
                SasCore.SasLanguageService.LineSeparator = "\r\n";
                var sro = new SasRunObject();
                sro.SasCode = sasCode;
                sro.SasLog = SasCore.SasLanguageService.FlushLog(SasCore.LogCharactersToReturn);
                sro.SasList = SasCore.SasLanguageService.FlushList(SasCore.ListCharactersToReturn).Replace("\f", "");
                return sro;
            }
            catch (Exception ex)
            {
                util.HandleError(MethodBase.GetCurrentMethod().Name, ex);
                return null;
            }
        }

Re: .NET: SASObjectManager COMException from OMRInterface when connecting to remote Metadata Server

meiacopeland — Thu, 14 Jul 2022 20:40:01 GMT

I tried the code you attached and was getting the same problem. We're thinking it's likely a security issue, especially since I am working on a company computer. We will be trying out other solutions, and contact tech support if we get stuck with those as well. Your help is much appreciated!

Re: .NET: SASObjectManager COMException from OMRInterface when connecting to remote Metadata Server

AlanC — Thu, 14 Jul 2022 21:34:51 GMT

Make sure you go into dcomcnfg utility in Windows and, on any SAS objects, set Permissions to None. That may help. When I looked, I didnt see any SAS objects in my DCOM which is strange. They used to always be there. Check yours and good luck.

Fiddler may help you as would sysmon in the SysInternals suite.

Re: .NET: SASObjectManager COMException from OMRInterface when connecting to remote Metadata Server

meiacopeland — Tue, 09 Aug 2022 15:00:49 GMT

Wanted to update this now that I have solved the issue.

I googled the SAS Integration Technologies Client, and the first several hits were for SAS 9.2. I have now gotten a link from SAS to the newest version, and am able to connect to the server remotely.