|
Known SiteWatch Version 4 issues with Microsoft Vista, Windows Server 2008 and
Windows 7
e-Watch Server issues with Windows Server 2008
1. The SiteWatch (Server) installer may fail.
Even though Internet Information Services (IIS) Version 7 is installed, the SiteWatch
(Server) installer may display the message:
"Internet Information Services (IIS) is required for this application. Please
install IIS first then re-run this installation."
Solution: Install IIS Metabase and IIS 6 configuration compatibility on the e-Watch
server
- Click Start->Control Panel->Programs->Programs and Features
- Click Turn Windows features on or off
- Expand Roles
- Right-click Web Server (IIS)
- Click Add Role Services
- Under Management Tools, check IIS 6 Management Compatibility
- Click Next
- Click Install
2. The logon.asp page may fail to load.
Instead of loading logon.asp, Internet Explorer may display "HTTP Error
404", along with the message:
"The page you are requesting cannot be served because of the Multipurpose Internet
Mail Extensions (MIME) map policy that is configured on the Web server. The page you
requested has a file name extension that is not recognized and is not allowed."
Or
"HTTP Error 404"
Solution: Install Active Server Pages (ASP) on the e-Watch server
- Click Start->Control Panel->Programs->Programs and Features
- Click Turn Windows features on or off
- Expand Roles
- Right-click Web Server (IIS)
- Click Add Role Services
- Under Application Development, check ASP
- Click Next
- Click Install
3. The server may fail to respond to to the logon page.
After loading logon.asp, Internet Explorer may display "Server Did Not
Respond". If Windows Firewall logging is enabled, an error similar to the following
appears in the log file (default path
C:\windows\system32\logfiles\Firewall\pfirewall.log):
2009-07-27 14:38:58 DROP TCP
192.199.75.109 192.199.75.127 1414 3792 52 S
2689147845 0 65535 - - - RECEIVE.
Solution: Create an inbound rule to allow connections to e-Watch port 3792 on the
e-Watch server.
- Click Start->Administrative Tools->Windows Firewall
- Click Inbound Rules
- Click New Rule
- Click the Port radio button
- Click Next
- Click the TCP radio button
- Click the Specific local ports radio button
- Enter port number 3792
- Click Next
- Click the Allow the connection radio button
- Click Next
- Check the Domain, Private and Public
check boxes
- Click Next
- Enter a rule name and description
- Click Finish
4. The server may fail to respond to to the logon page.
After loading logon.asp, Internet Explorer may display "Server Did Not
Respond" and the following error event appears in the Application Log:
"com.ms.com.ComError: Failed creation of com/ms/wfc/data/adodb/Connection because
CoCreateInstance of CLSID {...} failed: Class not registered."
Solution: Manually register msado15.dll on the e-Watch server
- Locate the file msado15.dll - normally, this file is in the folder C:\Program
Files\Common Files\System\ado
- Open a command prompt and navigate to this folder
- Execute regsvr32.exe msado15.dll
- Restart the e-Watch Service
5. ViewWatch "ASP" pages may fail.
ViewWatch "ASP" pages that access the e-Watch databases, such as the Events
page and various reports pages, may fail with "500 - Internal server error" when
SiteWatch is installed with Microsoft Internet Information Services (IIS) Version 7.
Solution: Grant full control of the e-Watch databases folder to the IIS Anonymous User
Identity
Step 1: Determine the IIS Anonymous User Identity
- Click Start->Control Panel->Programs->Programs and Features
- Click Turn Windows features on or off
- Expand Roles
- Expand Web Server (IIS)
- Click Internet Information Services (IIS) Manager
- In the Connections window, click the local server
- In the Features View pane, double-click Authentication
- Right-click Anonymous Authentication
- Click Edit
- Note the anonymous user identity, e.g. "IUSR"
- Click Cancel
Step 2: Grant full control of the e-Watch databases folder to the IIS Anonymous User
Identity
- Run Windows Explorer
- expand the e-Watch installation drive (normally C:)
- expand the e-Watch folder
- Right-click the databases folder
- Click Properties
- Click the Security tab
- Click Edit
- Check whether the anonymous user identity (e.g. "IUSR") is in the Group
or user names list; if so, skip to step 14
- Click Add
- Choose "Select this object type:" Users, Groups or Built-in security
principals
- Choose "From this location:" <local server name>
- In the "Enter the object names to select" box, type the anonymous user
identity (e.g. "IUSR")
- Click OK
- In the "Group or user names" list, click the anonymous user identity (e.g.
"IUSR")
- In the "Permissions for <anonymous user identity>" box, click Full
control
- Click Apply
- Click OK
- Click OK
6. The Camera Configuration Utility may fail to execute.
The Camera Configuration Utility may fail to execute, and there is no way to open
Windows Media Player.
The Camera Configuration Utility requires Windows Media Player, which is not
automatically installed with Windows Server 2008.
Solution: Install the Windows Server 2008 Desktop Experience feature.
- Click Start->Control Panel->Administrative Tools->Server Manager
- In the left pane, click Features
- In the right pane, click Add Features
- Check the Desktop Experience checkbox
- Click Install
7. Windows Registry updates using the e-Watch Server App may not take effect.
Windows Registry updates using the e-Watch Server App may appear to succeed but
the software does not recognize the change.
This behavior is caused by Microsoft's Registry Virtualization feature, which causes
Registry updates made by any user other than the administrator to be redirected to a
different place in the Registry.
Solution #1: When preparing to use the e-Watch Server App to update the Windows
Registry, log on to the computer's administrator account.
Solution #2: When preparing to use the e-Watch Server App to update the Windows
Registry, right-click the desktop icon and click "Run as administrator".
ViewWatch issues with Microsoft Vista and Windows 7
1. The ViewWatch filter installer may fail when User Account Control is turned on.
The filter installer may fail with "Object doesn't support this property or
method" when User Account Control is turned on.
Solution #1: Turn off User Account Control on the ViewWatch computer
- Click Start->Settings->Control Panel->User Accounts->User Accounts
- Click Turn User Account Control on or off
- Uncheck Use User Account Control (UAC) to protect your computer
- Click OK
Solution #2: Select the "Run as administrator" option when opening Internet
Explorer
- Right-click an Internet Explorer shortcut
- Click Run as administrator
- Enter the e-Watch URL in the address bar
Or
- Create a shortcut to "iexplore.exe"
- Right-click the shortcut
- Click Properties
- Click the Shortcut tab
- In the Target box, append the e-Watch URL to the iexplore.exe path, for
example:
"C:\Program Files\Internet Explorer\iexplore.exe"
"http://myserver/ewatch/logon.asp?station=mystation"
- Click the Advanced button
- Check the Run as administrator checkbox
- Click OK
- Click OK
- Double-click the shortcut to launch ViewWatch
Solution #3: Manually install the filters on the ViewWatch computer
- Install the video filters using the installer on the SiteWatch CD in the
"filters" folder
- Append "filtercheck=false" to the ViewWatch logon URL, for example http://myserver/ewatch/logon.asp?station=main&filtercheck=false
(SiteWatch 3.1.7 or later)
- You must remember to re-install the filters each time you upgrade SiteWatch.
2. ViewWatch may not display multicast video.
ViewWatch may not display multicast video. Instead, the video panes display "Data
Stream Interrupted".
Solution: Create a Windows Firewall exception to open the e-Watch multicast port 5002.
- Click Start->Settings->Control Panel->Windows Firewall
- Click Change Settings
- Click the Exceptions tab
- Click Add port
- Enter a description such as "e-Watch Multicast Video"
- Enter port number 5002
- Click the UDP radio button
- Click OK

Copyright ©2001 - 2011 e-Watch Corporation, All rights reserved.
|