Hi all, We are testing AMO 4.3 and Excel 2010 on XP with an AIX server running SAS 9.2M3.  We have observed that with "small" libraries - in the range of 200 tables - we can readily open any SAS table we that we have access to given our metadata permissions.  However, when the number of tables in the library is large - over 2000 in the one we're using - AMO returns the following error when we click OK to open the table (we are able to browse the library to select our table): This same table can be opened by the same user on the same client machine in EG 4.3. Has anyone else seen this kind of behavior? TIA Nick ... View more

Hi All, I'm trying to create a user session table (a text file would also be fine) for managing user sessions, in particular for correlating orphan processes and work libraries to users. I'm trying to have each EG user session update a table that contains four pieces of information - the user, the PID, the start date and time, and the work library path. The code below generates the table, but when i put it into my workspace server's autoexec_usermods.sas my EG session can't see any libraries (the library icon in the server tree view is visible, but when i try to expand it the + just disappears without showing any libraries). Has anyone built something similar, or used a mechanism other than the autoexec_usermods.sas to run code for each EG user session? Thanks, Nick data myinfo; length pid $ 8 user $ 16; pid="&sysjobid"; user="&sysuserid"; sdate="&sysdate"; stime="&systime"; length work $ 255; work=&sasworklocation; run; libname t '/usr/local/sasv9/EBI9.2/Lev1/SASApp/pidlog'; proc append base=t.pidlog data=myinfo force; run; libname t; ... View more

Hi all, We've noticed a difference between how EG 4.1 and EG 4.2 generate (or store) session parameters. EG 4.1 generates this output: %put &_CLIENTUSERNAME &_CLIENTMACHINE; nick.welke D03CB4 And EG 4.2 generates this: %put &_CLIENTUSERNAME &_CLIENTMACHINE; 'nick.welke' 'D03CB4' Does anyone else get this same result? Is it something we can disable in 4.2 to remove the quotes? TIA Nick ... View more

Hi all, Has anyone run into a minimum speed or bandwidth requirement for the connection between EG and Workspace (and Metadata) server? We're working with a client that has a central SAS server at one site and several analysts at another site - and the two are connected with a fairly old and slow link. Increasing the bandwidth is costly and moving the server is not an option for reasons beyond our control. To justify the expense of increasing the bandwidth I need to provide a "minimum viable" speed and am hoping for some anecdotal information from the community... TIA Nick ... View more

In testing EG4.1 (and SAS 9.1.3 SP4 on Solaris) we received an error that appears to be the result of using a unix login not associated with a metadata identity. I'd like to confirm if this is the case, or see if anyone else has run into this error. The EG error is: An error occurred executing the stored process job "Sample: Stored Process Macro Variables". The stored process library failed to provide a data set event interface. Connected.0x0metalooklziida86860115931E31-667F-11D5-8804-00C04F35AC8CSASStoredProcess.StoredProcessServer.1.0SASApp - Stored Process ServerDefaultAuth6700 This error occurs on the second and subsequent attempts to run a stored process, but the first one runs successfully. Same error regardless of whether we run the same stored process or a different stored process (testing only samples). There were no events in the stored process logs corresponding to this error. In troubleshooting this, we noticed that the user was connected as "UNKNOWN" - not the user and not PUBLIC. In further checking we realized that the user had a metadata identity but not a unix system login, so while the connection to the metadata was being made as a metadata user (who has an LDAP login defined in their metadata logins in SMC User Manager) the connection to the workspace server was being made as a different user - EG was prompting (only on the first attempt to run a stored process) for a userID and password and the tester provided a valid unix user/pass pair. These credentials are not associated with the metadata user, but rather with a metadata group. We then realized the user being tested wasn't a member of this group. After we added the metadata user as a member of the group the error disappeared. So, all that to say, has anyone seen this before? Is the "stored process library failed to provide a data set event interface" error the expected result of using valid but unassociated credentials for the workspace server? Thanks Nick ... View more

I've looked through the admin guide for eguide 4 (among other places) and can't find any reference to proxy servers. Does EG support a configuration with a proxy server between the server and EG? TIA Nick ... View more