If you have used Host Integration Server 2006 and earlier, you have likely seen HIS display certain error messages in popup message dialogs. For example, a popup message dialog like the following is displayed on a HIS Client when the SnaBase process is unable to connect to a sponsor server:
Host Integration Server – ERROR # 1003
SnaBase could not open a sponsor connection to server servername
When HIS 2009 is installed on either Windows Vista or Windows Server 2008, the HIS popup message dialogs will not be displayed. The reason the popup messages will not be displayed in due to the Session 0 Isolation feature that was introduced in Windows Vista. This feature was added to improve security. If you would like additional details about Session 0 Isolation and its potential impacts, the following are good starting points:
Impact of Session 0 Isolation on Services and Drivers in Windows Vista
Application Compatibility: Session 0 Isolation
Instead of the HIS popup message dialog, HIS 2009 logs an Event 1042 message that contains the information that the HIS popup error dialog would have displayed. The following is an Event 1042 message that is logged when the SnaBase process fails to connect to a sponsor server:
Event ID: 1042Source: SNA Base ServiceDescription: Application returned Error: SnaBase could not open a sponsor connection to server servername
The Event 1042 is a new event message that has been added to HIS 2009.
You will also see that the new Event 1042 message is logged when HIS 2009 is installed on earlier versions o f Windows (e.g. Windows XP) that allow the HIS popup message dialogs to be displayed. In these scenarios, you will get the HIS popup message dialog and the Event 1042 message.
You may also see an event similar to the following logged when HIS 2009 is unable to display the popup message dialog on Windows Vista and Windows Server 2008:
Event ID: 589Source: SNA Base ServiceDescription: Failed to display a pop-up, rc = 0
EXPLANATIONA CreateProcess call for the pop-up process failed. The return code is shown.
The Event 589 is logged in addition to the Event 1042 message.