LISTSERV at the University of Georgia
Menubar Imagemap
Home Browse Manage Request Manuals Register
Previous messageNext messagePrevious in topicNext in topicPrevious by same authorNext by same authorPrevious page (January 2002, week 1)Back to main SAS-L pageJoin or leave SAS-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:         Fri, 4 Jan 2002 10:25:17 -0600
Reply-To:     Sterling Price <ssprice@WAL-MART.COM>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         Sterling Price <ssprice@WAL-MART.COM>
Subject:      SAS/Connect signon problems
Content-Type: text/plain

Greetings all,

I have newly installed SAS 8.2 on a Win2K server, but I don't seem to be able to connect to the SAS/Connect spawner. Here's an example log:

34 OPTIONS COMAMID= tcp REMOTE = labhonts165; 35 FILENAME RLINK "c:\tcpwin.scr"; 36 signon; NOTE: Remote signon to LABHONTS165 commencing (SAS Release 8.02.02M0P012301). ERROR: Invalid or unspecified remote session id. Set OPTIONS REMOTE=session_id. ERROR: Remote signon to LABHONTS165 cancelled.

This same set of statements will sign on correctly with REMOTE = honts165 (honts165 is an existing NT 4.0 server that has had SAS/Connect installed for some time).

I've verified that the server is named labhonts165 in its network properties, that spawner.exe is running as a service, and that it is a started service. I can also successfully ping labhonts165 and see its shares by typing \\labhonts65 at the Run prompt on the Start menu.

Anyway, I think this is a different problem than I would get if labhonts165 wasn't on the network - I get a different error message if I use a remote session ID that I know doesn't exist:

37 OPTIONS COMAMID= tcp REMOTE = bogus; 38 FILENAME RLINK "c:\tcpwin.scr"; 39 signon; NOTE: Remote signon to BOGUS commencing (SAS Release 8.02.02M0P012301). ERROR: A communication subsystem partner link setup request failure has occurred. ERROR: Cannot locate TCP host 'BOGUS'. ERROR: Remote signon to BOGUS cancelled.

Can anyone suggest something else to try?

Thanks,

Sterling Price

********************************************************************** This email and any files transmitted with it are confidential and intended solely for the individual or entity to whom they are addressed. If you have received this email in error destroy it immediately. **********************************************************************


Back to: Top of message | Previous page | Main SAS-L page