About AndreasMenrath

AndreasMenrath · ‎07-25-2014

This task is very old and most likely compiled against SAS Enterprise Guide 4.2 and the Microsoft .Net Framework 2.0 It may be possible that SAS changed the custom taks API in EG 6.1 or that you run into .Net issues when you try to execute the DLL inside a newer .Net Framework environment. You might also have some 32/64 bit compatibilty issues. My advice: turn on the logging in EG, search the log for errors and post the error message. See: 17730 - Turning on logging in SAS® Enterprise Guide® 4.2, 4.3, 5.1, and 6.1

AndreasMenrath · ‎07-25-2014

This is complicated. A STP is not a STP. Every SAS version brings modifications and new features for STPs so a STP works different in each SAS version. Also there are different ways and technologies to run a STP: Java, .Net and COM. With VBA you have picked the most challenging technology! If you have licenced the SAS Addin for Microsoft Office you may use the API of the SAS Addin (see http://support.sas.com/resources/papers/proceedings11/012-2011.pdf). If you don't have SAS AMO you should consider using another technology. IMHO calling the STP as a BI web service will be the easiest way.

AndreasMenrath · ‎07-09-2014

SAS is not like a database. What you intend to do is typical for databases. For SAS a view is just a query saved in the file system. When you execute the view the query is executed and your users will need access privileges to the underlying table. So it is not possible to do that with SAS datasets.

AndreasMenrath · ‎07-09-2014

The best practice to run SAS programs in batch is to run the program directly on the server. You can start a new SAS session and execute a program with some simple batch files (.bat in Windows, .sh in Linux/Unix). These batch files are usually called by a scheduler like LSF or UC4. If you want to keep the control of the execution at the client side you might want to take a look at the examples #1 and #4 here: Cmdlets4Sas / Wiki / Connect-SasWorkspaceServer #1 shows how to use the integrated windows authentication #4 shows how to prompt the user for login credentials Good luck!

AndreasMenrath · ‎07-09-2014

The good news is that i can recreate your problem in my environment (SAS 9.3, Windows 7 x64) too. So i guess this is a general bug in the SAS IT Client. The documentation file sasoman.chm in the IT Client folder !SASHOME\x86\Integration Technologies only knows the 2 argument version of the method CreateObjectByLogicalName. There is a CreateObjectByLogicalNameAndLogins method with 5 arguments which has a similar signature to the web documentation (http://support.sas.com/documentation/cdl/en/itechwcdg/64888/HTML/default/viewer.htm#p05uy6cy21o83vn15ev4mxlhkkox.htm). IMHO the web documentation is totally wrong in this case. As a side note: welcome to the SAS IOM hell! It is poorly documented, many documented features do not work as expected and many important features are not documented. The only solution for these problems is a lot of trial and error coding. Back to your problem: accourding to the error message <sassecuritypackage>Negotiate</sassecuritypackage> <sassecuritypackagelist>Kerberos,NTLM</sassecuritypackagelist> the IT client tries to connect to the server using the integrated windows authentication method and not the user/password combination. Maybe the Workspaceserver needs to be reconfigured with the SAS Management Console to use Security package "Username/Password": Can you describe what you want to achieve after you have connected to the server? Maybe my PowerShell commandlets (http://sourceforge.net/projects/cmdlets4sas/) already cover your needs. Greetings, Andreas

AndreasMenrath · ‎04-21-2014

it reduces my test write time from 8s to 2s, writing 5 rows instead of 1 row in each insert. That is still very slow. I guess that most of that time is used to open the dataset and initialize the driver. Can you try 1000 rows and measure the performance? The next question is, does anyone know the character size limit of the query text? There is no documented limit. Maybe 32K (32768) characters. As a best practice you should try different lengths. If there is a limit it may be different in each SAS version and x86 and x64.

AndreasMenrath · ‎04-06-2014

There is no easy way to write to SAS datasets. You might want to try the SAS ODBC drivers, but ODBC brings a lot of pain, too. Then there is an undocumented and strange API for the COM interface SAS.IDataSet. I would not recommend anyone to use that. Another option would be to export your data to a CSV or XML file, transport it to your SAS server and import it with SAS code. So OleDB is still the best way to write a SAS dataset. I guess when you talk about "single row SQL insert queries" your programm inserts one row and waits for the OleDB provider to finish until the next row is sent. So you might get a performance boost if you insert multiple rows with a single SQL statement. You can insert multiple rows with a SET or VALUES clause (see http://support.sas.com/documentation/cdl/en/proc/61895/HTML/default/viewer.htm#a002294531.htm for example). If you find a better way for writing a SAS dataset with OleDB please post your solution here. I'm looking for it since years. It's about time that someone writes an awesome ADO.NET Entity Framework provider for SAS tables :smileylaugh:

AndreasMenrath · ‎11-05-2013

Usually COM is only used to start a Workspace Server on your local machine. If you connect to a remote server you use the IOM Bridge protocoll. Maybe this link to the documentation can help you understand the infrastructure of SAS: SAS(R) 9.4 Integration Technologies: Overview

AndreasMenrath · ‎10-25-2013

Hi Eric, you might want to take a look at my project at https://sourceforge.net/p/cmdlets4sas/wiki/Home/https://sourceforge.net/projects/cmdlets4sas/ There are some PowerShell commands available to connect to a STP server, execute SAS code and check the log. Prompts just generate and fill macro variables. You can simulate prompt values by setting macro variables at the beginning of your SAS code.

AndreasMenrath · ‎10-25-2013

This is a pure C# question, right? So this might not be the best place to ask for help. This sounds like a .Net property in your Textbox Control. Which user control do you use? Do you use WinForms or WPF? Look for some properties like "Mulitline" at your control (e.g. TextBox.Multiline Property (System.Windows.Forms))

AndreasMenrath · ‎10-11-2013

I have programmed some SAS applications with C# in the past and can tell you that you can expect some surprises on your way. The best way to start is to read the windows client developer's guide and the oledb cookbook mentioned before. But expect some resistance when you read or update data with SQL: - mapping .Net data types to SAS data types (with formats and informats) and vice versa - standard mechanisms of .Net to update an DataTable will not work with the SAS provider. So you have to write all your operations in SAS SQL. - if you also want to execute some SAS scripts and interact with a workspace server take a close look at the object keeper. Good luck!

AndreasMenrath · ‎10-11-2013

You can also user OLEDB to connect to your SAS share server (SAS(R) 9.3 Providers for OLE DB: Cookbook). Please clarify what your front end and your backend should do. Do you want to just load SAS tables into your Access DB or do you need to execute SAS code in your backend?

AndreasMenrath · ‎10-06-2013

It looks like FUTS has not been updated for a long time (and perl does not seem to be a state of the art programming language any more). More recent is SasUnit (http://sourceforge.net/projects/sasunit/), but support for STPs is not implemented yet (although intended, see SASUnit / Tickets / #45 Allow for testing of Stored Processes ). This leads back to the question what Eric intends to test about the STPs which is not covered by testing the SAS code? The STP may consist of a single call of a utility macro. This macro could be unit tested with any mentioned unittesting framework. Or do you need regression tests to make sure that the tested SAS code inside the STP still works when it is run on the STP Server (different machine, executed as a technical user with different privileges, dependencies on OS capabilities, autocall macros or formats may not be available, ...)?

AndreasMenrath · ‎10-06-2013

That's an interesting topic. I'm also interested in the topic of testing STPs. The downside of STPs is that a STP consists of many different aspects and that makes automated testing difficult. Which aspects do you want to test? Prompts Execution of SAS code (including dependencies to autocall macros, formats, datasets, ...) ODS Results/ Reports Does the STP run on the STP Server or on a Workspace Server? Is the result of the type stream, package or both? Is the STP executed on the "Stored Process Web Application" Can you specify a typical unit test for the testing scenarios you have in mind? Maybe you can achieve some of these points with PROC STP.

AndreasMenrath · ‎03-25-2013

Well the message says everything: you are connecting to the metadata server and not the workspaceserver. The workspaceservers default port is 8591. Perhaps the workspaceserver also runs on a different machine. Connect to your profile, go to the serverlist, locate the server you want to connect to and right click the context menu "properties" to see the right connection profile for your workspaceserver. BTW: if you are using IWA (integrated windows authentication) you must not provide a username and password. So i suggest this code: obServer.MachineDNSName = "GBLONTAS68" obServer.Protocol = SASObjectManager.Protocols.ProtocolBridge obServer.Port = 8591 Set obSAS = obObjectFactory.CreateObjectByServer("sas", True, obServer, Nothing, Nothing)

Online Status	Offline
Date Last Visited	Friday

Re: VSCode SAS Extension - IOM Bridge for Linux ?

Re: Can GPT-5 Build SAS Studio Flows? A Hands-On Test Drive

Re: Modern authentication methods for Analytics Pro? MFA required!

Modern authentication methods for Analytics Pro? MFA required!

Re: Some SASWORK storage options for SAS Viya on Kubernetes

Re: Accessing Social Media data (and more) from SAS Viya with embedded...

Re: Error using Office 365 SMTP relay

Re: Error using Office 365 SMTP relay

Error using Office 365 SMTP relay

Re: SAS VA 7.5: Geomap Execution Context

Is there a SAS statement regarding Ingress-NGINX reaching EOL?

Can GPT-5 Build SAS Studio Flows? A Hands-On Test Drive

SAS Viya High Throughput Batch Processing: Part 1 – Reusable Batch Ser...

SAS Viya CLI container image in Azure DevOps (March 2024 Update)

Using NFS Premium shares in Azure Files for SAS Viya on Kubernetes

Re: SAS with Azure DevOps

Code Kata: Wonderland number

Re: SAS Viya 3.4 for Containers: error in deployment

SAS Viya 3.4 for Containers: error in deployment

Re: SASUNIT configuration in 9.4 linux

Re: System Command Task Not Working in EG 6.1

Re: Example code to call a stored process from VBA?

Re: Grant access to a view not to the table

Re: Using "CreateObjectByLogicalName" to connect to a remote SAS Works...

Re: Using "CreateObjectByLogicalName" to connect to a remote SAS Works...

Re: Writing local SAS tables from 64-bit C# process without explicit S...

Re: Writing local SAS tables from 64-bit C# process without explicit S...

Re: IOM vs COM

Re: Stored Processes unit test in 9.3

Re: Saving character field from C# app to sas with carriage returns

Re: How can I use Access 2010 as the front end and SAS as the back end

Re: How can I use Access 2010 as the front end and SAS as the back end

Re: Stored Processes unit test in 9.3

Re: Stored Processes unit test in 9.3

Re: Calling SAS through VBA

SAS Innovate 2026

SAS Inner Circle Panel

SAS Plattform Netzwerk

SAS Explore

SAS Analytics Explorers