Kurt, Along those lines, I think reviewing the logs may help. Perhaps a large number of errors, warnings, and notes are being generated suddenly causing the log to explode. ... View more

It is most likely a latency issue. See if the server moved to a new location or if you have code that calls a file that is now not local to the job. The server also may be under load. Disk thrashing can cause wild spikes so the server could be constrained. There isnt really much in your question to aid in diagnosis. I can give you just some guesses based upon my consulting experiences and common causes. Server or network assuming code hasnt changed. ... View more

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. ... View more

For github, look under savian or savian.net. The xpt format was created to allow for SAS data to be stored in an accessible format. This was done, decades ago, for govt compliance reasons. It allows SAS data to be read/written. However, for you, it would allow your data to be written to a format that a SAS customer could consume. Warning, it uses IBM mainframe floating points so those have to be converted. My code has that in there. I didnt solve it but I did the conversion to C#. That is on CodePlex, I believe. You cant bundle SAS in your product. If you were just going to read SAS, there are some ways. Writing it is a lot more complex. Stick with the xpt format and ignore sas7bdat, my suggestion. ... View more

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; } } ... View more

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. ... View more

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

I also have a C# package on GitHub that does the xport format. It is a lot closer to Java than R or Python if you want to do a translation. It doesn't handle the most recent xport format since that one has a documentation issue on the SAS website. That may have been fixed.   I left the code in place in case you need to tackle it but it is not widely used (from what I saw). ... View more

Use the following options at the top of the program:   options mfile mprint obs=0 noerrorbyabend errors=0 source source2 nonotes; filename mprint 'c:\temp\SasCode.txt’;   When you run your program, a new copy of it will be in the SasCode.txt file with all macros resolved. ... View more

Use the local provider, 64 bit. BTW, when I am at a client site and have to figure any DB connection string, I always use the UDL trick. ... View more

Use this technique for testing: http://www.polyweb.com/blog/index.php/archives/17 Go to connectionstrings.com for info on the parts of the connection string. SAS will also have documentation on their allowed parameters. No, I didnt test with Unix. It shouldnt matter: you are just reading a file. ... View more

It depends on complexity. .NET is the best, IMO, because it supports very rich window controls, is what EG is written in, and you can create custom EG tasks. I have built very complex controls in EG using C#. Your skills and needs may be different. ... View more

I just did a quick test and connected to PowerBI: Instructions:   Go here: https://support.sas.com/downloads/package.htm?pid=2472# Download the 1st driver (64 bit) and install it Open PowerBI Add OleDB datasource. Connection string: Provider=SAS.LocalProvider.1; Data Source=c:\temp\MySasData See sample in attached picture     ... View more

I stand corrected. My examples are using OleDb.  ... View more