1. Troubleshooting Web Link II
1.1. General Web-Link II Troubleshooting

 

  1. What version of Web-Link II? 
  2. What Windows OS?
  3. What type of HAI controller?
  4. What is wrong?
    1. Server Connection – Step 5
    2. Login Locally – Step 6
    3. Login Remotely – Step 7
    4. Video – Step
  5. Server Connection
    1. Was IIS installed prior to Web-Link II?
    2. Was “DCOMCONFIG” utility performed?
    3. Serial or Ethernet Port?  Verified settings with controller?
    4. Verified connectivity through PC Access?
    5. Positive “ping” from PC to Ethernet Port?
    6. Access Login on System tab correct
  6. Login Locally
    1. Is the HAI Communications Service running?
    2. Verify Anonymous Access is set properly in IIS?
    3. What results when you use http://localhost only in browser?
    4. What results with substituting computer name for localhost?

http://my_computer/web-link

 

            instead of

 

http://localhost/web-link

    1. Has Script Blocking been disabled in anti-virus software?
    2. Is firewall software installed?  If so, has it been configured properly?

 

  1. Login Remotely
    1. Does ISP (internet service provider) block Port 80?
    2. Dynamic or Static IP Address?  If Dynamic, has DNS service been setup?
    3. Verify proper internet IP Address?
    4. Verify proper port forwarding through router?
    5. Was IIS installed and configured prior to Web-Link II installation?
    6. Can you “ping” the IP Address from a DOS prompt?
    7. Has any firewall software been configured to allow remote access
  2. Video
    1. Verify proper Hauppauge product (model 190 or USB) or web cam?
    2. For Hauppauge product, has WDM driver been properly updated?
    3. Verify proper settings in Video Link tab of HAI Communications Service properties.
    4. Does video play on Web-Link II computer?
    5. Verify version of Windows Media Encoder?
    6. Does version of Web-Link II support version of Windows Media Player?
    7. Will video display in WME properly?
    8. Has Port 8080 been properly forwarded in router utilities?
    9. Will video display in MPLAYER2 or Windows Media Player separately from Web-Link?
1.2. Common Errors Encountered When Using Web-Link II
  1. Error #-2146959355: 006~ASP 0177~Server.CreateObject Failed~80080005

 

This error will be received when either the HAI Communications Service has not completely loaded, or, when the HAI Communications Service is not running.  Testing with version 4082 has shown that it takes approximately 20-30 seconds for the completion of loading “after” you see HAI Communications Service when passing the mouse over the icon.  You can reduce the overall loading time by “un-checking” the boxes for “Retrieve Setup” and “Retrieve Names” on the advanced tab of the HAI Communications Service properties.

 

  1. Server object error 'ASP 0177:800401f3'

Server.CreateObject Failed

The call to Server.CreateObject failed. The requested object instance cannot

be created.

 

This error is rarely seen, and can simply be resolved by re-installing the software.

 

  1. HTTP Error 403

403.9 Access Forbidden: Too many users are connected

 

This error indicates that too many people are currently connected to the server computer.  Although that is rarely the case, users not properly logging out of the software can precipitate this issue.  Simply rebooting the server computer should resolve this issue.

 

  1. Error#-2147024891: Access is denied

 

This is a permissions error and will be received in most instances where the software can not successfully negotiate permissions.  Some of the most common are:

 

    1. When attempting to add/edit/change channelsright click on the channels.xml file in the Web-Link web directory (c:\inetpub\wwwroot\web-link) and select "Properties".  Click the "Security" tab and select "Everyone".  Under "Permissions", check the "Write" check box to allow write permission for this file, then click "OK".
    2. Service Pack 2

Start/Run/DCOMCNFG

 

Expand "Component Services"

Expand "Computers"

 

Right-Click on "My Computer" and choose Properties

Choose the "Default Properties" tab

Check the "Enable DCOM" option

Choose the "Default COM Security" tab

Choose the "Edit" button for Access Permissions

Add the IUSR_xxxxx account and give it "Allow" access permissions

Choose the "Edit" button for Launch Permissions

Add the IUSR_xxxxx account and give it "Allow" access permissions

Add the IWAM_xxxxx account and give it "Allow" access permissions

Close the Properties page

 

Expand "My Computer"

Expand "DCOM Config"

Right-Click on "Web-Link Server" and choose "Properties"

 

On the "General" tab verify that "Default" is selected.

On the "Security" tab choose default for Launch Permissions

On the "Security" tab choose default for the Access permissions

On the "Security" tab choose Customize for the configuration permissions

Choose "Edit" to configure permissions

Choose "Everyone" (add it if necessary) and give it "Full Control".  Choose OK

Choose the "Identity" tab

Select "The Interactive User".  Choose OK.

 

REBOOT THE COMPUTER

 

    1. Web Sharing – If web sharing is not enabled, with a Web-Link alias, this error can be received.  Using Windows Explorer, navigate to C:\Inetpub\wwwroot\Web-Link, right click on Web-Link and select Properties from the drop down menu, and check the Web Sharing tab.

 

  1. Error #40: An attempt to acquire a network resource failed.  The startup of Video-Link broadcasting has been aborted.

 

This error is typically related to the port being used to broadcast video.  By default, Web-Link sets Port 8080 for video broadcast.  If other system devices are using this port, you will receive this error.  Use the Media Encoder to find a free port and make the appropriate change on the Video tab of the HAI Communications Service.

 

  1. Active Server Pages, ASP 0134 (0x80004005)

The object has an invalid ProgID of 'MSWC.MyInfo'.

//global.asa, line 1

 

This error is rarely seen.  You will only encounter this error when Web

Link is installed on a computer where Windows XP Pro has been installed

“over” Windows 2000, that has the IIS component installed.  When IIS is

installed on Windows 2000, a “global.asa” file is installed under

C:\Inetpub\wwwroot.  Simply rename this file, changing the “.asa” to “.as2”

will resolve the issue.

 

  1. Error # -1072889827: Failed to open a file

 

The only time this error will be encountered is when Web-Link version 2084 is installed on an XP Pro computer.  You can resolve this by enabling “Web Sharing” for the Web-Link folder properties under C:\Inetpub\wwwroot\Web-Link.

  1. Error # -2147467231

 

You will receive this error anytime the software can not successfully negotiate a command.  This typically caused by making changes within the controller and not updating the HAI Communications Service.  This problem can be quickly resolved by logging out of Web-Link, opening the HAI Communications Service properties, selecting the Advanced tab, and clicking on either/or the “Retrieve Setup” and/or “Retrieve Names” buttons.

 

  1. Error # - 2147467259

 

This error is generated after attempting to operate a command in Web-Link (turning on a light), and is directly related to a loss of communication between the controller and Web-Link.  Although the HAI Communications Service may appear to be running, valid communication has stopped.  Stopping and re-starting the server will resolve this error.  NOTE:  If this is happening on an Omni/Omni Pro controller, check the firmware.  Anything lower than version 1.8 should be replaced.

 

  1. Error #2 – Unable to obtain valid format details from server

 

You can receive this error under 3 circumstances:

    1. Attempting to use Web-Link version 0909 with an Omni II series controller
    2. Non-alphanumeric symbols used in naming control devices
    3. Using anti-virus software where the “Script Blocking” feature has not been disabled.

 

  1. Error #3

 

Rarely seen anymore, this error is directly related to running an older version of Web-Link (prior to 3052) on a computer using Media Player 9.  Simply updating the Web-Link to the current version will resolve this.

 

  1. << OLE Object: Picture (Metafile) >> Error #16410: 006~ASP 0177~Server.CreateObject Failed~The server process could not be started because the configured identity is incorrect.  Check the username and password.

 << OLE Object: Picture (Metafile) >>

Please specify the correct user name and user code.

This error is usually related to the use of Terminal Services, but has been associated with Service Pack 2 also.  If the application of #4 above does not provide resolution, then Terminal Services, or other similar software, is the culprit.  Simply disabling Terminal Services will resolve this issue.  If Terminal Services is a necessity, have the customer set up Web-Link as a service.

  1. Error # 2146828283

This error is directly related to incompatible WDM drivers for the Hauppauge video tuner.  Updating the drivers will resolve.

  1. ERROR # 2146828218

This error may be encountered when attempting to delete videos.  It is caused by insufficient permissions with regard to the Video folder in the Web-Link directory under C:\Inetpu\wwwroot\Web-Link\Video.  Applying the same fix as Step 4a above will resolve this issue.

  1. Error # - 1072882841 No Profile Set in Source Group

This error is received when attempting to access the video component within Web-Link , and is related to a missing or incompatible setting within the Video properties tab of the HAI Communications Service.  Check that the video driver is supported (Hauppauge), that a valid audio driver is selected (required), and that the configuration is a known working codec (Video for web server – 56 Kbps or Video for email and dual channel isdn – 128 Kbps).

  1. Error # - 2147467238: 006~ASP 0177~Server.CreateObject Failed

This error has been reported when accessing the Web Client in Windows 2003 Server.  The cause was due to a setting within the customer’s firewall software.

 

 

1.3. Anonymous Access/Windows Authentication
Discussion:
 
When attempting to access the Web-Link client, a Windows login screen appears similar to below:
 
 
Cause:
 
A Windows login screen will appear anytime proper authentication has not been allowed for Web-Link.  This can be related to custom configurations of the IIS (Internet Information Services), as well as some internet security features.
 
Resolution:
 
  1. Open the Control Panel on the computer hosting the Web-Link II server.
  2. Open the Administrative Tools icon.
  3. Open the Internet Information Services (IIS) icon.
  4. Expand the directories on the left hand side to find the Default Web Site section; right-click and select Properties.
  5. Click the Directory Security tab and click Edit in the Anonymous access and authentication control section.
  6. Check the Anonymous access, Allow IIS to control password, and Integrated Windows authentication boxes; apply and save the changes.
  7. Hit the plus beside Default Web Site to find the Web-Link folder; right-click and select Properties.
  8. Repeat steps 5 and 6 for this folder.
  9. Close all windows.
1.4. Web Link Client Not Accessible After Service Pack 2 Install

PROBLEM:

When you have Web-Link II installed on a computer that is running Microsoft Internet Information Services (IIS) version 5.1, and you apply Microsoft Windows XP Professional Service Pack 2 to the computer, you may receive the following error message when you access the site:

Web-Link II Server Initialization failed!

The server cannot be accessed at this time.

Error #-2147024891: 006~ASP 0178~Server.CreateObject Access Error~The call to Server.CreateObject failed while checking permissions. Access is denied to this object.

CAUSE:

Appropriate permissions to access and launch the Out-Of-Process (OOP) COM object has not been set due to increased security after installing Service Pack 2 for Windows XP Professional. 

 

SOLUTION:

 

1.       Close the web browser that is displaying the error message.

2.       Launch “Component Services” by clicking Start, selecting Run, and typing "Dcomcnfg" in the Run dialog box.

a)       Double-click on “Component Services”.

b)       Double-click “Computers”.

c)       Right-click on "My Computer" and select “Properties”.

d)       Click the “COM Security” tab.

e)       Under “Launch and Activation Permissions” click the “Edit Default” button.

f)         Add the “Everyone” account by clicking on the "ADD" button, then clicking on the "Advanced" button. This will open the "Select Users or Groups" dialog box. Now, click on the "Find Now" button. After clicking on the "Find Now" button, a list of users and groups will appear below. Highlight the entry named “Everyone” and click on OK to add “Everyone” Launch Permissions.

g)       Under “Permissions for Everyone”, select the “Allow” check box for each of the entries.

h)       Click “OK” to close the “Launch Permissions” dialog.

i)         Click “OK” to apply and close the “My Computer Properties” dialog.

3.       Launch the “DCOM Config” utility by double-clicking on “My Computer”, and then double-clicking on “DCOM Config” under “Component Services”. 

Note: You may receive several DCOM Configuration Warning messages.  Select “Yes” for each.

a)       Right-click on “Web-Link Server” and select “Properties”.

b)       Click the “Security” tab.

c)       Select the “Customize” button under “Launch Permissions”.

d)       Click the “Edit” button.

e)       Add the “Everyone” account by clicking on the "ADD" button, then clicking on the "Advanced" button. This will open the "Select Users or Groups" dialog box. Now, click on the "Find Now" button. After clicking on the "Find Now" button, a list of users and groups will appear below. Highlight the entry named “Everyone” and click on OK to add “Everyone” Launch Permissions.

f)         Under “Permissions for Everyone”, select the “Allow” check box for each of the entries.

g)       Click “OK” to close the “Launch Permissions” dialog.

h)       Click “OK” to apply and close the “Web-Link Server Properties” dialog.

 Related Articles:

After installing SP2, I can no longer access Web-Link II

1.5. After installing SP2, I can no longer access Web-Link II

 

PROBLEM:

When you have Web-Link II installed on a computer that is running Microsoft Internet Information Services (IIS) version 5.1, and you apply Microsoft Windows XP Professional Service Pack 2 to the computer, you may receive the following error message when you access the site:

The page cannot be displayed. Can't find server or DNS error.

CAUSE:

This problem occurs because installing Service Pack 2 for Windows XP Professional enables the Internet Connection Firewall (ICF). 
 
SOLUTION:
 
To resolve this problem, configure ICF to enable HTTP traffic:
  1. Click Start, click Control Panel, and then double-click Windows Firewall.
  2. Click the Exceptions tab, and then click Add Port.
  3. In the Name box, type HTTP. In the Port box, type 80.

Note 1: This procedure enables HTTP traffic. If you also require HTTPS traffic for Secure Sockets Layer (SSL) sites, repeat these steps, but type HTTPS in the Name box, and then type 443 in the Port box.
 
Note 2:  For more information about this procedure, you can refer to the following link:
 
 
Note 3: The installation of SP2 may also affect the way your computer handles "cookies".  You can open Internet Explorer, click on Tools, click on Internet Options, click on the Privacy tab and changing the security to allow Web-Link II to function properly (typically a Medium setting).
 
Related Articles:
 
1.6. Web-Link Server Stops Communicating

 

PROBLEM:

The Web-Link II Server stops communicating with the Omni/Omni Pro controller intermittently.

CAUSE:

In order for Web-Link II to function properly, the Omni controller must firmware version 1.8 or later.

SOLUTION:

Upgrade firmware to version 1.8 or higher.

1.7. Finding the Security Tab When Applying Permissions

Problem:

When the customer attempts to add/make changes by right-clicking on a folder and selecting Properties, there is no "Security Tab" available.

Solution:

When "Simple File Sharing" is enabled, the Security Tab will not appear in the properties dialogue window.  To disable "Simple File Sharing", do the following:

1. In Windows Explorer, click on "Tools" and select Folder Option.

2. Click on the "View" tab.

3. In the "Advanced Settings" box scroll down til you reach "Use Simple File Sharing" and uncheck the box.

4. Click on Apply, and then OK.

You should now be able to see the Security Tab when you access a folder's properties.

1.8. Why can't I access my Web-Link II from a remote location?

 

Question:

Why can't I access my Web-Link II from a remote computer?

Answer:

To access a web server installed on a computer behind a router, port forwarding must be configured. Port forwarding sets up public services on your network. When users from the Internet make certain requests of your network, the router will forward those requests to the appropriate computer. The router's DHCP function is typically disabled when using port forwarding.

Using the router's utility, map Port 80 (HTTP) and Port 8080 (Video broadcasting) to the IP Address of the computer (Web-Link Server computer) that you want the Internet users (Web-Link Clients) to be able to access.

1.9. Workaround for Blocked Port 80
Because of excessive internet usage, some ISP’s (Internet Service Providers) have begun blocking Port 80. This makes the use of Web-Link unusable from a remote location. Customers may formally request that this blockage be removed. The ISP’s may honor that request, or charge an additional cost for this change, or refuse such requests entirely. For Windows 98 users, there is no work-a-round, short of upgrading their operating system.

If using Windows 2000, NT, or XP Pro, do the following:
 
  1. Click on Start, go to Settings, and open Control Panel (on XP, there is a direct link to Control Panel in the main menu).
  2. Open Administrative Tools.
  3. Open Internet Services Manager (Internet Information Services in XP).
  4. In the left hand pane, click on the "+" next to the Computer Name.
  5. Right click on "Default Web Site" and select "Properties" from the drop down menu.
  6. On the "Web" tab (it should default to that), you will see where Port 80 is selected for TCP/IP.
  7. You will need to change this to a free port. I typically suggest something like 1012, 1013.
  8. Click on OK and exit.
  9. From your desktop, right click on the icon for "Web-Link Client" and select "Properties" from the drop down menu.
  10. In the URL window add the Port number you are using to the command. An example would be:

          http://localhost/web-link/default.asp

          would be changed to

          http://localhost:1012/web-link/default.asp

          Also, you would have to use that "Port" reference when accessing Web-Link from a remote computer. Another example is:

          http://255.10.12.113/web-link

          would be changed to

 
If using Vista, perform the following steps:
  1. Open Control Panel.
  2. Open Administrative Services.
  3. Open Internet Informaiton Services.
  4. In the left panel, expand the server tree.
  5. Expand Sites tree.
  6. Right-Click on Default Web Site and select Edit Bindings from the drop-down menu.
  7. Highlight HTTP 80 and select Edit to change the Port.
 
 
1.10. Configuring URL for Non-Standard Port in Version 2.1.7249
Question:

How do I change the Client Access shortcut on the server computer to account for a different HTTP port?


Answer:

The default icon that is created when version 2.1.7249 is installed does not have a URL address any longer.  To create a shortcut, using Port 1012 as an example:

  1. Right click on any free space on your desktop and select New>Shortcut from the context menu.
  2. In the Location dialogue box, type in http://localhost:1012/Web-Link/.
  3. Click on Next, and then Finish.

The above will establish an Internet shortcut to your Web-Link login.  If you want the shortcut icon to display the familiar Web-Link logo, simply:

  1. Right click on the shortcut you created and select Properties from the context menu.
  2. Click on the Web Document tab, if necessary.
  3. Click on the Change Icon button.
  4. Click on the Browse button and navigate to your Web-Link folder (the default is C:\Program Files\HAI\Web-Link.
  5. Click on Haicommsrv.ico and select OK.
1.11. Can Not Connect to Web Server

 

Discussion:

A customer will report that when they try to connect to the “Web-Link Web Client”, they receive an error – CAN NOT CONNECT TO SERVER.In troubleshooting, you find that they have installed the software properly and that the “HAI Communications Service” is running properly.

Resolution:

  1. Open a web browser.
  2. Click on the Tools button and select Internet Options.
  3. Select the Connections tab.
  4. Click on the LAN Settings button.
  5. Confirm that the Use Proxy Server box is checked.  If it is, check the box for “Bypass proxy server for local addresses”.
  6. Click on Advanced.
  7. In the “Exceptions” field, add localhost.
  8. Click on OK, OK, Apply, and OK.

You should now be able to access the local client.

1.12. Cannot Access Web Link II From Behind Firewall

Cannot Access Web-Link

From Behind a Firewall

This procedure should be used to access Web-Link II from a remote location that is located behind a firewall:

1. From your desktop, click on Start>>Settings>>Control Panel (Win2000), Start>>Control Panel (XP Pro).

2. Open Administrative Tools.

3. Open Internet Information Services.

4. From the left side Preview, click on the computer name (you will see a "+" appear next to the name.

5. Expand out the menu (click on the "+")

6. Expand out the Default Web Site.

7. Right click on the "Web-Link" folder and select Properties.

8. Click on the "Directory Security" tab.

9. Click on the "Edit" box of the Anonymous Access and Authentication Control frame.

10. Now, enable (check) the Anonymous Access box.

11. Click on OK to exit, OK again to exit properties, and close the IIS.

1.13. ASP Pages Will not Display

Occasionally, a customer may call in and report that they receive a "Page Cannot Be Displayed" message when trying to login to Web-Link II. A quick test to see if the error is related to ".asp" pages, is to have the customer access both of the hyperlinks below and report their results:

http://localhost/homeview/help.htm

http://localhost/homeview/help.asp

If the "help.htm" displays properly, but the "help.asp" returns the "Page Cannot Be Displayed" message, have them do the following:

  1. Close the HAI Communications Service (right click on icon and select Close).
  2. Go to Control Panel (Windows 2000 – Start>>Settings>>Control Panel; Windows XP Pro – Start>>Control Panel).
  3. Open Administrative Tools.
  4. Open Computer Management.
  5. In the left frame, expand out (click on "+" sign) Services & Applications.
  6. Expand out Internet Information Services.
  7. Right click on Default Web Site and select Properties from the drop down menu.
  8. Select the Home Directory tab (may also be Virtual Directory or Directory).
  9. Check what is showing for "Starting Point". It should be "Default Web Site" and be grayed out. If it shows nothing or none, click on Add and select Default Web Site (it should be done by default).
  10. Click on Configuration and confirm the ".asp" appears in the "App Mapping" tab and click on OK.
  11. Select the Directory Security tab.
  12. Click on Edit under "Anonymous Access and Authentication Control".
  13. Check "Anonymous Access" and "Integrated Windows Authentication". Both should be checked.
  14. Click on OK and close everything until you get back to your top level display.
  15. Start the HAI Communications Service.

Now, the customer should be able to login to Web-Link II.

1.14. Windows 2003 Active Server Page
Symptoms

When you request dynamic content such as an Active Server Pages (ASP) page, an ASP.NET page, an Internet Services API (ISAPI) application, or a Common Gateway Interface (CGI) application on a Microsoft Windows Server 2003 server that is running Internet Information Services (IIS) 6.0, you may receive the following error message:

HTTP Error 404 - File Not Found

-or-

HTTP Error 404- File or Directory not found

 

Cause

By default, when IIS is installed on any version of the Windows Server 2003 family, IIS only serves static content (HTML).
 

Resolution

To permit IIS to serve dynamic content, the administrator must unlock this content in the Web service extensions node in IIS Manager. To do this, the administrator must either enable a pre-existing Web service extension or add a new Web service extension.  NOTE: You may not need to complete all of the steps below.  After applying the steps in each of the bold categories below, check performance.

Enable a Pre-existing Web Service Extension in IIS 6.0

To permit IIS to serve content that requires a specific ISAPI or CGI extension that is already listed in the Web service extensions list, follow these steps:
1. Open IIS Manager, expand the master server node (that is, the Servername node), and then select the Web service extensions node.
2. In the right pane of IIS Manager, right-click the extension that you want to enable. In this example, this is Active Server Pages.
3. Click to select the Allow check box.

Add a New Web Service Extension to IIS 6.0

To permit IIS to serve content that requires a specific ISAPI or CGI extension that is not already listed in the Web service extensions list, follow these steps:

1. Open IIS Manager, expand the master server node, and then select the Web service extensions node.
2. In the right pane of the IIS Manager, click Add a new Web service extension under Tasks.
3. In the Extension name box, type a friendly name for the extension that you want to add (for example, FrontPage Server Extensions).
4. In the Required files box, click Add, and then select the path and the name of the file that will handle requests for the specific extension. After you select the path and the file name, click OK.
5. If the extension must be enabled immediately, click to select the Set extension status to allowed check box.
6. Click OK to save your changes.

Additional steps for Common Gateway Interface (CGI) applications

For CGI applications, you must also follow these steps:

1. Right-click Default Web Site or the Web site that you want, and then click Properties.
2. On the Home Directory tab, click Scripts and Executables in the Execute Permissions list.
3. Make sure that the Everyone group has the following NTFS file system permissions on the C:\InetPub\wwwroot folder or on the folder that has the Web content for the site that you want:
Read & Execute
List Folder Contents
Read
4. Right-click Default Web Site or the Web site that you want, and then click Properties.
5. On the Home Directory tab, make sure that DefaultAppPool is selecting in the Application pool box. If another application pool is selected, follow these steps in IIS Manager:
a. Expand Application Pools, right-click the application pool that you want, and then click Properties.
b. On the Identity tab, make sure that one of the following conditions is true:
The Network Service account is selected.
The account that is selected is a member of the IIS_WPG group.
 

References

For more information about Web service extensions, search for "Enabling and Disabling Dynamic Content" in the IIS 6.0 Help documentation.

For more information, click the following article number to view the article in the Microsoft Knowledge Base:
332124 (http://support.microsoft.com/kb/332124/) ASP.NET is not automatically installed on Windows Server 2003
1.15. Page Can Not Be Displayed

PROBLEM:

Customer installs Web-Link II in an XP Pro environment.  When attempting to login to Web-Link II for the first time, a default Windows "Page Can Not Be Displayed" error is displayed.  Upon further inspection, the following information is found associated with the error:

Active Server Pages, ASP 0134 (0x80004005)
The object has an invalid ProgID of 'MSWC.MyInfo'.
//global.asa, line 1

CAUSE:

The "global.asa" file is installed as part of the Microsoft IIS components in a Windows 2000 operating system.  When attempting to login to Web-Link in XP Pro, the DNS can not negotiate the "global.asa", thereby causing the error.  The most likely causes for this error are:

1. The Windows XP Pro was installed as a second operating system on a computer with Windows 2000 software.

2. The Windows XP Pro was installed over an existing Windows 2000 environment.

3. When installing the Microsoft IIS components, the installations detects a Windows 2000 environment.

 

SOLUTION:

1. Open Windows Explorer.

2. Navigate to C:\Inetpub\wwwroot.

3. Right click on the global.asa file and rename the file (i.e. global.as2).

4. Close Windows Explorer.

5. Login to Web-Link

NOTE:  If you are unable to find the global.asa file, click on Tools, select Folder Options, click on the View tab, and un-check the box for "Hide extensions for known file types".

1.16. Converting File System To NTFS

Converting File System To NTFS

 

 

To convert your file system to NTFS, do the following:

  1. Click on Start.
  2. Click on Run.
  3. Type in cmd and hit OK.
  4. From the dos prompt that opens up, type in convert c:/fs:ntfs and hit enter.
  5. Follow the instructions and reboot when necessary.
1.17. Error # -1072889827: Failed to open a file

Error # -1072889827: Failed to open a file

The first issue that must be addressed is the fact that, for some unknown reason, after doing a clean install of XP Pro, Web Link II & the 2.1.2084.0 update, the Web-Link directory located inside the C:\Inetpub\wwwroot path is not automatically setup as a "shared web directory." More specifically, an "alias" named "Web-Link" at the aforementioned path is normally created when you do an installation of Web Link II under any operating system other than a "clean" installation of Windows XP Pro. In practice, however, if you do an installation of Web Link II and the 2.1.2084.0 update to a system containing a clean installation of Windows XP Pro, the necessary alias for the sharing of the Web-Link directory with Internet Information Services is not automatically created. You must manually create the alias by right-clicking in the Web-Link folder inside the C:\Inetpub\wwwroot path, choose "sharing and security" and then click on the "Web Sharing" tab. Next, you must click on "Add," confirm that the "Alias" field reads "Web-Link" and then click on "OK." By adding this alias, this eliminates the "Error #-1072889827: Failed to open a file" error message.

The second issue that must be addressed is that of the appropriate user needing full permissions to access, at a minimum, the "Video" sub-directory inside the Web-Link directory. Without the necessary permissions, an error message reading "Error #-2146828218: Permission denied." is generated whenever you attempt to do operations such as delete a no-longer-needed video recording. Similarly, simply attempting to clear the server log delivers an equally undesirable error message, "Error #-2147024891: Access is denied." The solution is to assign the necessary access permissions to the entire Web-Link directory by right-clicking on the Web-Link folder inside the C:\Inetpub\wwwroot path, choosing "Sharing and Security," then clicking on the Security tab. Next, in the "Permissions for Users" section, select the user account which begins with "Users" and place a check mark in the "Full Control" box in the "Allow" column. Finally, click OK. This effectively eliminates all error messages which are the result of any of the files or directories in the Web-Link directory not having sufficient permission to delete or modify files.

Note that the necessary file permissions for the Web-Link directory in the previous paragraph are entirely unnecessary if the system that Web Link II is being installed on is not using the NTFS file system. If the FAT (or FAT32) system is being used, there are no default security restrictions in place which need to be modified (unless you do an upgrade to XP).

To complicate matters further, the above instructions wouldn't make any sense to anyone that did a clean installation of XP Pro, but told XP Pro that they are operating in a Workgroup environment, as opposed to an environment with a Domain. The reason for this is that, by default, when you tell XP Pro that you are operating in a Workgroup environment, XP Pro automatically configures itself with the "Simple File Sharing" feature enabled. Unfortunately, the effect of this is that, when you go to right-click on the Web-Link folder in Explorer to change the above-referenced settings, the tabs on the "Sharing and Security" menu item are quite different. In fact, with Simple File Sharing enabled, there is no option to activate the necessary security level to perform the above operations. As such, if a clean installation of XP Pro has been performed to a Workgroup environment, it is necessary to go into the Control Panel and disable Simple File Sharing. This is done by clicking on Appearance and Themes (if the "category view" of the Control Panel is enabled) in the Control Panel and clicking on the "Folder Options" icon in the Control Panel. Next, after opening the Folder Options, it is necessary to click on the "View" tab. Finally, remove the check mark from the "Use simple file sharing (recommended)" item at the extreme bottom of the list. This will enable the user interface which will allow the above operations to be completed without any unnecessary confusion.

Similarly, when you upgrade to XP, Simple File Sharing is automatically enabled. As such, if the upgrade has been performed using the NTFS file system, it is necessary to go into the Control Panel and disable Simple File Sharing (as stated above).

This is where it gets tricky. If the upgrade has been performed using the FAT file system, you may or may not have to alter permissions. I'm not sure why sufficient permissions are granted (by default) on some systems but not others. But if sufficient permissions are not granted (as evidenced by one of the above error messages), you must convert the file system from FAT (or FAT32) to NTFS. Afterwards, it is necessary to go into the Control Panel and disable Simple File Sharing (as stated above).

1.18. Error # -2147467231:

This error is directly associated with a command that the Web-Link II software is incapable of executing.The most common cause for this is performing some sort of programming to the controller that Web-Link II does not recognize and/or update.When this error occurs, do the following:

1.  Log out of Web-Link II.

2.  Open the HAI Communications Service (right click on house icon and select Properties).

3.  Click on the Advanced tab.

4.  Click on the Retrieve Setup button.

5.  Click on the Retrieve Names button.

6.  Login to Web-Link.

Web-Link should function properly now. 

1.19. Error # - 2147467259 Receive error when initiating a control command within Web-Link

 

PROBLEM:

When attempting to operate a feature within Web-Link (i.e. turn on light, adjust tstat setting, etc.), an Error # - 2147467259 appears.

CAUSE:

This problem can be caused by a loss of communication between the Omni controller and the PC.  The HAI Communications Service is running, but it has lost valid communication with the controller.

SOLUTION:

1. Log out of Web-Link (if applicable).

2. Close the HAI Server (right click on house icon and select Close).

3. Restart the HAI Server (Start>>Programs>>HAI>>Web-Link>>Web-Link Server).

4. Login to Web-Link.  It should function properly.

1.20. Error #2 - Unable to obtain valid format details from server

Web-Link II

Error #2 – Unable to Obtain Valid Format Details from Server

This error can be related to three (3) items:

 

  1. Older software (version 0909) communicating with an Omni II series controller.

 

  1. Non-alphanumeric symbols used in the naming of control units.

 

  1. Anti-virus software where the “Script Blocking” feature has not been disabled.
1.21. Error #3 When Accessing Cameras

PROBLEM:

When clicking on the camera icon in Web-Link II, Error - #3 is received.

CAUSE:

This error is generated when using a version of Web-Link II prior 3052, on a computer running Media Player 9.

SOLUTION:

1.  Update Web-Link II software (recommended).

2. Uninstall Media Player 9.

1.22. Event Log Not Displaying Current Events

 

PROBLEM:

 

            When viewing the Event Log in Web-Link II, the most current events are not displaying.

 

 

CAUSE:

 

            This scenario can take place if the database that stores system information becomes corrupted.  Corruption of the database can be caused by momentary loss of communication between the software and controller.

 

 

SOLUTION:

 

1.      Log out of Web-Link (if applicable).

2.      Close the HAI Communications Service (right click on house icon in systray and select Close).

3.      Open Windows Explorer.

4.      Navigate to C:\Program Files\HAI\Web-Link.

5.      Highlight and delete the “haiinfo.dat” file.

6.      Close Windows Explorer.

7.      Start the HAI Communications Service (Start>>Programs>>Web-Link>>Web-Link Server).

8.      Login to Web-Link.  The Event Log should now be current.

1.23. Server.CreateObject Failed ERROR

 

Discussion: 

 

Web-Link II Error:

<< OLE Object: Picture (Metafile) >> Error #16410: 006~ASP 0177~Server.CreateObject

Failed~The server process could not be started because the configured identity is incorrect.

Check the username and password.

 << OLE Object: Picture (Metafile) >>

Please specify the correct user name and user code.

 

Solution:

This error can occur when logging in via Terminal Services (Remote Desktop).

  -- Restart the computer

  -- Login locally to the computer and verify HAICommSrv is running

  -- Try accessing web-link

If you don't do this then HAICommSrv will initially start in the Terminal Services process which will not be available from a permissions standpoint to the web service.

If logging in via Terminal Services (Remote Desktop) is necessary, we recommend that you follow the procedures for setting up the HAI Communications Service as a “Service” as described in the Web-Link “Help.htm” file to avoid this issue.

 

 

1.24. Getting Web Link II to Work with Win 2K

The workaround for this problem is to set the DCOM permissions to give everyone access to them. To change the DCOM settings do the following:

·         From the Start menu, choose Run and enter "DCOMCNFG"

·         Choose the ‘Default Security’ tab

·         In the "Default Access Permissions" section, choose the "Edit Default" button

·         Choose the "Add" to display the "Add Users and Groups" dialog

·         In the "List names in" list box choose the name of the local computer

·         In the "Names" list box select "Everyone"

·         Choose OK several times to exit out of the DCOMCNFG utility

·         Reboot the computer

1.25. Running HAICommSrv As A Service

When Web-Link II is installed on a computer, it is not set up as a “service”.  This can be a bothersome issue to customers that may not want to be logged onto their computer all the time.  Changing the HAI Communications Server to a “service” will allow the customer the freedom of logging off from their computer without disrupting the HAI Communications Service.  Another potential benefit of running as a “service” is that in the event of a reboot, the HAI Communications Service would restart without having to ever login.

 

Here are some instructions and guidelines for running HAICommSrv as a Service.

 

When running as a “service” the HAI Communications Service icon will not appear in the task tray. Therefore, you cannot be running as a service if you have to make changes to any of the settings. See “Switching from Service” below for information on getting the UI visible again.

 

Switching to Service:

 

  1. Close HAICommSrv (if running, right click on house icon and select Close).
  2. Click on Start, select Run, type in CMD, and click on OK.
  3. From a C: prompt, type in CD PROGRAM FILES\HAI\WEB-LINK and press Enter.
  4. Type in HAICOMMSRV /UNREGISTER to unregister the file.
  5. Type in HAICOMMSRV /SERVICE to register the file as a service.
  6. Type in EXIT and press Enter.
  7. Click on Start, then right click on My Computer, and select Manage.
  8. Click the “+” next to Services and Applications.
  9. Right click on “Web-Link Service” and choose Start.

 

Switching from Service:

 

  1. Open the Task Manager, highlight HAICOMMSRV, and click on End Process.
  2. Click on Start, select Run, type in CMD, and click on OK.
  3. From a C: prompt, type in CD PROGRAM FILES\HAI\WEB-LINK and press Enter.
  4. Type in HAICOMMSRV /UNREGSERVER to unregister the file.
  5. Restart the computer.
  6. Click on Start, select Run, type in CMD, and click on OK.
  7. From a C: prompt, type in CD PROGRAM FILES\HAI\WEB-LINK and press Enter.
  8. Type in HAICOMMSRV /REGSERVER and press Enter.

 

1.26. Uninstalling/Reinstalling Web-Link II (for 32-bit Windows OS ONLY)

 ****THIS PROCEDURE SHOULD ONLY BE PERFORMED ON 32-BIT WINDOWS OPERATING SYSTEMS****

    1. Using Task Manager, stop/close all processes related to Web-Link.
    2. Uninstall Web-Link II using the Add/Remove feature in the Windows Control Panel.
    3. Open Windows Explorer, navigate to C:\Program Files\HAI\Web-Link and delete the Web-Link folder.
    4. Open the Registry Editor (Start>>Run, type in REGEDIT and click on OK).
    5. Click the "+" next to HKEY_LOCAL_MACHINE.
    6. Click the "+" next to Software.
    7. Highlight and delete the "Home Automation, Inc" key. NOTE: DO NOT delete the HAI key.
    8. Close the Registry Editor.
    9. Reboot the Computer.
    10. Install Web-Link II.
1.27. Upgrading Web-Link Causes Display Problem

Problem:

After updating Web-Link II to version 4082, everything works fine except that the login

HTML page display is different, as well as the display of the other Web-Link pages - they appear to be "plain-jane" html.

 

Cause:

There is probably a permissions setting that prevented the setup program from updating the "browscap.ini" file, which is

used to detect the current browser.

 

Solution:

Since the "browsecap.ini" can’t determine the browser, generic “html” pages are displayed, rather than the

“ie” pages.  To resolve this problem, copy the attached “browscap.ini” file to the "C:\Windows\system32\inetsrv" folder.

1.28. Error #499: 006~ASP 0177~Server.CreateObject Failed~Invalid class string
Symptoms

When attempting to login after installing version 2.1.6025.0, the following error is encountered:

Error #499: 006~ASP 0177~Server.CreateObject Failed~Invalid class string

Another error that may be reported is:

Error #-2147221005: 006~ASP 0177~Server.CreateObject Failed~Invalid class string

 

Cause

This error is caused when the ASP script requests the name of the HAI object and then the registry is searched for the name.  When it finds the name, it obtains the corresponding GUID and accesses the file.

"Invalid Class String" means that the HAI object "name" could not be found.  The two most common reasons for this are:

1. The name isn't there which means it wasn’t registered properly.

2. The process/user doesn't have rights to read from the registry (or that particular key/parent_key).  If you adjusted some security settings, this may actually be the problem.

 

 

Resolution

Open the Registry Editor and reset the default settings for the HKEY_CLASSES_ROOT
 

References

1.29. Error During Web-Link Installation
Symptoms

During installation, the following error occurs:

An error occurred during the move data process: -119

Component: Program DLLs

File Group: Program DLLs

File: C:\Program Files\HAI\Web-Link\EventMgr.DLL

 

Cause

This error almost always indicates that registration of the files failed and the #1 cause of that is a dependent file is not on the system.

 

 

Resolution

Now, for determining the dependent file that is missing, please do the following:

1.       Run setup again and when the error appears just leave it on the screen.  At this point all of the files will actually be on the system.

2.       Run the Dependency Walker application (see attached)

3.       Choose FILE|OPEN and navigate to “C:\Program Files\HAI\Web-Link”

4.       Open VIDLINKUI.DLL and look for Errors/Warnings about missing files or functions and send the results back.

5.       If everything with VIDLINKUI.DLL looks good then try inspecting the following files in this order:

a.       HAICommSrv.exe

b.       VidLink.dll

c.       Eventmgr.dll

d.       HAICommSrvUI.cpl

 


 

1.30. Norton Anti-Virus 2005

Situation:
After Installing Norton AntiVirus 2005,your Web-Link may be inaccessible from remote access. You may also see the following message:
"Internet worm protection detected a block of an intrusion attempt on your computer."

Solution:
This problem happens because the port used by Web-Link is blocked by the Internet Worm Protection feature of Norton AntiVirus. Follow the steps in the next section to remove all existing program entries and then re-add a program control rule in Internet Worm Protection to allow the port used by the Web-Link software to access the Internet.


Remove all existing Internet Worm Protection program control entries and then recreate a new rule for Web-Link
Follow the steps in each section in the order listed to remove all program rules and then let Internet Worm Protection create a new rule for the Web-Link software.

To remove all existing program rules

  1. Start Norton AntiVirus. If Norton AntiVirus is installed as part of Norton SystemWorks, then start that program.
  2. Click Options. Click Norton AntiVirus if you see a menu.
  3. On the left pane, select Internet Worm Protection.
  4. On the right pane, click Program Control.
  5. If there are programs listed, then click the first program in the list.
  6. Press CTRL+ A to highlight all items.
  7. Click Remove.
  8. Click OK and close Norton AntiVirus.


To create a new program rule for Web-Link software

  1. Start the Web-Link. This should generate a dialog box.
  2. On the dialog box, from the drop-down menu, click Permit.
  3. Click OK.

If this does not fix the problem, then try the workaround in the next section.


Allow communication on port 1012
Follow these steps to allow communication through a port used by the Web-Link software.

To allow communication on port 1012

  1. Start Norton AntiVirus. If Norton AntiVirus is installed as part of Norton SystemWorks, then start that program.
  2. Click Options. Click Norton AntiVirus if you see a menu.
  3. On the left pane, select Internet Worm Protection.
  4. On the right pane, click Trojan Rules.
  5. Scroll to and uncheck the entry Default Block Silencer Trojan horse.
  6. Click OK.
1.31. Blank Settings After Web-Link Update on Windows 2000
Problem Summary: After installing Web-Link version 6025, the Settings for Connection Type are blank and no information can be entered.
 

Cause:

 This ia a known flaw in version 6025 of the software, and only presents when installed on a computer running Windows 2000.
 

Resolution:

 1. Install the latest version of Web-Link (Version 6025).

2. Close Control Panel, if applicable.

3. Open Windows Explorer and navigate to C:\Program Files\HAI\Web-Link.

4. Highlight and rename HAICommSrvUI.CPL to HAICommSrvUI.old.

5. Unzip the attached file and place the HAICommSrvUI.CPL into the Web-Link folder.

6. Close Windows Explorer.

7. Open Control Panel.

8. Open HAI Configuration - everything should appear and function properly now.

 

 

1.32. Error when trying to access http://localhost/web-link.

I’m getting the following error when trying to access http://localhost/web-link:

 Error Type:
Server object, ASP 0177 (0x800401F3)
Invalid class string
/web-link/global_asp.js, line 26

  

Here are some possible solutions:

 (1) Look at the IIS permissions.  If it is currently set to anonymous, switch it to basic.  If it starts working, this indicates that the IUSR_machineaccount doesn’t have the proper access rights.  Nevertheless, this new setting will suffice.

 (2) There is a permissions problem (process/user doesn't have rights to read from the registry, to the directory that browscap.dll is in, or for loading the control).

 Other possible causes:

 The control is not registered correctly.  (Try re-registering browscap.dll using regsvr32…also make sure that browscap.ini is in the same folder as browscap.dll).

  • The "Logged On User" does not have adequate permissions to run the control. In many cases the anonymous login account (IUSR_<machine>) does not have appropriate permissions on certain Directories/Files or the specific component and its dependencies. While less frequent, if the registry permissions for certain keys are not set correctly, it causes the control to fail to initialize.

 

  • The "Everyone" group has been removed from having READ permissions on certain registry keys.

 

  • The control is not installed. Try uninstalling IIS and reinstalling it.

Additional information for theis canbe found in the Microsoft Knowledgebase: http://support.microsoft.com/default.aspx?scid=kb;en-us;251361

 

1.33. Removing Web-Link Completely and Re-installing From an Update

NOTE: The procedures below should only be performed on Windows XP Pro, or later, operating systems.

  1. Close/Stop the HAI Communications Service, if running.
  2. Open Control Panel.
  3. Open Add/Remove Programs.
  4. Highlight HAI Web-Link and click on Change/Remove.
  5. Close Add/Remove Programs and close Control Panel.
  6. Open Windows Explorer.
  7. Navigate to C:\Inetpub\wwwroot\Web-Link.
  8. Delete any/all files in the folder, and then delete the Web-Link folder itself.  NOTE:  Trying to delete the folder before the files will generally result in errors.
  9. Navigate to C:\Program Files\Web-Link.
  10. Delete any/all files in the folder, and then delete the folder itself.
  11. Close Windows Explorer.
  12. Click on Start, select Run, type in regedit, and click on OK.
  13. Click the “+” next to HKEY_LOCAL_MACHNIE.
  14. Click the “+” next to Software.
  15. Highlight and delete the Home Automation, Inc key.  NOTE: Do not delete the HAI key, if one exists – this is related to PC Access software.
  16. Close the Registry Editor.
  17. Reboot the computer.
  18. After reboot, open the zip file containing the Web-Link update.
  19. Extract all files to a folder on your computer.  TIP: Extracting the files to a folder (named Web-Link) on your desktop will provide easier access.
  20. After extraction, open the folder.
  21. Right-click on any free space in the folder, and select New>>Folder from the context menu.
  22. Name the folder Extras.  NOTE: The existence of this folder is required in order for a Web-Link Update to be installed when no previous version of Web-Link exists.
  23. Run the Setup.exe to install the update.  Once installed, test for performance.