| Author |
Message |
Neil Pike
Guest
|
 Posted:
Sat Oct 09, 2004 12:40 am Post subject:
Re: connect with SNA Client 4.0 and HIS 2000 Client to HIS 2 |
|
|
Thanks Charles - useful info!
Neil Pike. Protech Computing Ltd
(Please post ALL replies to the newsgroup only unless indicated otherwise) |
|
| Back to top |
|
 |
HASCH
Guest
|
| Posted:
Mon Oct 11, 2004 3:15 pm Post subject:
Re: connect with SNA Client 4.0 and HIS 2000 Client to HIS 2 |
|
|
Hi,
XP/HIS2000 Client problem is solved.
The repackaged HIS2000 Client Software (intern Software Releases) was faulty.
Installing from original is working fine.
Now, "NT with SNA Client 4.0" & "XP with HIS2000 Client" & "XP with HIS2004
Client" running SNABASE as service working proper with SNA Server 2004.
Many Thanks to Neil and Charles
"Neil Pike" wrote:
| Quote: | Most peculiar! I one of the MS folks doesn't come up with anything soon you'll
need to raise it as an MS PSS case.
If you do, post the result/fix back here!
cheers
giving "act as part of..." and now the service is starting, but I get the
same error
message in the HIS 2004 Server log as I start with the local account:
"Connection from PC7009 denied because LSA logons are not supported. ---
Error Code : 4097"
The SNABASE Service is needed for the WRQ Reflection Application
Neil Pike. Protech Computing Ltd
(Please post ALL replies to the newsgroup only unless indicated otherwise)
|
|
|
| Back to top |
|
|
Neil Pike
Guest
|
| Posted:
Mon Oct 11, 2004 9:13 pm Post subject:
Re: connect with SNA Client 4.0 and HIS 2000 Client to HIS 2 |
|
|
Ahhhh! That would make a lot of sense.
What re-packaging tool did they use as a matter of interest?
| Quote: | XP/HIS2000 Client problem is solved.
The repackaged HIS2000 Client Software (intern Software Releases) was faulty.
Installing from original is working fine.
Now, "NT with SNA Client 4.0" & "XP with HIS2000 Client" & "XP with HIS2004
Client" running SNABASE as service working proper with SNA Server 2004.
Many Thanks to Neil and Charles
|
Neil Pike. Protech Computing Ltd
(Please post ALL replies to the newsgroup only unless indicated otherwise) |
|
| Back to top |
|
|
HASCH
Guest
|
| Posted:
Mon Oct 11, 2004 9:33 pm Post subject:
Re: connect with SNA Client 4.0 and HIS 2000 Client to HIS 2 |
|
|
Hi,
it's InstallShield Admin Studio,
but I don't know if this was a problem of the software
or of the packager.
"Neil Pike" wrote:
| Quote: | Ahhhh! That would make a lot of sense.
What re-packaging tool did they use as a matter of interest?
XP/HIS2000 Client problem is solved.
The repackaged HIS2000 Client Software (intern Software Releases) was faulty.
Installing from original is working fine.
Now, "NT with SNA Client 4.0" & "XP with HIS2000 Client" & "XP with HIS2004
Client" running SNABASE as service working proper with SNA Server 2004.
Many Thanks to Neil and Charles
Neil Pike. Protech Computing Ltd
(Please post ALL replies to the newsgroup only unless indicated otherwise)
|
|
|
| Back to top |
|
|
Neil Pike
Guest
|
| Posted:
Tue Oct 12, 2004 12:15 am Post subject:
Re: connect with SNA Client 4.0 and HIS 2000 Client to HIS 2 |
|
|
Could be either - but most re-packaging these days is automated by the tool, so
I'd tend to blame the tool. Though it obviously wasn't tested properly before they
have it to you to use!
Many vendors don't support re-packaging of their products. Not sure what MS's
stance is, but I'd be surprised if they supported anything other than standard MSI
transforms.
(As HIS 2004 comes with full silent install/customisation capability it doesn't
really need to be re-packaged anyway....)
| Quote: | it's InstallShield Admin Studio,
but I don't know if this was a problem of the software
or of the packager.
|
Neil Pike. Protech Computing Ltd
(Please post ALL replies to the newsgroup only unless indicated otherwise) |
|
| Back to top |
|
|
Jonesie
Guest
|
| Posted:
Tue Mar 01, 2005 6:09 pm Post subject:
SNA Client 4.0 and HIS 2004 Server |
|
|
Does anyone have any experience with this combination?
I am (still!) in the process of upgrading from NT4 to Win2003. We still have
many NT SNA 4 clients but want to reirect them to use new HIS 2004 servers
until the desktop upgrades are completed.
When attempting a test connection from an Nt4 SNA4 (sp4) client to a new
2003 / HIS2004 server (simply using the 3270 Demo) I get the following event
on the server, as well as a failed sponsor connection error on the client. XP
clients work fine with HIS04 3270 client. I am using a known domain service
account on the NT clients. Note - I have this all working fine in a testbed
env, but am at a total loss as to why this error appears in production.
Event ID: 23
Connection Failure
Connection = TEST
Link Service = SNADEMO1
Outage Code = 0011
EXPLANATION
A link service reported a connection failure to the node. See below for more
information on the outage code that caused the connection to fail.
TOKEN RING, ETHERNET OR FDDI
0011
Data Set Ready (DSR) failure. The remote system has dropped the line, or the
modem has disconnected.
If this problem is occurring while initiating a dial-up SDLC connection,
confirm that the switched PU on the host is not already in use, or that the
Host Integration Server SNA SDLC Local Node ID matches a valid switched PU
definition in VTAM.
Any help gratefully received!
Thanks,
Mark. |
|
| Back to top |
|
|
Charles Ezzell (MSFT)
Guest
|
| Posted:
Wed Mar 02, 2005 6:59 pm Post subject:
Re: SNA Client 4.0 and HIS 2004 Server |
|
|
The link failure is a "bug" in the demo scripts. This can happen at times,
usually to some external issue, but since it is not a production type
problem (demo links are only for testing purposes, as is) it has not been
investigated fully.
More important to know would be what is the actual error your client is
receiving on the failed sponsor connection. Is the client getting any event
log errors that would have more details?
Charles
"Jonesie" <Jonesie@discussions.microsoft.com> wrote in message
news:191DEB9B-1257-41E1-B273-34A1CC84020E@microsoft.com...
| Quote: | Does anyone have any experience with this combination?
I am (still!) in the process of upgrading from NT4 to Win2003. We still
have
many NT SNA 4 clients but want to reirect them to use new HIS 2004 servers
until the desktop upgrades are completed.
When attempting a test connection from an Nt4 SNA4 (sp4) client to a new
2003 / HIS2004 server (simply using the 3270 Demo) I get the following
event
on the server, as well as a failed sponsor connection error on the client.
XP
clients work fine with HIS04 3270 client. I am using a known domain
service
account on the NT clients. Note - I have this all working fine in a
testbed
env, but am at a total loss as to why this error appears in production.
Event ID: 23
Connection Failure
Connection = TEST
Link Service = SNADEMO1
Outage Code = 0011
EXPLANATION
A link service reported a connection failure to the node. See below for
more
information on the outage code that caused the connection to fail.
TOKEN RING, ETHERNET OR FDDI
0011
Data Set Ready (DSR) failure. The remote system has dropped the line, or
the
modem has disconnected.
If this problem is occurring while initiating a dial-up SDLC connection,
confirm that the switched PU on the host is not already in use, or that
the
Host Integration Server SNA SDLC Local Node ID matches a valid switched PU
definition in VTAM.
Any help gratefully received!
Thanks,
Mark. |
|
|
| Back to top |
|
|
Jonesie
Guest
|
| Posted:
Thu Mar 03, 2005 4:59 pm Post subject:
Re: SNA Client 4.0 and HIS 2004 Server |
|
|
Thanks Charles, the client app event log just displays the start of sanbase
followed by "This service terminated by administrator - EXPLANATION - The
process was terminated by the administrator, using either the SNA Server
Admin program or the SNA Server command-line interface."
But are you saying the likelihood is that when I configure a mainframe
connection, then this problem may not occur?
By the way, I have run a trace on the client which admittedly does not mean
a lot to me. Is there anything in it I should look out for?
Thanks again,
Mark.
"Charles Ezzell (MSFT)" wrote:
| Quote: | The link failure is a "bug" in the demo scripts. This can happen at times,
usually to some external issue, but since it is not a production type
problem (demo links are only for testing purposes, as is) it has not been
investigated fully.
More important to know would be what is the actual error your client is
receiving on the failed sponsor connection. Is the client getting any event
log errors that would have more details?
Charles
"Jonesie" <Jonesie@discussions.microsoft.com> wrote in message
news:191DEB9B-1257-41E1-B273-34A1CC84020E@microsoft.com...
Does anyone have any experience with this combination?
I am (still!) in the process of upgrading from NT4 to Win2003. We still
have
many NT SNA 4 clients but want to reirect them to use new HIS 2004 servers
until the desktop upgrades are completed.
When attempting a test connection from an Nt4 SNA4 (sp4) client to a new
2003 / HIS2004 server (simply using the 3270 Demo) I get the following
event
on the server, as well as a failed sponsor connection error on the client.
XP
clients work fine with HIS04 3270 client. I am using a known domain
service
account on the NT clients. Note - I have this all working fine in a
testbed
env, but am at a total loss as to why this error appears in production.
Event ID: 23
Connection Failure
Connection = TEST
Link Service = SNADEMO1
Outage Code = 0011
EXPLANATION
A link service reported a connection failure to the node. See below for
more
information on the outage code that caused the connection to fail.
TOKEN RING, ETHERNET OR FDDI
0011
Data Set Ready (DSR) failure. The remote system has dropped the line, or
the
modem has disconnected.
If this problem is occurring while initiating a dial-up SDLC connection,
confirm that the switched PU on the host is not already in use, or that
the
Host Integration Server SNA SDLC Local Node ID matches a valid switched PU
definition in VTAM.
Any help gratefully received!
Thanks,
Mark.
|
|
|
| Back to top |
|
|
Charles Ezzell (MSFT)
Guest
|
| Posted:
Thu Mar 03, 2005 6:10 pm Post subject:
Re: SNA Client 4.0 and HIS 2004 Server |
|
|
Please forward the trace here. It does sound like a security issue, and
hopefully the client traces can tell me for sure exactly where it is
failing.
Thanks,
Charles
"Jonesie" <Jonesie@discussions.microsoft.com> wrote in message
news:DF2FDD63-F2D1-43DB-8778-84ABCB440364@microsoft.com...
| Quote: |
Thanks Charles, the client app event log just displays the start of
sanbase
followed by "This service terminated by administrator - EXPLANATION -
The
process was terminated by the administrator, using either the SNA Server
Admin program or the SNA Server command-line interface."
But are you saying the likelihood is that when I configure a mainframe
connection, then this problem may not occur?
By the way, I have run a trace on the client which admittedly does not
mean
a lot to me. Is there anything in it I should look out for?
Thanks again,
Mark.
"Charles Ezzell (MSFT)" wrote:
The link failure is a "bug" in the demo scripts. This can happen at
times,
usually to some external issue, but since it is not a production type
problem (demo links are only for testing purposes, as is) it has not been
investigated fully.
More important to know would be what is the actual error your client is
receiving on the failed sponsor connection. Is the client getting any
event
log errors that would have more details?
Charles
"Jonesie" <Jonesie@discussions.microsoft.com> wrote in message
news:191DEB9B-1257-41E1-B273-34A1CC84020E@microsoft.com...
Does anyone have any experience with this combination?
I am (still!) in the process of upgrading from NT4 to Win2003. We still
have
many NT SNA 4 clients but want to reirect them to use new HIS 2004
servers
until the desktop upgrades are completed.
When attempting a test connection from an Nt4 SNA4 (sp4) client to a
new
2003 / HIS2004 server (simply using the 3270 Demo) I get the following
event
on the server, as well as a failed sponsor connection error on the
client.
XP
clients work fine with HIS04 3270 client. I am using a known domain
service
account on the NT clients. Note - I have this all working fine in a
testbed
env, but am at a total loss as to why this error appears in production.
Event ID: 23
Connection Failure
Connection = TEST
Link Service = SNADEMO1
Outage Code = 0011
EXPLANATION
A link service reported a connection failure to the node. See below for
more
information on the outage code that caused the connection to fail.
TOKEN RING, ETHERNET OR FDDI
0011
Data Set Ready (DSR) failure. The remote system has dropped the line,
or
the
modem has disconnected.
If this problem is occurring while initiating a dial-up SDLC
connection,
confirm that the switched PU on the host is not already in use, or that
the
Host Integration Server SNA SDLC Local Node ID matches a valid switched
PU
definition in VTAM.
Any help gratefully received!
Thanks,
Mark.
|
|
|
| Back to top |
|
|
Jonesie
Guest
|
| Posted:
Thu Mar 03, 2005 6:37 pm Post subject:
Re: SNA Client 4.0 and HIS 2004 Server |
|
|
Is there an email address I should use? I'd rather not post all my network
details on the forum.
"Charles Ezzell (MSFT)" wrote:
| Quote: | Please forward the trace here. It does sound like a security issue, and
hopefully the client traces can tell me for sure exactly where it is
failing.
Thanks,
Charles
"Jonesie" <Jonesie@discussions.microsoft.com> wrote in message
news:DF2FDD63-F2D1-43DB-8778-84ABCB440364@microsoft.com...
Thanks Charles, the client app event log just displays the start of
sanbase
followed by "This service terminated by administrator - EXPLANATION -
The
process was terminated by the administrator, using either the SNA Server
Admin program or the SNA Server command-line interface."
But are you saying the likelihood is that when I configure a mainframe
connection, then this problem may not occur?
By the way, I have run a trace on the client which admittedly does not
mean
a lot to me. Is there anything in it I should look out for?
Thanks again,
Mark.
"Charles Ezzell (MSFT)" wrote:
The link failure is a "bug" in the demo scripts. This can happen at
times,
usually to some external issue, but since it is not a production type
problem (demo links are only for testing purposes, as is) it has not been
investigated fully.
More important to know would be what is the actual error your client is
receiving on the failed sponsor connection. Is the client getting any
event
log errors that would have more details?
Charles
"Jonesie" <Jonesie@discussions.microsoft.com> wrote in message
news:191DEB9B-1257-41E1-B273-34A1CC84020E@microsoft.com...
Does anyone have any experience with this combination?
I am (still!) in the process of upgrading from NT4 to Win2003. We still
have
many NT SNA 4 clients but want to reirect them to use new HIS 2004
servers
until the desktop upgrades are completed.
When attempting a test connection from an Nt4 SNA4 (sp4) client to a
new
2003 / HIS2004 server (simply using the 3270 Demo) I get the following
event
on the server, as well as a failed sponsor connection error on the
client.
XP
clients work fine with HIS04 3270 client. I am using a known domain
service
account on the NT clients. Note - I have this all working fine in a
testbed
env, but am at a total loss as to why this error appears in production.
Event ID: 23
Connection Failure
Connection = TEST
Link Service = SNADEMO1
Outage Code = 0011
EXPLANATION
A link service reported a connection failure to the node. See below for
more
information on the outage code that caused the connection to fail.
TOKEN RING, ETHERNET OR FDDI
0011
Data Set Ready (DSR) failure. The remote system has dropped the line,
or
the
modem has disconnected.
If this problem is occurring while initiating a dial-up SDLC
connection,
confirm that the switched PU on the host is not already in use, or that
the
Host Integration Server SNA SDLC Local Node ID matches a valid switched
PU
definition in VTAM.
Any help gratefully received!
Thanks,
Mark.
|
|
|
| Back to top |
|
|
Steve Smith
Guest
|
| Posted:
Fri Mar 04, 2005 11:11 pm Post subject:
Re: SNA Client 4.0 and HIS 2004 Server |
|
|
Hello Charles, the traces for Jonesie should be with you shortly...
Thanks, Steve Smith.
"Jonesie" wrote:
| Quote: |
Is there an email address I should use? I'd rather not post all my network
details on the forum.
"Charles Ezzell (MSFT)" wrote:
Please forward the trace here. It does sound like a security issue, and
hopefully the client traces can tell me for sure exactly where it is
failing.
Thanks,
Charles
"Jonesie" <Jonesie@discussions.microsoft.com> wrote in message
news:DF2FDD63-F2D1-43DB-8778-84ABCB440364@microsoft.com...
Thanks Charles, the client app event log just displays the start of
sanbase
followed by "This service terminated by administrator - EXPLANATION -
The
process was terminated by the administrator, using either the SNA Server
Admin program or the SNA Server command-line interface."
But are you saying the likelihood is that when I configure a mainframe
connection, then this problem may not occur?
By the way, I have run a trace on the client which admittedly does not
mean
a lot to me. Is there anything in it I should look out for?
Thanks again,
Mark.
"Charles Ezzell (MSFT)" wrote:
The link failure is a "bug" in the demo scripts. This can happen at
times,
usually to some external issue, but since it is not a production type
problem (demo links are only for testing purposes, as is) it has not been
investigated fully.
More important to know would be what is the actual error your client is
receiving on the failed sponsor connection. Is the client getting any
event
log errors that would have more details?
Charles
"Jonesie" <Jonesie@discussions.microsoft.com> wrote in message
news:191DEB9B-1257-41E1-B273-34A1CC84020E@microsoft.com...
Does anyone have any experience with this combination?
I am (still!) in the process of upgrading from NT4 to Win2003. We still
have
many NT SNA 4 clients but want to reirect them to use new HIS 2004
servers
until the desktop upgrades are completed.
When attempting a test connection from an Nt4 SNA4 (sp4) client to a
new
2003 / HIS2004 server (simply using the 3270 Demo) I get the following
event
on the server, as well as a failed sponsor connection error on the
client.
XP
clients work fine with HIS04 3270 client. I am using a known domain
service
account on the NT clients. Note - I have this all working fine in a
testbed
env, but am at a total loss as to why this error appears in production.
Event ID: 23
Connection Failure
Connection = TEST
Link Service = SNADEMO1
Outage Code = 0011
EXPLANATION
A link service reported a connection failure to the node. See below for
more
information on the outage code that caused the connection to fail.
TOKEN RING, ETHERNET OR FDDI
0011
Data Set Ready (DSR) failure. The remote system has dropped the line,
or
the
modem has disconnected.
If this problem is occurring while initiating a dial-up SDLC
connection,
confirm that the switched PU on the host is not already in use, or that
the
Host Integration Server SNA SDLC Local Node ID matches a valid switched
PU
definition in VTAM.
Any help gratefully received!
Thanks,
Mark.
|
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in