Hello,

We currently have two HIS Servers in a subdomain, both running Windows
Server 2003 Standard Edition, SP2 and both have Host Integration
Server 2000, SP1 installed.  One is a primary and one is a backup.
The backup server is very old and needs to be retired and we also need
to upgrade to HIS 2006.  We are trying to replace the old backup
server with a newer server and have run into problems.

The old backup server has been shut down but not removed from the SNA
subdomain yet.  We installed HIS 2006 on the new backup server, which
is also running Windows 2003 Standard Edition, SP2.  We have installed
only the "SNA Gateway", "DLC Protocol" and "Documentation" options.
The "Configuration Tool" ran and I was able to enter the subdomain,
choose "Secondary Configuration Server" as the Server Role and enter
the Primary Server Name.  After some initial problems, the new backup
server now sees the subdomain and the HIS 2000 servers.

The problem we are now having is when we try to create a new Link
Service on the HIS 2006 backup server.  In the SNA Manager on the new
server, when I right-click on the new server's "Link Services" folder
then select "New" and "Link Services" I receive the below error
message.

"Only the primary Host Integration Server computer can write to an
older configuration file.  Doing so will upgrade the file to the
current version, after which any Host Integration Server computer may
write to it."

If I try to create the new link from the HIS 2000 Primary Server I am
able to highlight the "DLC 802.2 Link Service" but when I click the
"Add" button nothing happens.

Any help would be greatly appreciated.

Thank you,
Donald A. Martin, Jr.

Donald,

Create the link service on the HIS2006 server using linkcfg.exe first.  Then 
you should be able to do the "SNA" side of it from the primary HIS2000 server.

That's what I did with a similar upgrade from SNA4/2000 to HIS2004 a while 
back.

 Neil Pike.  Protech Computing Ltd
 Microsoft SNA/HIS MVP
 https://mvp.support.microsoft.com/profile=BE66F0D8-9D78-47EF-840A-08E6D8522A2D
 http://www.linkedin.com/in/neilpike

On Dec 6, 2:54 am, Neil Pike  wrote:
> Donald,
>
> Create the link service on the HIS2006 server using linkcfg.exe first.  Then
> you should be able to do the "SNA" side of it from the primary HIS2000 server.
>
> That's what I did with a similar upgrade from SNA4/2000 to HIS2004 a while
> back.
>
>  Neil Pike.  Protech Computing Ltd
>  Microsoft SNA/HIS MVP
>  https://mvp.support.microsoft.com/profile=BE66F0D8-9D78-47EF-840A-08E...
>  http://www.linkedin.com/in/neilpike

Neil,

When I run the below command line I get an error that states "The
LSTYPE parameter must be included in the command string."

linkcfg linksvc /lstype "DLC 802.2 Link Service"

Am I missing an options somewhere?

Thank you,
Donald A. Martin, Jr.

On Dec 6, 9:38 am, Mart...@whitecastle.com wrote:
> On Dec 6, 2:54 am, Neil Pike  wrote:
>
> > Donald,
>
> > Create the link service on the HIS2006 server using linkcfg.exe first.  Then
> > you should be able to do the "SNA" side of it from the primary HIS2000 server.
>
> > That's what I did with a similar upgrade from SNA4/2000 to HIS2004 a while
> > back.
>
> >  Neil Pike.  Protech Computing Ltd
> >  Microsoft SNA/HIS MVP
> >  https://mvp.support.microsoft.com/profile=BE66F0D8-9D78-47EF-840A-08E...
> >  http://www.linkedin.com/in/neilpike
>
> Neil,
>
> When I run the below command line I get an error that states "The
> LSTYPE parameter must be included in the command string."
>
> linkcfg linksvc /lstype "DLC 802.2 Link Service"
>
> Am I missing an options somewhere?
>
> Thank you,
> Donald A. Martin, Jr.

Neil,

I found my typo and added a collen to the command so it now looks like
the below.

linkcfg linksvc /lstype:"DLC 802.2 Link Service"

I don't get the error anymore but now it is prompting me for other
options.  Do you know of any documentaion for the linkcfg.exe command
so I determine what I need to enter for the other options?

Thank you,
Donald A. Martin, Jr.

wrote ...
> I don't get the error anymore but now it is prompting me for other
> options.  Do you know of any documentaion for the linkcfg.exe command
> so I determine what I need to enter for the other options?

Hi Donald,

Do these help?

Linkcfg options for the DLC 802.2 link service.
http://technet.microsoft.com/en-us/library/ms965236.aspx

How to Use the SNA Server Linkcfg.exe on Windows 2000
http://support.microsoft.com/kb/262807

Let us know how you get on.

-- 
Andrew McLaren
amclar (at) optusnet dot com dot au

On Dec 6, 10:03 am, "Andrew McLaren"  wrote:
>  wrote ...
>
> > I don't get the error anymore but now it is prompting me for other
> > options.  Do you know of any documentaion for the linkcfg.exe command
> > so I determine what I need to enter for the other options?
>
> Hi Donald,
>
> Do these help?
>
> Linkcfg options for the DLC 802.2 link service.http://technet.microsoft.com/en-us/library/ms965236.aspx
>
> How to Use the SNA Server Linkcfg.exe on Windows 2000http://support.microsoft.com/kb/262807
>
> Let us know how you get on.
>
> --
> Andrew McLaren
> amclar (at) optusnet dot com dot au

Andrew,

Thanks for the links, they really helped.

I was able to create the Link Service successfully using the
linkcfg.exe command line.  I was then able to create the SNA
Connection from the Primary Server via the SNA Manager but once I
rebooted the new backup server, the SNABase service would nolonger
stay running.  It will start and run for about 30 seconds then stop.
The entry in the Application Log shows that the service was stopped by
the Administrator.  I've googled for this problem and searched
Microsoft's Knoweldge Base but couldn't find anything.  Do you have
any ideas?

Thank you,
Donald A. Martin, Jr.

wrote ...
> rebooted the new backup server, the SNABase service would nolonger
> stay running.  It will start and run for about 30 seconds then stop.
> The entry in the Application Log shows that the service was stopped by
> the Administrator.  I've googled for this problem and searched

Hi Donald

What is the event ID and text of the event?

And, what happens if you try to start Snabase manually - eg by doing "net 
start snabase"?

-- 
Andrew McLaren
amclar (at) optusnet dot com dot au

Donald - out of interest, what did you do to finally resolve the below issue?
 
> After some initial problems, the new backup
> server now sees the subdomain and the HIS 2000 servers.


 Neil Pike.  Protech Computing Ltd
 Microsoft SNA/HIS MVP
 https://mvp.support.microsoft.com/profile=BE66F0D8-9D78-47EF-840A-08E6D8522A2D
 http://www.linkedin.com/in/neilpike

Donald,
 
 That's bizarre.  Anything in the eventlogs on the primary server to indicate whether it might be issuing 
the shutdown?
 
 I assume snabase is set to automatic startup?

 Any systems management tools running that might, for whatever reason, be stopping services that it's not 
expecting to see running?  (Shot in the dark, but you never know...)
 
 Other than that, I'd be turning on auditing to see who/what is connecting to the server and might be 
telling the service to stop.
  
> I was able to create the Link Service successfully using the
> linkcfg.exe command line.  I was then able to create the SNA
> Connection from the Primary Server via the SNA Manager but once I
> rebooted the new backup server, the SNABase service would nolonger
> stay running.  It will start and run for about 30 seconds then stop.
> The entry in the Application Log shows that the service was stopped by
> the Administrator.  I've googled for this problem and searched
> Microsoft's Knoweldge Base but couldn't find anything.  Do you have
> any ideas?

 Neil Pike.  Protech Computing Ltd
 Microsoft SNA/HIS MVP
 https://mvp.support.microsoft.com/profile=BE66F0D8-9D78-47EF-840A-08E6D8522A2D
 http://www.linkedin.com/in/neilpike

On Dec 7, 5:49 am, Neil Pike  wrote:
>  Donald,
>
>  That's bizarre.  Anything in the eventlogs on the primary server to indicate whether it might be issuing
> the shutdown?
>
>  I assume snabase is set to automatic startup?
>
>  Any systems management tools running that might, for whatever reason, be stopping services that it's not
> expecting to see running?  (Shot in the dark, but you never know...)
>
>  Other than that, I'd be turning on auditing to see who/what is connecting to the server and might be
> telling the service to stop.
>
> > I was able to create the Link Service successfully using the
> > linkcfg.exe command line.  I was then able to create the SNA
> > Connection from the Primary Server via the SNA Manager but once I
> > rebooted the new backup server, the SNABase service would nolonger
> > stay running.  It will start and run for about 30 seconds then stop.
> > The entry in the Application Log shows that the service was stopped by
> > the Administrator.  I've googled for this problem and searched
> > Microsoft's Knoweldge Base but couldn't find anything.  Do you have
> > any ideas?
>
>  Neil Pike.  Protech Computing Ltd
>  Microsoft SNA/HIS MVP
>  https://mvp.support.microsoft.com/profile=BE66F0D8-9D78-47EF-840A-08E...
>  http://www.linkedin.com/in/neilpike

Neail,

Yes, the SnaBase is set to start automatically.  I didn't see any
events on the primary server that would indicate it was sending a
shutdown command to the backup server.  There are no other system
management tools running on the server that I know of.

I've copied the text of the event that shows the shutdown just on the
off chance it would give you an idea.

------------------------------------------------------------------------------------------------------------------------------------------
Event Type:	Information
Event Source:	SNA Base Service
Event Category:	None
Event ID:	590
Date:		12/07/2007
Time:		11:19:02 AM
User:		WCS\sna
Computer:	WCM23004
Description:
This service terminated by administrator

 EXPLANATION
 The process was terminated by the administrator, using either Host
Integration Server SNA Manager or the Host Integration Server SNA
command-line interface.

 ACTION
 No action is necessary.
------------------------------------------------------------------------------------------------------------------------------------------

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

As for how we resolved the original problem, we applied a bunch of
Microsoft updates and rebooted all of our servers.  We just presumed
that one of the updates fixed our problem.

Thank you,
Donald A. Martin, Jr.

Donald,
 
 The full message doesn't help too much other than confirming it looks like a 
HIS component is shutting it down via an application level call, as opposed to 
something just issuing a service shutdown command.  (I'm pretty sure snabase 
doesn't write out any such message if it's shut down by the service method).
 
 As to why it's being shutdown, that doesn't make much sense.  I suspect it's 
going to need a call to MS PSS and a bunch of tracing to show what's going on.
 
 Does the snabase shutdown issue only occur since the link service was 
installed/configured on the server?
 
 Have you defined any connections over the link service yet?  One thing that's 
just springing to mind is maybe HIS is shutting it down because it doesn't 
think there are any sna resources on the server...
 
 Neil Pike.  Protech Computing Ltd
 Microsoft SNA/HIS MVP
 https://mvp.support.microsoft.com/profile=BE66F0D8-9D78-47EF-840A-08E6D8522A2D
 http://www.linkedin.com/in/neilpike

On Dec 7, 1:15 pm, Neil Pike  wrote:
>  Donald,
>
>  The full message doesn't help too much other than confirming it looks like a
> HIS component is shutting it down via an application level call, as opposed to
> something just issuing a service shutdown command.  (I'm pretty sure snabase
> doesn't write out any such message if it's shut down by the service method).
>
>  As to why it's being shutdown, that doesn't make much sense.  I suspect it's
> going to need a call to MS PSS and a bunch of tracing to show what's going on.
>
>  Does the snabase shutdown issue only occur since the link service was
> installed/configured on the server?
>
>  Have you defined any connections over the link service yet?  One thing that's
> just springing to mind is maybe HIS is shutting it down because it doesn't
> think there are any sna resources on the server...
>
>  Neil Pike.  Protech Computing Ltd
>  Microsoft SNA/HIS MVP
>  https://mvp.support.microsoft.com/profile=BE66F0D8-9D78-47EF-840A-08E...
>  http://www.linkedin.com/in/neilpike

This was the first time we had rebooted the server since we found
HIS2006 was seeing the subdomain so I'm not sure if the link service
caused the problem or if it would have broken with a reboot anyway.

I had defined an SNA connection for the new server via the SNA Manager
on the Primary Server, since I got the same error about writing to a
older version of the configuration file from the backup server.  I
didn't see the connetion on the backup server so I rebooted it to
reset the services.

Your earlier question about the SnaBase service being set to automatic
got me thinking about the other SNA services.  I went back through the
System Log and found this error when I rebooted the backup server.
I'm not sure how I missed it yesterday.

------------------------------------------------------------------------------------------------------------------------------------------
Event Type:	Information
Event Source:	Application Popup
Event Category:	None
Event ID:	26
Date:		12/06/2007
Time:		12:24:10 PM
User:		N/A
Computer:	WCM23004
Description:
Application popup: Host Integration Server   -   ERROR # 1004  :
SnaBase didn't find any Host Integration Server computers in your
domain WCS

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
------------------------------------------------------------------------------------------------------------------------------------------

There are then a couple of errors about HIS related services not
starting.  I'm not sure if it will help but here are the HIS related
services that are set to start automatically on the backup server.

SNA MngAgent
SNA RPC Service
SnaBase
SnaDlc1
SnaPrint
SnaPrint
SnaServer
TN3270

Thank you
Donald A. Martin, Jr.

Martin,

The SnaServer, SnaPrint, and TN3270 services are never set to start 
automatically by default. Most customers will change the SnaServer service 
so that is starts automatically. Customers that use TN3270 and/or SnaPrint 
will also typically autostart these services. If they are set to autostart 
now, they were changed manually to autostart.

DLC link services (e.g. SnaDlc1) would not normally be autostarted unless 
the link service was configured with the "Allow link service to be 
distributed" option enabled (e.g. /DISTRIBUTABLE:YES in linkcfg). This is 
only needed if you will be having remote HIS Servers connect to the link 
service remotely in a distributed HIS envinronment.

The Event 26 error is likely happening because one of these other services 
is trying to start and SNABASE is not running.

I am fairly certain that the SNABASE service is terminating because of 
security issues. What account are the SNA services on the primary HIS 2000 
Server running under and what account are the HIS 2006 services running 
under?

If they are using different accounts, it may be causing the issue. The 
security model used by HIS 2006 is much tighter than the model used by HIS 
2000. The service account used in HIS 2000 was pretty much given Admin 
rights. This no longer occurs when using HIS 2006.

You may want to contact Microsoft HIS support to assist here.

You can do the following to have traces that we would likely want to look at 
if you call support:

1) Run snatrace.exe
2) Highlight SnaBase in the list of trace items and click Properties.
3) Click the "Set All" button on the Internal Trace tab and click OK.
4) Minimize the SNA Trace Utility doalog.
5) Start SnaBase (Net start snabase).
6) Once you see that SnaBase stops again, restore the SNA Trace Utility 
dialog and click "Clear All Traces" to stop the traces.
7) Send us the resulting napint1.atf trace file in the C:\Program 
Files\Microsoft Host Integration Server\traces folder.

-- 
Stephen Jackson
Microsoft® HIS Support

Please do not send e-mail directly to this alias. This alias is for
newsgroup purposes only. This posting is provided "AS IS"
with no warranties, and confers no rights.


 wrote in message 
news:b51d416a-d598-4289-a919-4492e10dde86@v4g2000hsf.googlegroups.com...
> On Dec 7, 1:15 pm, Neil Pike  wrote:
>>  Donald,
>>
>>  The full message doesn't help too much other than confirming it looks 
>> like a
>> HIS component is shutting it down via an application level call, as 
>> opposed to
>> something just issuing a service shutdown command.  (I'm pretty sure 
>> snabase
>> doesn't write out any such message if it's shut down by the service 
>> method).
>>
>>  As to why it's being shutdown, that doesn't make much sense.  I suspect 
>> it's
>> going to need a call to MS PSS and a bunch of tracing to show what's 
>> going on.
>>
>>  Does the snabase shutdown issue only occur since the link service was
>> installed/configured on the server?
>>
>>  Have you defined any connections over the link service yet?  One thing 
>> that's
>> just springing to mind is maybe HIS is shutting it down because it 
>> doesn't
>> think there are any sna resources on the server...
>>
>>  Neil Pike.  Protech Computing Ltd
>>  Microsoft SNA/HIS MVP
>>  https://mvp.support.microsoft.com/profile=BE66F0D8-9D78-47EF-840A-08E...
>>  http://www.linkedin.com/in/neilpike
>
> This was the first time we had rebooted the server since we found
> HIS2006 was seeing the subdomain so I'm not sure if the link service
> caused the problem or if it would have broken with a reboot anyway.
>
> I had defined an SNA connection for the new server via the SNA Manager
> on the Primary Server, since I got the same error about writing to a
> older version of the configuration file from the backup server.  I
> didn't see the connetion on the backup server so I rebooted it to
> reset the services.
>
> Your earlier question about the SnaBase service being set to automatic
> got me thinking about the other SNA services.  I went back through the
> System Log and found this error when I rebooted the backup server.
> I'm not sure how I missed it yesterday.
>
> ------------------------------------------------------------------------------------------------------------------------------------------
> Event Type: Information
> Event Source: Application Popup
> Event Category: None
> Event ID: 26
> Date: 12/06/2007
> Time: 12:24:10 PM
> User: N/A
> Computer: WCM23004
> Description:
> Application popup: Host Integration Server   -   ERROR # 1004  :
> SnaBase didn't find any Host Integration Server computers in your
> domain WCS
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> ------------------------------------------------------------------------------------------------------------------------------------------
>
> There are then a couple of errors about HIS related services not
> starting.  I'm not sure if it will help but here are the HIS related
> services that are set to start automatically on the backup server.
>
> SNA MngAgent
> SNA RPC Service
> SnaBase
> SnaDlc1
> SnaPrint
> SnaPrint
> SnaServer
> TN3270
>
> Thank you
> Donald A. Martin, Jr.

Donald,

> This was the first time we had rebooted the server since we found
> HIS2006 was seeing the subdomain so I'm not sure if the link service
> caused the problem or if it would have broken with a reboot anyway.

 Pretty sure it would have broken anyway by the sound of it.
 
> Your earlier question about the SnaBase service being set to automatic
> got me thinking about the other SNA services.  I went back through the
> System Log and found this error when I rebooted the backup server.
> I'm not sure how I missed it yesterday.
> 
> Application popup: Host Integration Server   -   ERROR # 1004  :
> SnaBase didn't find any Host Integration Server computers in your
> domain WCS

 SNABase probably shut itself down then.  Look at the SNABase reg entries again to see how it's resolving the servers
 in the domain now.
 

 Neil Pike.  Protech Computing Ltd
 Microsoft SNA/HIS MVP
 https://mvp.support.microsoft.com/profile=BE66F0D8-9D78-47EF-840A-08E6D8522A2D
 http://www.linkedin.com/in/neilpike

On Dec 9, 6:58 am, Neil Pike  wrote:
> Donald,
>
> > This was the first time we had rebooted the server since we found
> > HIS2006 was seeing the subdomain so I'm not sure if the link service
> > caused the problem or if it would have broken with a reboot anyway.
>
>  Pretty sure it would have broken anyway by the sound of it.
>
> > Your earlier question about the SnaBase service being set to automatic
> > got me thinking about the other SNA services.  I went back through the
> > System Log and found this error when I rebooted the backup server.
> > I'm not sure how I missed it yesterday.
>
> > Application popup: Host Integration Server   -   ERROR # 1004  :
> > SnaBase didn't find any Host Integration Server computers in your
> > domain WCS
>
>  SNABase probably shut itself down then.  Look at the SNABase reg entries again to see how it's resolving the servers
>  in the domain now.
>
>  Neil Pike.  Protech Computing Ltd
>  Microsoft SNA/HIS MVP
>  https://mvp.support.microsoft.com/profile=BE66F0D8-9D78-47EF-840A-08E...
>  http://www.linkedin.com/in/neilpike

I noticed that the COM.CFG file on the Backup Server was not updated
so I manully copied the file from the Primary Server to the Backup
Server.  I was then able to successfully get into the SNA Manager
program and start the SNA Service, the TN3270 and the SNA Printing
from inside the SNA Manager.  I then rebooted the Backup Server and
everything started successfully.  Using the SNA Manager on the Primary
Server I was able to create the SNA Connection and add LUs.  I was
then able to successully connect to mainframe via the Backup Server
from a client.

However, I've still got two strange problems.  The first is that the
COM.CFG file is not getting pushed out to the Backup Server from the
Primary Server.  The second is that while everything shows up
correctly in the SNA Manager on the Primary Server, the SNA Manager on
the Backup Server shows the status of the Primary Server as "Status
Undetected".  Do these two problems indicate that I still have a
problem with the Backup Server or are these normal problems between a
HIS2006 Backup Server and a HIS2000 Primary Server?  If so, does
anyone know how to fix them?

Thank you,
Donald A. Martin, Jr.

Yes, you still have a problem. Primary HIS Servers notify backups that a 
configuration change has been made via normal UDP datagram updates. The 
backup HIS Servers will then connect to the primary HIS Server to copy the 
new COM.CFG.  It is a pull process, not a push.

The backup HIS Server is having problems communicating with the primary HIS 
Server which explains the symtoms.

Are there differences in the service accounts that are being used between 
the two HIS Servers?

I would suggest that you open a support case with MS HIS Support since this 
may likely require looking at HIS traces and permissions around the service 
accounts.

-- 
Stephen Jackson
Microsoft® HIS Support

Please do not send e-mail directly to this alias. This alias is for
newsgroup purposes only. This posting is provided "AS IS"
with no warranties, and confers no rights.


 wrote in message 
news:d471ce2b-f0c5-42b1-80cd-f2ff790de524@s19g2000prg.googlegroups.com...
> On Dec 9, 6:58 am, Neil Pike  wrote:
>> Donald,
>>
>> > This was the first time we had rebooted the server since we found
>> > HIS2006 was seeing the subdomain so I'm not sure if the link service
>> > caused the problem or if it would have broken with a reboot anyway.
>>
>>  Pretty sure it would have broken anyway by the sound of it.
>>
>> > Your earlier question about the SnaBase service being set to automatic
>> > got me thinking about the other SNA services.  I went back through the
>> > System Log and found this error when I rebooted the backup server.
>> > I'm not sure how I missed it yesterday.
>>
>> > Application popup: Host Integration Server   -   ERROR # 1004  :
>> > SnaBase didn't find any Host Integration Server computers in your
>> > domain WCS
>>
>>  SNABase probably shut itself down then.  Look at the SNABase reg entries 
>> again to see how it's resolving the servers
>>  in the domain now.
>>
>>  Neil Pike.  Protech Computing Ltd
>>  Microsoft SNA/HIS MVP
>>  https://mvp.support.microsoft.com/profile=BE66F0D8-9D78-47EF-840A-08E...
>>  http://www.linkedin.com/in/neilpike
>
> I noticed that the COM.CFG file on the Backup Server was not updated
> so I manully copied the file from the Primary Server to the Backup
> Server.  I was then able to successfully get into the SNA Manager
> program and start the SNA Service, the TN3270 and the SNA Printing
> from inside the SNA Manager.  I then rebooted the Backup Server and
> everything started successfully.  Using the SNA Manager on the Primary
> Server I was able to create the SNA Connection and add LUs.  I was
> then able to successully connect to mainframe via the Backup Server
> from a client.
>
> However, I've still got two strange problems.  The first is that the
> COM.CFG file is not getting pushed out to the Backup Server from the
> Primary Server.  The second is that while everything shows up
> correctly in the SNA Manager on the Primary Server, the SNA Manager on
> the Backup Server shows the status of the Primary Server as "Status
> Undetected".  Do these two problems indicate that I still have a
> problem with the Backup Server or are these normal problems between a
> HIS2006 Backup Server and a HIS2000 Primary Server?  If so, does
> anyone know how to fix them?
>
> Thank you,
> Donald A. Martin, Jr.

Donald,

 Yes, you have a problem - this isn't normal!
 
 I suspect that the service account you're using on the backup server has some sort of
 issue connecting to the primary server.  Maybe it lacks the "access this computer from the network"
 user right or something like that.
 
> However, I've still got two strange problems.  The first is that the
> COM.CFG file is not getting pushed out to the Backup Server from the
> Primary Server.  The second is that while everything shows up
> correctly in the SNA Manager on the Primary Server, the SNA Manager on
> the Backup Server shows the status of the Primary Server as "Status
> Undetected".  Do these two problems indicate that I still have a
> problem with the Backup Server or are these normal problems between a
> HIS2006 Backup Server and a HIS2000 Primary Server?  If so, does
> anyone know how to fix them?
> 
> Thank you,
> Donald A. Martin, Jr.


 Neil Pike.  Protech Computing Ltd
 Microsoft SNA/HIS MVP
 https://mvp.support.microsoft.com/profile=BE66F0D8-9D78-47EF-840A-08E6D8522A2D
 http://www.linkedin.com/in/neilpike

On Dec 11, 7:59 am, Neil Pike  wrote:
>  Donald,
>
>  Yes, you have a problem - this isn't normal!
>
>  I suspect that the service account you're using on the backup server has some sort of
>  issue connecting to the primary server.  Maybe it lacks the "access this computer from the network"
>  user right or something like that.
>
> > However, I've still got two strange problems.  The first is that the
> > COM.CFG file is not getting pushed out to the Backup Server from the
> > Primary Server.  The second is that while everything shows up
> > correctly in the SNA Manager on the Primary Server, the SNA Manager on
> > the Backup Server shows the status of the Primary Server as "Status
> > Undetected".  Do these two problems indicate that I still have a
> > problem with the Backup Server or are these normal problems between a
> > HIS2006 Backup Server and a HIS2000 Primary Server?  If so, does
> > anyone know how to fix them?
>
> > Thank you,
> > Donald A. Martin, Jr.
>
>  Neil Pike.  Protech Computing Ltd
>  Microsoft SNA/HIS MVP
>  https://mvp.support.microsoft.com/profile=BE66F0D8-9D78-47EF-840A-08E...
>  http://www.linkedin.com/in/neilpike

The same service account is being used on both the Primary and Backup
Servers.  This account is a member of the Administrators group.  I
checked the "Access this computer from the network" option in the
Local Security Settings on both servers.  I found Administrators and
Everyone are both listed.  Would the service account need to be
specifically listed or is there something else I should check?

Thank you,
Donald A. Martin, Jr.

Martin,

The following is from the HIS 2006 readme.htm:

Deploying Host Integration Server 2006 as a Backup

If you are deploying Host Integration Server 2006 as a backup in an existing 
Host Integration Server 2004, Host Integration Server 2000, or SNA Server 
4.0 domain, you must make the following configuration changes:

- Create a COMLOGS share pointing to <installdir>\system. Grant the service 
account and HIS administrators group Read access. This share is used by the 
SNA Manager when you are creating link services on remote computers.

- Add any users who need to perform administrative tasks to the local HIS 
Administrators group on the Host Integration Server 2006 computer.

- Users who create link services must be local administrators on the 
computer where the link services will be created.

- Use the same service account for the Host Integration Server 2006 server 
as is used for the Host Integration Server 2000/2004 or SNA Server 4.0 
servers. This will ensure that all components have the appropriate rights to 
perform their necessary functions.

Note that some new features on Host Integration Server 2006 will not be 
available until all servers in the subdomain have been upgraded.

Did you do all of these steps?

Thanks...

-- 
Stephen Jackson
Microsoft® HIS Support

Please do not send e-mail directly to this alias. This alias is for
newsgroup purposes only. This posting is provided "AS IS"
with no warranties, and confers no rights.


 wrote in message 
news:108285de-b3d6-4b2a-bf8b-8abc578d0271@y5g2000hsf.googlegroups.com...
> On Dec 11, 7:59 am, Neil Pike  wrote:
>>  Donald,
>>
>>  Yes, you have a problem - this isn't normal!
>>
>>  I suspect that the service account you're using on the backup server has 
>> some sort of
>>  issue connecting to the primary server.  Maybe it lacks the "access this 
>> computer from the network"
>>  user right or something like that.
>>
>> > However, I've still got two strange problems.  The first is that the
>> > COM.CFG file is not getting pushed out to the Backup Server from the
>> > Primary Server.  The second is that while everything shows up
>> > correctly in the SNA Manager on the Primary Server, the SNA Manager on
>> > the Backup Server shows the status of the Primary Server as "Status
>> > Undetected".  Do these two problems indicate that I still have a
>> > problem with the Backup Server or are these normal problems between a
>> > HIS2006 Backup Server and a HIS2000 Primary Server?  If so, does
>> > anyone know how to fix them?
>>
>> > Thank you,
>> > Donald A. Martin, Jr.
>>
>>  Neil Pike.  Protech Computing Ltd
>>  Microsoft SNA/HIS MVP
>>  https://mvp.support.microsoft.com/profile=BE66F0D8-9D78-47EF-840A-08E...
>>  http://www.linkedin.com/in/neilpike
>
> The same service account is being used on both the Primary and Backup
> Servers.  This account is a member of the Administrators group.  I
> checked the "Access this computer from the network" option in the
> Local Security Settings on both servers.  I found Administrators and
> Everyone are both listed.  Would the service account need to be
> specifically listed or is there something else I should check?
>
> Thank you,
> Donald A. Martin, Jr.

Stephen,

I don't know how I missed these but below is the status of each.

> - Create a COMLOGS share pointing to <installdir>\system. Grant the service
> account and HIS administrators group Read access. This share is used by the
> SNA Manager when you are creating link services on remote computers.

On the Backup Server, I have shared the C:\Program Files\Microsoft
Host Integration Server 2006\system folder as "COMLOGS".  This share
has the below permissions.  Since the service account is a member of
the Administrators and the HIS Administrators groups I did not add it
seperately.

Share Permissions
-----------------
Everyone - Read

Serurity Permissions
---------------------
Administrators - Full Control
Authenticated Users - Read & Execute
CREATOR OWNER - No Permissions
Everyone - Read
HIS Administrators - Full Control
HIS Runtime Users - Read & Execute
Server Operators - Modify
SYSTEM - Full Control

Does this same share need to be setup on the Primary Server also?

> - Add any users who need to perform administrative tasks to the local HIS
> Administrators group on the Host Integration Server 2006 computer.

The Backup Server is also a BDC so, as far as I know, there are no
local groups or users.  The service account we are using has been
added to the HIS Administrators group in AD.

> - Users who create link services must be local administrators on the
> computer where the link services will be created.

The service account is a member of the Administrators group for the
domain.

> - Use the same service account for the Host Integration Server 2006 server
> as is used for the Host Integration Server 2000/2004 or SNA Server 4.0
> servers. This will ensure that all components have the appropriate rights to
> perform their necessary functions.

We have used the same service account for both servers.

I have rebooted the Backup Server but the Primary Server is still
showing up as "Status Undetected".  Additionally, I made a change in
the SNA Manager on the Primary Server and saved the configuration but
the change has not replicated out to the Backup Server.  I'm presuming
there is still a permission problem somewhere but I'm not sure where.

Thank you,
Donald A. Martin, Jr.

Donald,

 The issue here is the share permissions which are overriding the ntfs file 
permissions.  Change the share permissions to Everyone FULL and you should be 
good to go..
 
> On the Backup Server, I have shared the C:\Program Files\Microsoft
> Host Integration Server 2006\system folder as "COMLOGS".  This share
> has the below permissions.  Since the service account is a member of
> the Administrators and the HIS Administrators groups I did not add it
> seperately.
> 
> Share Permissions
> -----------------
> Everyone - Read
> 
> Serurity Permissions
> ---------------------
> Administrators - Full Control
> Authenticated Users - Read & Execute
> CREATOR OWNER - No Permissions
> Everyone - Read
> HIS Administrators - Full Control
> HIS Runtime Users - Read & Execute
> Server Operators - Modify
> SYSTEM - Full Control

 Neil Pike.  Protech Computing Ltd
 Microsoft SNA/HIS MVP
 https://mvp.support.microsoft.com/profile=BE66F0D8-9D78-47EF-840A-08E6D8522A2D
 http://www.linkedin.com/in/neilpike

We don't recommend using Everyone Full Control for security reasons. It 
leaves the box open to attack.

I'd suggest that you open a case with PSS because we will likely need to 
look at some SnaBase traces at a minimum.

-- 
Stephen Jackson
Microsoft® HIS Support

Please do not send e-mail directly to this alias. This alias is for
newsgroup purposes only. This posting is provided "AS IS"
with no warranties, and confers no rights.


"Neil Pike"  wrote in message 
news:VA.00006579.080267c1@compuserve.com...
> Donald,
>
> The issue here is the share permissions which are overriding the ntfs file
> permissions.  Change the share permissions to Everyone FULL and you should 
> be
> good to go..
>
>> On the Backup Server, I have shared the C:\Program Files\Microsoft
>> Host Integration Server 2006\system folder as "COMLOGS". This share
>> has the below permissions. Since the service account is a member of
>> the Administrators and the HIS Administrators groups I did not add it
>> seperately.
>>
>> Share Permissions
>> -----------------
>> Everyone - Read
>>
>> Serurity Permissions
>> ---------------------
>> Administrators - Full Control
>> Authenticated Users - Read & Execute
>> CREATOR OWNER - No Permissions
>> Everyone - Read
>> HIS Administrators - Full Control
>> HIS Runtime Users - Read & Execute
>> Server Operators - Modify
>> SYSTEM - Full Control
>
> Neil Pike.  Protech Computing Ltd
> Microsoft SNA/HIS MVP
> https://mvp.support.microsoft.com/profile=BE66F0D8-9D78-47EF-840A-08E6D8522A2D
> http://www.linkedin.com/in/neilpike
>
>

Stephen,
 
 Unless I'm misunderstanding what Donald's provided, having the share 
permissions as everyone:read will nullify any ntfs security acl's in place on 
the actual files underneath it?  (For stuff that accesses the files via the 
share rather than a local c:\program files\.......... access?
 
 Isn't it the NTFS file acl's that you're not recommending everyone:full for?
 
> We don't recommend using Everyone Full Control for security reasons. It 
> leaves the box open to attack.
> 
> I'd suggest that you open a case with PSS because we will likely need to 
> look at some SnaBase traces at a minimum.


 Neil Pike.  Protech Computing Ltd
 Microsoft SNA/HIS MVP
 https://mvp.support.microsoft.com/profile=BE66F0D8-9D78-47EF-840A-08E6D8522A2D
 http://www.linkedin.com/in/neilpike

On Dec 11, 5:25 pm, Neil Pike  wrote:
>  Stephen,
>
>  Unless I'm misunderstanding what Donald's provided, having the share
> permissions as everyone:read will nullify any ntfs security acl's in place on
> the actual files underneath it?  (For stuff that accesses the files via the
> share rather than a local c:\program files\.......... access?
>
>  Isn't it the NTFS file acl's that you're not recommending everyone:full for?
>
> > We don't recommend using Everyone Full Control for security reasons. It 
> > leaves the box open to attack.
>
> > I'd suggest that you open a case with PSS because we will likely need to 
> > look at some SnaBase traces at a minimum.
>
>  Neil Pike.  Protech Computing Ltd
>  Microsoft SNA/HIS MVP
>  https://mvp.support.microsoft.com/profile=BE66F0D8-9D78-47EF-840A-08E...
>  http://www.linkedin.com/in/neilpike

Hello,

I've tried setting the Share Permissions to both "Change" and "Full
Control" and rebooting the Backup Server but the Primary Server is
still showing as "Status Undetected".  Additionally, the changes I
made in the SNA Manager on the Primary Server have not replicated to
the Backup Server.  Are there any other permissions on the Backup
Server or even the Primary Server that I should check?

Thank you,
Donald A. Martin, Jr.

Donald,
 
  As long as the service account is in the HIS Administrators group that's the 
only other "security" thing I can think of.   Can't think of anything else.
  
  If setting security auditing on at both ends doesn't show anything failing to 
access a file, obtain a user right etc. then you're down to a call to PSS and 
doing some snabase internal tracing to see what's going on.
 
> I've tried setting the Share Permissions to both "Change" and "Full
> Control" and rebooting the Backup Server but the Primary Server is
> still showing as "Status Undetected".  Additionally, the changes I
> made in the SNA Manager on the Primary Server have not replicated to
> the Backup Server.  Are there any other permissions on the Backup
> Server or even the Primary Server that I should check?

 Neil Pike.  Protech Computing Ltd
 Microsoft SNA/HIS MVP
 https://mvp.support.microsoft.com/profile=BE66F0D8-9D78-47EF-840A-08E6D8522A2D
 http://www.linkedin.com/in/neilpike

On Dec 13, 2:09 am, Neil Pike  wrote:
>  Donald,
>
>   As long as the service account is in the HIS Administrators group that's the
> only other "security" thing I can think of.   Can't think of anything else.
>
>   If setting security auditing on at both ends doesn't show anything failing to
> access a file, obtain a user right etc. then you're down to a call to PSS and
> doing some snabase internal tracing to see what's going on.
>
> > I've tried setting the Share Permissions to both "Change" and "Full
> > Control" and rebooting the Backup Server but the Primary Server is
> > still showing as "Status Undetected".  Additionally, the changes I
> > made in the SNA Manager on the Primary Server have not replicated to
> > the Backup Server.  Are there any other permissions on the Backup
> > Server or even the Primary Server that I should check?
>
>  Neil Pike.  Protech Computing Ltd
>  Microsoft SNA/HIS MVP
>  https://mvp.support.microsoft.com/profile=BE66F0D8-9D78-47EF-840A-08E...
>  http://www.linkedin.com/in/neilpike

Good News.  We had to reboot our Primary Server, which is also the
PDC, this morning and once it came back up, the Backup Server saw it
normally in the SNA Manager and changes I made from the Primary Server
replicated out to the Backup Server within a few minutes.  It looks
like my problem may have been that the Primary Server needed to be
rebooted.  Other than an SNA Trace, are there any utilities we can run
to confirm the Primary and Backup are now communicating consistently?

Thank you,
Donald A. Martin, Jr.

Donald,
 
 That's odd - can't see why a reboot would make any difference!  Had you previously 
tried restarting the SNA Services on the PDC?
 
 Best way to tell they're talking is to define new resources on the backup server 
from the primary and make sure they show up.  If that occurs then you're good to 
go.
 
> Good News.  We had to reboot our Primary Server, which is also the
> PDC, this morning and once it came back up, the Backup Server saw it
> normally in the SNA Manager and changes I made from the Primary Server
> replicated out to the Backup Server within a few minutes.  It looks
> like my problem may have been that the Primary Server needed to be
> rebooted.  Other than an SNA Trace, are there any utilities we can run
> to confirm the Primary and Backup are now communicating consistently?
> 
> Thank you,
> Donald A. Martin, Jr.


 Neil Pike.  Protech Computing Ltd
 Microsoft SNA/HIS MVP
 https://mvp.support.microsoft.com/profile=BE66F0D8-9D78-47EF-840A-08E6D8522A2D
 http://www.linkedin.com/in/neilpike

On Dec 13, 12:52 pm, Neil Pike  wrote:
>  Donald,
>
>  That's odd - can't see why a reboot would make any difference!  Had you previously
> tried restarting the SNA Services on the PDC?
>
>  Best way to tell they're talking is to define new resources on the backup server
> from the primary and make sure they show up.  If that occurs then you're good to
> go.
>
> > Good News.  We had to reboot our Primary Server, which is also the
> > PDC, this morning and once it came back up, the Backup Server saw it
> > normally in the SNA Manager and changes I made from the Primary Server
> > replicated out to the Backup Server within a few minutes.  It looks
> > like my problem may have been that the Primary Server needed to be
> > rebooted.  Other than an SNA Trace, are there any utilities we can run
> > to confirm the Primary and Backup are now communicating consistently?
>
> > Thank you,
> > Donald A. Martin, Jr.
>
>  Neil Pike.  Protech Computing Ltd
>  Microsoft SNA/HIS MVP
>  https://mvp.support.microsoft.com/profile=BE66F0D8-9D78-47EF-840A-08E...
>  http://www.linkedin.com/in/neilpike

Neil,

I thought this was strange also.  Since the Primary Server was able to
see the new Backup Server we had not reset the services on the
Primary, except for the reboot to apply updates a couple of weeks
ago.  I don't recall having to reboot the Primary Server when we setup
the old Backup Server several years ago.  Looking back, I wonder if
rebooting the Primary Server would have fixed my initial problems with
getting the Backup Server to see the subdomain.

I have made several changes from the Primary Server and they seem to
be replicating out to the Backup Server now.  We'll be setting up
users on it to test their applications over the next couple of weeks
so we should find any problems then.

I really appricate the help you and Stephen gave me on this.

Thank you,
Donald A. Martin, Jr.

Donald,
 
 No problem - glad you're up and working.
 
 My theory on why a reboot caused it to work is as follows (a restart of the SNA 
Services on the Primary would also resolve if this was the case)
 
 - The reason the primary couldn't update the backup server was the lack of 
share/permissions on the backup server
 - At some point the primary server gave up trying to talk to the backup and in some 
way marked it "off-line"
 - You fixed the share permissions
 - Primary still wasn't going to work with the backup until the SNA Services on the 
primary were restarted.
 
 But, that's just a theory.  Could have been something else - potentially related to 
running HIS on a DC, which is something I've never done.

 Good luck with the user testing.
 
> I thought this was strange also.  Since the Primary Server was able to
> see the new Backup Server we had not reset the services on the
> Primary, except for the reboot to apply updates a couple of weeks
> ago.  I don't recall having to reboot the Primary Server when we setup
> the old Backup Server several years ago.  Looking back, I wonder if
> rebooting the Primary Server would have fixed my initial problems with
> getting the Backup Server to see the subdomain.
> 
> I have made several changes from the Primary Server and they seem to
> be replicating out to the Backup Server now.  We'll be setting up
> users on it to test their applications over the next couple of weeks
> so we should find any problems then.
> 
> I really appricate the help you and Stephen gave me on this.

 Neil Pike.  Protech Computing Ltd
 Microsoft SNA/HIS MVP
 https://mvp.support.microsoft.com/profile=BE66F0D8-9D78-47EF-840A-08E6D8522A2D
 http://www.linkedin.com/in/neilpike