cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
jhckx
‎10-27-2016
  • 7 Posts
  • 0 Likes Given
  • 0 Solutions
  • 1 Likes Received

Open an Enterprise Guide project using a different profile

by Fluorite | Level 6 in SAS Enterprise Guide
‎07-23-2014 10:42 AM
1 Like
‎07-23-2014 10:42 AM
1 Like
A colleague has been uisng EG with a locally installed SAS version but now needs to switch to our server. She can create new EG projects just fine but all her existing projects won't run unless she changes her profile to 'local'. Is there any way to get EG to work with the existing projects, created with the local SAS version? She's using EG 6.1, the server runs SAS 9.4, as does her local SAS. The EG projects were created using the point-and-click interface. ... View more

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

by Fluorite | Level 6 in SAS Enterprise Guide
‎07-10-2014 11:10 AM
‎07-10-2014 11:10 AM
We used to have the problem of the screen not keeping up with our typing but IT upgraded our VMWare system and it works great now. I can get good performance with my EG batch script if I run it from an editor located on the company intranet. Performance is bad though if run the editor from the hard drive on my laptop. I use PSPad as editor, it doesn't need an install program so I can put it on my local network share and run it from there when I'm using VMWare. ... View more

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

by Fluorite | Level 6 in SAS Enterprise Guide
‎07-10-2014 02:50 AM
‎07-10-2014 02:50 AM
Well, the real disappointment was that a batch run over VPN was just as slow with a script based on a Workspace object as with a script based on an EG object. I'd hoped that using a Workspace object would avoid some of the overhead involved with EG but that doesn't look like it's the case.A fairly simple job took over a minute using the Workspace script over a VPN connection versus 5 seconds on the office network using the EG script. Now I know how the Dutch team feels after losing from Argentine :smileycry:. ... View more

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

by Fluorite | Level 6 in SAS Enterprise Guide
‎07-09-2014 11:20 AM
‎07-09-2014 11:20 AM
I spoke too soon . The negotiate method does work to the extent that I can connect to the SAS server and e.g. create data from scratch or use builtin datasets. But I'm not recognized as my userid so I can't include files or define libnames to data I have access too. Complicated. ... View more

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

by Fluorite | Level 6 in SAS Enterprise Guide
‎07-09-2014 09:43 AM
‎07-09-2014 09:43 AM
Thanks Chris, "negotiate" did the trick! For anyone else sweating in IOM Hell, here's what works for me: ' force declaration of variables in VB Script Option Explicit Dim objFactory, objServerDef, objSAS, program, log Set objFactory = WScript.CreateObject("SASObjectManager.ObjectFactoryMulti2") Set objServerDef = WScript.CreateObject("SASObjectManager.ServerDef") objServerDef.MachineDNSName = "SASServer" ' SAS Workspace node objServerDef.Port = 8591 ' workspace server port objServerDef.Protocol = 2 ' 2 = IOM protocol 'This assumes that you've configured your environment for single-signon/integrated Windows authentication. objServerDef.BridgeSecurityPackage = "Negotiate" ' Class Identifier for SAS Workspace objServerDef.ClassIdentifier = "440196d4-90f0-11d0-9f41-00a024bb830c" ' create and connect to the SAS session Set objSAS = objFactory.CreateObjectByServer("SASApp",True,objServerDef,"","") program = "ods listing; proc means data=sashelp.cars mean mode min max; run;" ' run the program objSAS.LanguageService.Submit(program) Dim loglines loglines="" do     loglines=objSAS.LanguageService.FlushLog(1000)     wscript.echo loglines loop while Len(loglines) > 0 objSAS.Close() ... View more

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

by Fluorite | Level 6 in SAS Enterprise Guide
‎07-09-2014 09:03 AM
‎07-09-2014 09:03 AM
Hi Andreas, At the least, "sasoman.chm" cleared up the "4 vs 2 arguments" issue. If you look in the index, there are two entries for "CreateObjectByLogicalName" (and most other "create" methods), with 4 arguments for "ObjectFactory" and with 2 arguments for "ObjectFactory2". What I want to do is to run SAS programs in batch. I can do that now using VBScripts that create an "Enterprise Guide" object (also from posts by Chris Hemedinger) but I'd prefer to bypass EG and create a workspace object directly. I've modified the VBScript to do that but it requires that userid and password are included in the script and that's not a good idea from a security point of view. "CreateObjectByLogicalName" seemed like what I was looking for but I suspect you're right and that the server is configured for integrated windows authentication. Does anyone know how to create a Workspace object without including the user password? Thanks for your help Andreas! ... View more

Using "CreateObjectByLogicalName" to connect to a remote SAS Workspace

by Fluorite | Level 6 in SAS Enterprise Guide
‎07-09-2014 05:41 AM
‎07-09-2014 05:41 AM
I've been experimenting with Chris Hemedinger's scripts for using powershell to connect to a SAS workspace and run SAS jobs ( Using Windows PowerShell to connect to a SAS Workspace server - The SAS Dummy). That works but requires your loginname and password to be included in the script, which I'd like to avoid if possible. It should also be possible to connect using the "CreateObjectByLogicalName" method. There's an example here (using Python): Example of how to use SAS Workspace APIs to upload a file to a remote SAS session. Uses SAS LanguageService, FileService and BinarySteam APIs, part of IOM. The main section: # create the Integration Technologies objects objFactory = win32com.client.Dispatch("SASObjectManager.ObjectFactoryMulti2") # these xml files can be created using the SAS Integration Technologies Configutation Utility objFactory.SetMetadataFile( "C:/path/to/serverinfo.xml" , "C:/path/to/userinfo.xml" , False ) # create a connection to the SAS Workspace Server objSAS = objFactory.CreateObjectByLogicalName( "SASApp - Logical Workspace Server" , "" ) I've used ITConfig to create a default connection to the metadataserver. That creates "oms_serverinfo2.xml" and "oms_userinfo2.xml" in "%USERPROFILE%\AppData\Roaming"\SAS\MetadataServer", the latter contains my password in encrypted form. In Powershell, I create objFactory using the syntax from Chris's examples: $objFactory = New-Object -ComObject SASObjectManager.ObjectFactoryMulti2 If I understand the documentation, I should be able to connect without pointing to my metadata but I've defined that just to be sure $objFactory.SetMetadataFile( "<path>\oms_serverinfo2.xml" , "<path>r\oms_userinfo2.xml" , $FALSE ) Now, I should be able to create a workspace object using: $objSAS = $objFactory.CreateObjectByLogicalName("SASApp - Logical Workspace Server" , "" ) This doesn't work though, I get an error: Exception calling "CreateObjectByLogicalName" with "2" argument(s): "<connectionAttempts>     <connectionAttempt>         <description>Cannot locate an identity in metadata for the specified identity id ().</description>         <status>0x80042102</status>         <saslogin></saslogin>         <sasmachinednsname></sasmachinednsname>         <sasport>8591</sasport>         <sassecuritypackage>Negotiate</sassecuritypackage>         <sassecuritypackagelist>Kerberos,NTLM</sassecuritypackagelist>         <sasclassid></sasclassid>         <sasprogid>SAS.Workspace.1.0</sasprogid>         <sasserver>SASApp - Workspace Server</sasserver>         <sasdomain>DefaultAuth</sasdomain>         <threadid>2280</threadid>         <sasauthenticationservice>Host</sasauthenticationservice>     </connectionAttempt> </connectionAttempts>" At line:1 char:48 + $objSAS = $objFactory.CreateObjectByLogicalName <<<< ("SASApp - Logical Workspace Server" , "" )     + CategoryInfo          : NotSpecified: (:) [], MethodInvocationException     + FullyQualifiedErrorId : ComMethodTargetInvocation The server doesn't seem to be able to find who I am. Does anyone know what I might be doing wrong here? The few examples I've been able to find using "CreateObjectByLogicalName" use two arguments, the server's logical name and an empty string. The SAS documentation though, specifies 4 arguments: SAS(R) 9.4 Integration Technologies: Windows Client Developer's Guide So I've also tried: $objSAS = $objFactory.CreateObjectByLogicalName("SASApp", $TRUE, "SASApp - Logical Workspace Server" , "") In that case, I get an error Cannot find an overload for "CreateObjectByLogicalName" and the argument count: "4". At line:1 char:48_te + $objSAS = $objFactory.CreateObjectByLogicalName <<<< ("SASApp", $TRUE, "SASApp - Logical Workspace Server" , "" )     + CategoryInfo          : NotSpecified: (:) [], MethodException     + FullyQualifiedErrorId : MethodCountCouldNotFindBest That sounds like I just shouldn't be using 4 arguments. Hope someone can help with this. The SAS server runs SAS 9.4, the server itself is Windows 2008 R2. ... View more
Contact Me
Online Status
Offline
Date Last Visited
‎10-27-2016 03:35 AM
Likes from
View All
Quick links