View FAQ
Frequently Asked Questions
Search
Keyword
Categories
Categories
WebWatchBot General 
Watch Item Settings/Configuration 
WebWatchBot Email Settings/Configuration 
WebWatchBot Connectivity - Network - Firewalls 
WebWatchBot Known Issues 
WebWatchBot Installation 
WebWatchBot Errors (Not Relating to Installation) 
WebWatchBot Known Issues - Resolved 
WebWatchBot Performance 
Article
Category Watch Item Settings/Configuration 
Question/Issue How can I monitor a web page with a login? 
Answer/Solution To do this, you would use the POST data feature and you will need to look at your web page's HTML source.

1. Create a new Watch Item
2. View the source of your web page and find the <form> tag.
3. The "action" attribute will equal the URL that you will actually monitor - not the page with the login form!
4. Find the <input> tags for the username and password
5. Your "POST" data will be the name/value pairs of these tags. For example if you have the tags:
<INPUT TYPE=text NAME=username>
<INPUT TYPE=password NAME=password>
Then your POST data will be "username=someuser&password=secret". Change the username and password to your data.
6. In your Watch Item, click the "Watch Type Settings" button. A new dialog box will open.
7. Click on the "Advanced" button.
8. Change the "Request Type" from "GET" to "POST"
9. Enter "username=someuser&password=secret" (without the quotes) in the field "POST Data"
10. Click OK until all dialog boxes are closed.
 
Permanent Link 57 
 
Category Watch Item Settings/Configuration 
Question/Issue How do you set-up a Watch Item for HTTP Post to an ASP.NET page? 
Answer/Solution PAGES WITHOUT <INPUT type="submit"> TAG:

Some ASP.NET pages are constructed in such a way that they do not have a <INPUT type="submit"> button, but rather use "post-back" techniques to submit a form. If this is the case, you should include __EVENTTARGET in your POST data:

__EVENTTARGET=some_id

Where "some_id" is the tag id of the button/link that users click to submit the form which causes the page to post-back and submit the form.


PAGES WITH <INPUT type="submit"> TAG:

include __EVENTTARGET in your POST data:

__EVENTTARGET=tag_name

Where "tag_name" is the name attribute of the <INPUT type="submit"> tag that users click to submit the form which causes the page to post-back and submit the form.
 
Permanent Link 58 
 
Category WebWatchBot Installation 
Question/Issue Error 1303. "The Installer Has Insufficient Privileges..." occurs When You Try to Install WebWatchBot 
Answer/Solution SYMPTOMS
When you install WebWatchBot, an error message similar to the following may appear:

Error 1303. The installer has insufficient privileges to access this directory: . The installation cannot continue. Log on as administrator or contact your system administrator.
where is the name of the directory with the insufficient privileges.

CAUSE
You will receive the above error if either of the following is true for the folder in which you are installing WebWatchBot:
The SYSTEM group does not have Full Control privileges.
-or-
The Everyone group does not have Full Control privileges.

RESOLUTION
To prevent this error from occurring, make sure the folder location into which you are installing WebWatchBot has Full Control permissions for either the Everyone group or the SYSTEM group. Check the permissions for the parent folders because the permissions on these folders may also cause this problem.
 
Permanent Link 59 
 
Category WebWatchBot Installation 
Question/Issue Error 1327 Occurs When You Try to Install WebWatchBot 
Answer/Solution SYMPTOMS
When you try to install WebWatchBot, you may receive an error message similar to the following
Error 1327. Invalid Drive: Drive
NOTE: This error message most frequently refers to drive U, but this may vary.


CAUSE
This behavior may occur if a registry key contains an incorrect value in a Data field.


RESOLUTION
To resolve this behavior, enter the correct value data for the registry key. To do this, follow these steps.

WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. ExclamationSoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
1. Click Start, and then click Run.
2. In the Open box, type regedit, and then click OK.
3. In Registry Editor, locate the following registry key:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders
4. In the right pane, note the values in the Data field of each entry. If any value contains a drive that is not correct for your computer, right-click the entry, type c:\my documents in the Value data box, and then click OK.
5. Repeat step 4 for each entry whose Data value contains an incorrect drive.
6. Repeat steps 3 through 5 for each of the following registry keys:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders
7. Close Registry Editor.
8. Install WebWatchBot. 
Permanent Link 61 
 
Category WebWatchBot Installation 
Question/Issue Error 1722 Occurs When You Try to Install WebWatchBot 
Answer/Solution SYMPTOMS:
During installation, an error 1722 occurs.

CAUSE:
There are several causes for this error. Three of the most common are:
1. The logged in user installing the application does not have the correct directory permissions.
2. During an upgrade from a previous version, an error has occurred in the database upgrade procedure.
3. Low Disk Space - check the system requirements of WebWatchBot to ensure that you have the minimum required disk space.

RESOLUTION/WORKAROUND:
1. Check the WebWatchBot System Requirements to ensure permissions are set correctly.
2. Check the log file wwbupgrade_log.txt in the directory "\Documents and Settings\All Users\Application Data\ExclamationSoft\WebWatchBot\Data". If there was an error noted in this log file, contact support and notify them of the error. 
Permanent Link 62 
 
Category WebWatchBot General 
Question/Issue When performing database maintenance, an error occurs 
Answer/Solution This can happen for several reasons:
1. The database is already open by another user/process running WebWatchBot Manager
2. The currently logged in user does not have permission to perform maintenance.
3. WebWatchBot is busy making database updates.

For reasons 1 and 2, ensure that the database is not in use and that the logged in user has permission to access the database file.

For reason 3, try performing database maintenance again: Tools -> Database -> Database Maintenance. If that does not resolve the problem, try suspending all Watch Items, then perform database maintenance. 
Permanent Link 63 
 
Category WebWatchBot Errors (Not Relating to Installation) 
Question/Issue Microsoft JET Database Engine Error: -2147467259 
Answer/Solution This error can happen for several reasons:
1. The database is already open by Access
2. The database is already open by another user/process running WebWatchBot Manager
3. The currently logged in user does not have permission to perform maintenance.
4. WebWatchBot is busy making database updates.

For reasons 1-3, ensure that the database is not in use and that the logged in user has permission to access the database file.

For reason 4, try performing database maintenance again: Tools -> Database -> Database Maintenance.

If the problem persists, please open a support case 
Permanent Link 64 
 
Category WebWatchBot Installation 
Question/Issue Error 1931 Occurs When You Try to Install WebWatchBot 
Answer/Solution SYMPTOMS:
Error 1931. The windows installer service cannot update the system file c:\windows\system32\odbcjt32.dll because the file is protected by windows. You need to update your operating system for this program to work correctly.

CAUSE:
The file "odbcjt32.dll" is locked and does not need to be updated by the Windows Installer

RESOLUTION/WORKAROUND:
During installation, you can safely click "OK" and ignore this message as it is only a warning and will not affect your installation of WebWatchBot.
 
Permanent Link 67 
 
Category WebWatchBot Email Settings/Configuration 
Question/Issue I'm not receiving email alerts 
Answer/Solution There are two possible problems and resolutions:

1. Email setting were recently changed and a restart of WebWatchBot needs to be performed. If you are running WebWatchBot as a service, simply restart the service: Tools -> Stop Service, Tools -> Start Service.

2. The email alert sent is being rejected by the mail server due to "bare LF" (refer to: http://cr.yp.to/docs/smtplf.html). To workaround this problem, uncheck the option to send output with the email alert (refer to: http://www.exclamationsoft.com/webwatchbot/help/website/SendAnEmail.html, Field "Send Output")  
Permanent Link 68 
 
Category WebWatchBot Email Settings/Configuration 
Question/Issue Cannot send email - Error 10053 Cannot connect to mail server 
Answer/Solution If you are using McAfee Virus Scan, it is blocking WebWatchBot from sending email.

Please see this KB article on how to resolve this issue:

http://www.exclamationsoft.com/ExclamationSoft/Support/kb/cannot_connect_10053.asp 
Permanent Link 71 
 
Category WebWatchBot Installation 
Question/Issue Install Fails with Error: Login failed for "xxx". Reason: Not associated with a trusted SQL Server connection 
Answer/Solution If the installation of WebWatchBot fails with the error: Login failed for "xxx". Reason: Not associated with a trusted SQL Server connection.

1. Configure SQL Server to accept a trusted connection:
(Please refer to the following KB article) http://www.exclamationsoft.com/ExclamationSoft/Support/kb/sql_server_trust.asp

2. Run the WebWatchBot setup again. 
Permanent Link 72 
 
Category WebWatchBot Installation 
Question/Issue Install Completes with Error: User xxx is not associated with a trusted SQL Server connection 
Answer/Solution DESCRIPTION
Installation error when installing to SQL Server database

SYMPTOMS
During installation, an error message appears "User xxx is not associated with a trusted SQL Server connection". The installation continues with success.

CAUSE
The machine WebWatchBot is being installed on cannot connect using a trusted connection as specified in the connection string.

RESOLUTION/WORKAROUND
1. Complete the installation and start WebWatchBot.
2. You should receive another error message stating that a connection to the database cannot be made and that you should check your database settings. If not, go to Tools -> Preferences -> Advanced Settings -> Database.
3. Enter database configuration on the settings screen that appears.
4. Either enter the Source, Username, and Password, or change the connection string.
5. Click OK
6. You will need to run the database creation script manually through SQL Server Query Analyzer. The script is located in the "resource" directory under the WebWatchBot installation folder, e.g. \Program Files\WebWatchBot 3\resource.
7. Start WebWatchBot.

 
Permanent Link 73 
 
Category WebWatchBot Errors (Not Relating to Installation) 
Question/Issue When starting WebWatchBot, an error appears: "Cannot connect to database error:-2146824582 Msg:Unknown error 0x800A0E7A" 
Answer/Solution This error is typically seen on older systems running Windows NT without the Jet Engine data provider installed.

Download the latest Jet 4.0 service pack: http://support.microsoft.com/default.aspx?kbid=239114#3 
Permanent Link 77 
 
Category WebWatchBot Installation 
Question/Issue Installation ends with an error, but there is no error number 
Answer/Solution To diagnose the problem, you will need to do the following:

1. Go to the command line (DOS prompt window).
2. Change directory to the location where the installation package is. For example:

cd \downloads
3. Type:

WebWatchBot5.1.3MSDE.exe /l log.txt
- or -
WebWatchBot5.1.3SqlServer.exe /l log.txt

This will run the installation with a log.

4. After you get the error, click OK. Send the log file to support@exclamationsoft.com.
 
Permanent Link 78 
 
Category WebWatchBot Errors (Not Relating to Installation) 
Question/Issue Error: -2147467259 Msg: Unspecified error Description: Cannot open any more tables 
Answer/Solution SYMPTOMS
At any point while running WebWatchBot, the following error appears:
Error: -2147467259 Msg: Unspecified error Description: Cannot open any more tables

RESOLUTION/WORKAROUND
Refer to Microsoft KB article: http://support.microsoft.com/default.aspx?scid=kb;en-us;304536

To resolve this problem, install the latest Microsoft Jet 4.0 service pack 6 
Permanent Link 79 
 
Category Watch Item Settings/Configuration 
Question/Issue Do you have a document which details the format of the ini file used in the import feature? 
Answer/Solution The .ini file is not documented, but here is what you can do:
1. Create a Watch Item and set the defaults you wish to use.
2. Export the one Watch Item: File -> Import/Export -> Export Selected
3. Open the .ini file
4. Copy-and-paste the entire section for the Watch Item.
5. Increment the section name, e.g. "[1076813251]" by one, for example "[1076813252]"
6. Change the value for "m_sWatchURL"
7. Change the value for "m_sDisplayName"
8. Import the file: File -> Import/Export -> Import 
Permanent Link 83 
 
Category WebWatchBot Errors (Not Relating to Installation) 
Question/Issue Microsoft JET Database Engine Error: File sharing lock count exceeded 
Answer/Solution SYMPTOMS:
The Event Viewer Application log shows an error from WebWatchBot with a similar description to: "Microsoft JET Database Engine
Error: -2147467259 Msg: Unspecified error Description: File sharing lock count exceeded. Increase MaxLocksPerFile registry entry..."

CAUSE:
Using a MS Access database with WebWatchBot, the total number of records in the database exceeds a threshold which causes long running queries to trigger this error.

WORKAROUND/RESOLUTION:
Follow the instructions to change the registry setting for "MaxLocksPerFile" to 50000. Refer to the Microsoft KB article for complete instructions:
http://support.microsoft.com/default.aspx?id=815281 
Permanent Link 84 
 
Category Watch Item Settings/Configuration 
Question/Issue The Log Pane shows an error message for all of my Watch Items, why? 
Answer/Solution SYMPTOMS
The Log Pane shows an error message for all of my Watch Items or the log files are never created even though the log type is not set to "none".
An error message is displayed in the log pane:
"The log file {logfilename} does not exist or cannot be opened."

CAUSE
If you switch WebWatchBot from Windows Application mode to Windows Service mode, you may experience this error. This is because your logged in user account and the service's user account are different and may have different permissions for the data directory.

RESOLUTION
To resolve follow these steps:
1. Stop the WebWatchBot service: Tools -> Stop Service
2. Select the menu: Help -> Exclamationsoft Support -> View Data Folder
3. Close WebWatchBot Manager
4. Delete all of the sub-directories that are named with numbers only, or change the permissions of all files and sub-folders so that "Everyone" group has full access.
5. Start WebWatchBot. 
Permanent Link 85 
 
Category WebWatchBot Known Issues - Resolved 
Question/Issue Under specific conditions scheduled reports contain no data. 
Answer/Solution SYMPTOMS
Scheduled reports contain the message "There is no data to report on at this time", and there is illegible "garbage" at the bottom of the report.

CAUSE
If the following conditions are met, the above symptoms are experienced:
1. WebWatchBot was recently installed.
2. WebWatchBot is configured to run as a windows service during the installation.
3. The WebWatchBot service has not been restarted and a reboot has not occurred since the installation.
4. A report is run through the WebWatchBot scheduler.

RESOLUTION/WORKAROUND
Restart the WebWatchBot service or reboot your computer
We will address this issue in an upcoming maintenance release. (Resolved) 
Permanent Link 86 
 
Category WebWatchBot Errors (Not Relating to Installation) 
Question/Issue Certificate from a CA that is not trusted causes error. 
Answer/Solution PROBLEM:
"The security certificate was issued by a company you have not chosen to trust. View the certificate to determine whether you want to trust the certifying authority."

RESOLUTION/WORKAROUND
You will need to install the certificate for all user account which access that site (or obtain a certificate from a trusted CA)

If you are running WebWatchBot as a Windows Service, you will need to log in under the account that is running the service (Control Panel -> Administrative Tools -> Services, service name "WWBServer") and install the certificate.

If the log in account is "SYSTEM", you should change it to an account that has Administrative privilege, then log in and install the certificate.

You will know they are both installed when the warning dialog no longer appears after you load the page when you first start-up your browser.

The process is not terribly complicated and should only take a few minutes to do.  
Permanent Link 90 
Previous [ 3 ] Next