|
Short Description
|
Demo to Yale from ASP SSurfer.ASPRequest doesn't work
|
|
Entered
|
By:
Tom Kent
When: 1999-07-09 11:17:06 Build: 1.03.07A
|
|
Categories
|
Type:
Problem
Department: Product
Category:
Troubleshooting
|
Description
|
I get the following when trying the demo to query a book by an author:
Publications by Ernest Hemingway
Error Occurred!
Sorry, but your query caused an error in the SurferScript
template that services this request-- the status is: Variable Value
RetCode -1
FailComponent TEACTION CONNECT
FailMessage Unable to connect to group LU_GROUP_2--return code=-4
FailSection cfsurfer.booklist
SessionKey
ScreenID
|
|
|
|
Append
|
By: Tom Kent When: 1999-07-09 11:33:52 New Status:
Pending IE
|
|
Comment
|
Build is 1.03.28E
But I'm only trying ASP demo to your server.
|
|
|
|
Append
|
By: WindSurfer When: 1999-07-09 13:14:47 New Status:
Pending Customer
|
|
Comment
|
The ASP demo part is working-- this time of year the Yale Library site goes up and down, so sometimes connections don't work--we just tweaked the script here to accomodate a new summer twist-- please try again now.
|
|
|
|
Append
|
By: WindSurfer When: 1999-07-09 17:22:36 New Status:
Pending Customer
|
|
Comment
|
Are you sure you are going against our server? If you are trying to do this against your own Screensurfer server from ASP, then you need to make sure that the Yale Library is defined at your LU_GROUP_2 in your Screensurfer configuration--either that or change the LU group that \screensurfer\hostserver\templates\cfsurfer.stml is pointing to.
If you are trying against our server, you should have the registry key HKEY_LOCAL_MACHINE/Software/Intelligent Environments/AspRequestTarget:Address set to "support.screensurfer.com".
To add LU_GROUP_2, use the Screensurfer console and access the Settings, then put *TN3270:orbis.yale.edu for the group, and give it a session range (if you only have one group at 1..1 for the first group, then you can give Yale 2..2).
|
|
|
|
Append
|
By: wfmiller When: 2000-09-26 11:37:43 New Status:
Pending IE
|
|
Comment
|
I thought *ANY should work, but after trying the suggestion
above, There was a DNS error shown in the diagnostic log.
So I did my own nslookup and was able to get a response
from the mainframe using '*TN3270:130.132.21.133'. Is there
any way to use *ANY and specify the actual host in the
CONNECT statement (while also correctly looking up IP's)?
Thanks,
Bill
WinNT/IIS 5.0
|