View FAQ
Frequently Asked Questions
Search
Keyword
Categories
Categories
WebWatchBot General 
NetMailBot General 
Website - General  
NetMailBot Performance 
Watch Item Settings/Configuration 
WebWatchBot Email Settings/Configuration 
NetMailBot Mail Merge & Using a Database 
NetMailBot - Attachments 
WebWatchBot Connectivity - Network - Firewalls 
WebWatchBot Known Issues 
NetMailBot Installation 
NetMailBot Known Issues 
WebWatchBot Installation 
WebWatchBot Errors (Not Relating to Installation) 
WebWatchBot Known Issues - Resolved 
WebWatchBot Performance 
Article
Category Watch Item Settings/Configuration 
Question/Issue For transactions, what is the maximum amount of time that I should set the summary step's timeout? 
Answer/Solution The timeout for the summary can be an aggregate (total) of all steps in the transaction, but not necessarily so.

If you are interested in performance, then the summary timeout number should be set to the lowest acceptable number, e.g. 5000 ms (5 sec).
If you are more interested in completion of the transaction, then the number should be equal to or greater than the aggregate of all steps. 
Permanent Link 133 
 
Category WebWatchBot Installation 
Question/Issue How do I move WebWatchBot's data from one location to another? 
Answer/Solution WebWatchBot's data folder can be changed from the default to a different directory.

NOTE:
1. This procedure requires changes to the registry. If you are uncomfortable making these changes, DON’T DO IT.
2. The drive and folder used by default is standard for Windows programs, e.g. C:\documents and settings\...


1. Create the new folder where you wish to store WebWatchBot's data.
2. Stop the WebWatchBot service: Tools -> Stop Service
3. Close WebWatchBot Manager.
4. Stop SQL Server, if applicable. (Start -> Control Panel -> Administrative Tools -> Services)
5. Next, update the registry to point to this new location
6. Open the system registry: Start Menu -> run -> type "regedit", press enter.
7. Navigate to HKEY_LOCAL_MACHINE
8. Navigate to Software, ExclamationSoft, WebWatchBot 2/3/4/5, General
9. Change the string (double-click on) Data_Path to the new drive and directory where you would like to store data.
10. (Version 2/3/4 using the Standard MS Access database only) Change the string (double-click on) DATABASE_FILENAME to the new drive and directory where the database now resides.
11. Copy any existing data from the old location to the new location. This includes folders and files.
12. If you are using WebWatchBot with MSDE: The database engine needs to point to the new location. You have two options: 1. Uninstall WebWatchBot, install WebWatchBot and specify the new location. 2. Using SQL Server tools (Management Studio or Enterprise Tools), attach the database to the new location. Refer to SQL Server documentation for more detail – this is not supported by ExclamationSoft.
13. If you are using WebWatchBot for SQL Server, use SQL Server tools (Management Studio or Enterprise Tools), attach the database to the new location. Refer to SQL Server documentation for more detail – this is not supported by ExclamationSoft.
14. Start WebWatchBot Manager, and you should be prompted to start the service, if applicable.
 
Permanent Link 134 
 
Category WebWatchBot Performance 
Question/Issue WebWatchBot is running slow/sluggish 
Answer/Solution PROBLEM:
WebWatchBot is running slow/sluggish

SYMPTOMS:
Charts load slowly, selecting different Watch Items take a long time.

SOLUTION:
-=Memory=-
WebWatchBot performance is greatly reliant on physical memory available.
Increasing the amount of physical RAM on the machine running WebWatchBot will increase performance.

-=WebWatchBot Manager=-
The real-time chart requires a good amount of system resources to display and update data. Switching to the Log view will save resources.

-=SQL Server=-
Using SQL Server as the back-end database to store WebWatchBot's data (an option during install) is the best option for long-term performance.

-=Database Maintenance=-
Performing database maintenance on a regularly scheduled basis is also beneficial to performance. We recommend scheduling database maintenance at least once a week or more .

-=Permissions=-
Another area to check is file permissions. If your Windows user account (what you signed into Windows with) or the "SYSTEM" account does not have "Full Control" permission to the data directory (Get there from the menu: Help -> ExclamationSoft Support -> View Data Folder), then WebWatchBot will start-up and perform slowly.
 
Permanent Link 135 
 
Category NetMailBot Known Issues 
Question/Issue NetMailBot 30-Day Trial will not start on Windows 2003 
Answer/Solution SYMPTOMS
When running NetMailBot, the following error occurs:

Cannot find import; DLL may be missing, corrupt, or wrong version File "BotDll.dll", error 998

CAUSE
Our copy protection system conflicts with Windows 2003

RESOLUTION/WORKAROUND
Refer to the following KB article, replacing references to the product WebWatchBot with NetMailBot: http://www.exclamationsoft.com/exclamationsoft/support/kb/install_win2003sp1.asp 
Permanent Link 136 
 
Category NetMailBot Known Issues 
Question/Issue Error: Cannot find import; DLL may be missing, corrupt, or wrong version File "BotDll.dll", error 998 
Answer/Solution SYMPTOMS
When running NetMailBot, the following error occurs:

Cannot find import; DLL may be missing, corrupt, or wrong version File "BotDll.dll", error 998, or "system cannot find the file specified"

CAUSE
Our copy protection system conflicts with Windows 2003

RESOLUTION/WORKAROUND
Refer to the following KB article, replacing references to the product WebWatchBot with NetMailBot: http://www.exclamationsoft.com/exclamationsoft/support/kb/install_win2003sp1.asp 
Permanent Link 137 
 
Category Watch Item Settings/Configuration 
Question/Issue What should the threshold for maximum response time be set to? 
Answer/Solution A Watch Item’s threshold for response time maximum is used to trigger an alarm which depends on different factors:
1. How fast should the Watch Item respond, e.g. what is an acceptable amount of time: 2 seconds? 5 seconds?

2. What is the average response time? A Watch Item's response time can fluctuate over time, but an average will be evident after a day of testing or when a hundred or so data points are collected.

3. What is the threshold at which someone should be notified? If a Watch Item responds after 10 seconds once a day, is it a cause for concern or just an anomaly?

Taking everything into account:
1. If a Watch Item should respond in 2 seconds (2000 ms), a recommended threshold is at least 2 times that amount – 4 seconds - to prevent false alarms. Setting the threshold to 2 seconds would cause an alarm to trigger frequently.

2. If the average response time is 3 seconds (3000 ms) then setting the threshold too low, say 4 seconds, may be too low because it does not take into account fluctuations during the day.

3. If someone should be notified as soon as a Watch Item responds slowly, then the threshold should be set to a number that reflects the urgency. If a Watch Item is monitoring a critical web page that cannot ever go down, setting the threshold to a low number will trigger more often, allowing the opportunity for more scrutiny.

Examples:
SCENARIO 1: Home Page of corporate website. The site is critical for the company’s image and cannot be unavailable. The page should respond – best case scenario - in 1 second or less, averages a download time 1200 ms, responds quickly – 800 ms - in the morning and nighttime hours, slowly - 1500 ms - in the afternoon when traffic peaks, and moderately – 1100 ms - in the evening. The system administrator needs to be notified as soon as the site has an outage – does not respond at all.
RECOMMENDATION: Set the threshold for maximum response time to 5000 ms, and set the trigger for an alarm to 1 consecutive failure to ensure the sys admin is notified of all problems.

SCENARIO 2: Sub-page of a website that connects to a database and displays dynamic content. The page is not critical but important. The page should respond in 3 seconds, averages around 3 seconds and the response time does not fluctuate throughout the day. Someone should be notified if the page goes down for more than a few minutes.
RECOMMENDATION: Set the threshold for maximum response time to 10000 ms, and set the trigger for an alarm to 3 consecutive failures to ensure someone is notified that there is a problem.

SCENARIO 3: Login page for a company Intranet. Response time is not critical, but having the page available is a must. The page should load and respond in 5 seconds.
The average response time is 10 seconds – it’s slow and the website programmers are looking into it – and fluctuate wildly.
RECOMMENDATION: Set the threshold for maximum response time to 50000 ms, and set the trigger for an alarm to 3 consecutive.

 
Permanent Link 138 
 
Category WebWatchBot Known Issues - Resolved 
Question/Issue Status Reports: Watch Groups and Transactions are repeated 
Answer/Solution SYMPTOMS (Fixed in v4.0.2)
After changing settings for a status report, Watch Groups and Transactions are displayed more than once. Problem only occurs when running WebWatchBot as a Windows Service and if Watch Groups and/or Transactions are displayed.

RESOLUTION/WORKAROUND
Stop and Start the WebWatchBot service after all changes to status report settings. This issue will be fixed in version 4.0.2 and 3.0.11 
Permanent Link 139 
 
Category NetMailBot General 
Question/Issue What are the limitations of the trial version of NetMailBot? 
Answer/Solution There are two limitations:
1. You can only trial the software for 30 days.
2. You can only send 100 separate emails per run/execution of NetMailBot. 
Permanent Link 140 
 
Category WebWatchBot Known Issues - Resolved 
Question/Issue Changing the setting to 0 (zero) for "Simulate HTTP Threads" causes an error in WebWatchBot 
Answer/Solution PROBLEM (Fixed in v4.0.4)
Changing the setting for "Simulate HTTP Threads" causes an error in WebWatchBot

SYMPTOMS
Application error in WebWatchBot Manager or WWBServer

RESOLUTION/WORKAROUND
Set the value to 1 which will give the same results as 0

The problem is that the formula is: total image download time / simulate threads

Example:
4565 / 0 = divide by zero error - causing the error
4565 / 1 = 4565
4565 / 3 = 1521.67 (default)

This will be fixed in version 4.0.4 
Permanent Link 141 
 
Category WebWatchBot Known Issues - Resolved 
Question/Issue After creating a transaction, a popup appears stating that there are orphaned Watch Items 
Answer/Solution SYMPTOMS
After creating a transaction, a popup appears stating that there are orphaned Watch Items. This problem only occurs in v4.0.4 build 14400

RESOLUTION/WORKAROUND
Three solutions available:
1. Download the hot fix here: http://www.exclamationsoft.com/ExclamationSoft/download/WebWatchBot4.0.4hotfix.zip
Then unzip the one file (wwbgui.exe) in your WebWatchBot installation folder, e.g. C:\Program Files\WebWatchBot 4The build number should show 14401.

2. Download and install the full install of WebWatchBot v4.0.4 build 14401: http://www.exclamationsoft.com/ExclamationSoft/download/WebWatchBot.zip


If you do not want to install the hot fix or the full install, use the workaround:
3. Click the button "Do Nothing" to ensure that the Watch Items are not deleted or made non-transaction exclusive.

This problem has been resolved in version 4.0.5 
Permanent Link 144 
 
Category WebWatchBot Known Issues - Resolved 
Question/Issue Error creating a new Watch Group. 
Answer/Solution PROBLEM:
Adding a new Watch Group, creating a new Watch Item, then immediately adding it to the newly created group when prompted, causes the WebWatchBot service to error.

SYMPTOMS:
An error occurs.

WORKAROUND/SOLUTION:
Stop the WebWatchBot service, add a new Watch Group, start the WebWatchBot service.

This issue will be resolved in the next maintenance release, v4.0.6.

Resolved in v4.0.6 
Permanent Link 145 
 
Category WebWatchBot Installation 
Question/Issue How do I move WebWatchBot from one computer to another? 
Answer/Solution For WebWatchBot version 4, please refer to this KB article: http://www.exclamationsoft.com/ExclamationSoft/Support/kb/webwatchbot_data_move_v4.asp

For WebWatchBot version 5, please refer to this KB article: http://www.exclamationsoft.com/ExclamationSoft/Support/kb/webwatchbot_data_move_v5.asp 
Permanent Link 146 
 
Category WebWatchBot Known Issues - Resolved 
Question/Issue WebWatchBot using SQL Server as its back-end database uses large amounts of memory. 
Answer/Solution SYMPTOMS
** Update: (3 June 2006) The problem is not a memory leak, but rather a cause of how SQL Server is configured. Please refer to this KB article: http://www.exclamationsoft.com/exclamationsoft/customersupport/faqarticle.asp?faq_id=149&


In some cases SQL Server will not release memory, causing the memory usage of the SQL Server process, and in some cases WWBServer process to climb.

RESOLUTION/WORKAROUND
Create a scheduled item in WebWatchBot to run once a day – or less if the problem is not severe.
1. Switch to the Scheduler View
2. Create a new Scheduled Item: In WebWatchBot Manager, select the menu item "File" -> "New" -> "Scheduled Item" (Ctrl-N) or click the "New" icon on the toolbar.
3. The "Schedule Item" window will appear.
4. Select the Watch Item "All Watch Items" from the Watch Item dropdown list.
5. The “type” should be “Maintenance”
6. Set the start date and time to be any time you wish. Set the end date and time to be one minute later than the start time.
7. Set the pattern to daily, or weekly if the problem is not severe enough to warrant daily.
8. Click OK to save the scheduled item.

When WebWatchBot goes into maintenance mode, it disconnects from SQL Server and shuts down all Watch Items and Transactions, allowing SQL Server to release memory.  
Permanent Link 147 
 
Category WebWatchBot Known Issues - Resolved 
Question/Issue Cannot create a new report 
Answer/Solution SYMPTOMS
Creating a new report causes WebWatchBot to exit unexpectedly.

RESOLUTION/WORKAROUND
A fix for this bug will be issued in v4.0.7

** Resolved in v4.0.7 ** 
Permanent Link 148 
 
Category WebWatchBot Performance 
Question/Issue SQL Server uses a large amount of memory (memory leak) 
Answer/Solution SYMPTOMS
Applies to: WebWatchBot installations with SQL Server as the back-end database.

Over a period of time, the SQL Server process (sqlservr.exe) consumes a large amount of memory and can appear to be a memory leak because memory consumption increases consistantly.

CAUSE
SQL Server manages memory and will increase usage as configured. By default SQL Server can use up to the total amount of physical memory.

RESOLUTION
To limit the maximum amount of memory that SQL Server can use, please refer to the Microsoft KB article on configuring SQL Server Memory Usage: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_config_9zfy.asp 
Permanent Link 149 
 
Category WebWatchBot Known Issues - Resolved 
Question/Issue "Connection is busy with results for another hstmt"  
Answer/Solution SYMPTOMS
In the event viewer, application log, one or more entries with the following description: "Error: -2147467259 Msg: Unspecified error Description: [Microsoft][ODBC SQL Server Driver]Connection is busy with results for another hstmt
Query: SELECT * FROM WatchItemStats WHERE WatchItemId = xxx"

CAUSE
SQL Server is not executing the query requested because it is busy with other queries.

RESOLUTION/WORKAROUND
This issue should be resolved in version 4.0.10 or later, including version 5.0 and later. 
Permanent Link 151 
 
Category WebWatchBot Installation 
Question/Issue How do I change the user account the WebWatchBot service uses? 
Answer/Solution To change the user account of the WebWatchBot Service:
1. Delete log files and saved output (This is necessary to ensure that the logs and output do not retain permissions from the old user account):
a. Open WebWatchBot Manager
b. Select from the menu: Help -> ExclamationSoft Support -> View Data Folder
c. When the Windows Explorer/My Computer window opens, close WebWatchBot Manager.
d. Select all of the numbered folders and delete. This will only delete log files and last saved output and your data will remain intact.
e. Close the window
2. Start (Windows Start Button)
3. Control Panel
4. Administrative Tools
5. Services
6. Find "WWBServer" (the WebWatchBot Service name)
7. Stop the service
8. Right-click on WWBServer and select "Properties"
9. Click the "Log on" tab.
10. Select the "This account tab"
11. Enter the user account and password. You should enter a user account that has high enough privilege to create, modify, read and write to files on the computer, send email, and access network resources.
12. Click OK
13. Start WebWatchBot Manager.
14. When prompted, start the WebWatchBot service.
 
Permanent Link 152 
 
Category WebWatchBot Known Issues 
Question/Issue Web Position Gold Scheduler may prevent WebWatchBot Manager from starting 
Answer/Solution PROBLEM
If Web Position Gold Scheduler is running, WebWatchBot Manager will not start.

SYMPTOMS
When WebWatchBot is launched, its window will not appear. Task scheduler shows WebWatchBot's process running at 100% CPU usage.

RESOLUTION/WORKAROUND
Before starting WebWatchBot, stop the Web Position Gold Scheduler, start WebWatchBot Manager, then start Web Position Gold Scheduler again. WebWatchBot Manager will continue to run while the scheduler is started and running. 
Permanent Link 153 
 
Category WebWatchBot Installation 
Question/Issue How do I connect to a SQL Server 2005 Express Instance 
Answer/Solution Microsoft provides a free version of its SQL Server 2005 software, known as the Express Edition.

When using WebWatchBot, you must specify the machine name of the SQL Server instance you would like to use to store historical and configuartion data.

The machine name, by default is:
MACHINENAME\SQLEXPRESS

Additionally, there is a 15 character limit on the machine name. If the machine name exceeds 15 characters, only specify the first 15 characters.

For example, if the machine name is Windows2003StandardServer, you would specify a machine name of Windows2003Stan. 
Permanent Link 154 
 
Category WebWatchBot Errors (Not Relating to Installation) 
Question/Issue Error message when running the WebWatchBot Updater 
Answer/Solution **This is a non-critical error that will be resolved in version 5.0.3**

SYMPTOMS:
After checking for a new version of WebWatchBot and answering "Yes" to the prompt to download the update, and error occurs that a file is not found.

RESOLUTION/WORKAROUND:
Manually download the updater and run it: http://www.exclamationsoft.com/ExclamationSoft/download/instructions/html.asp?product=WebWatchBot&fe=no
 
Permanent Link 155 
Previous [ 6 ] Next