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 WebWatchBot General 
Question/Issue SQL Server and its files are taking up a large amount of disk space. 
Answer/Solution SQL Server automatically creates a database called tempdb for use as a workspace.

The simplest thing you can do to shrink tempdb to its minimum size is to shut down the SQL Server service and then restart it - there is no need to reboot.

If you need to control where the SQL Server files are located, e.g. not the C: drive, then you should consider installing a fully licensed copy of SQL Server (SQL Server 2005 Express Edition is free and is certified to work with WebWatchBot). 
Permanent Link 156 
 
Category WebWatchBot Errors (Not Relating to Installation) 
Question/Issue Service terminated because it was unable to initialize tcp/ip communications: Address already in use! 
Answer/Solution The error message "WebWatchBot Service terminated because it was unable to initialize tcp/ip communications: Address already in use!" usually means that another program/service is using port 444.

The cause for this error is if there are two instances of WebWatchBot running, e.g. two or more processes named "WWBGui.exe" or "WWBServer.exe" or if another program is using port 444.

To check for a conflict, open a dos command prompt window and type "netstat -a". This will produce a list of all the ports in use on your system. For example:
TCP MACHINENAME:444 MACHINENAME:0 LISTENING
This shows that something has a lock on port 444.

And a line like this:
TCP MACHINENAME:444 localhost:2692 ESTABLISHED
This shows that something is connected.

If you have the "Established" line, then something is already using that port - perhaps another instance of WebWatchBot. In this case, you can open the Windows task manager and search for a running process named "WWBGui.exe"

In the event of a conflict with another program, you can change the port numbers used by WebWatchBot. Since you cannot open WebWatchBot Manager, you will need to modify the registry.

1. Stop the WebWatchBot service (named WWBServer)
2. Open the registry editor: Start -> Run, type "regedit", then press Enter.
3. Navigate to: HKEY_LOCAL_MACHINE\SOFTWARE\Exclamationsoft\WebWatchBot\5.0\General
4. Double click "TCP_SERVER_PORT", select "Decimal" (ensure HEX is not selected) and enter a new port number then click OK.
5. Navigate to: HKEY_CURRENT_USER\Software\ExclamationSoft\WebWatchBot\5.0\Client
6. Double click "TCP_SERVER_PORT", select "Decimal" (ensure HEX is not selected) and enter the same port number you entered on step 4 then click OK.
7. Start WebWatchBot Manager - if you don't get the error then start the service when prompted.
 
Permanent Link 157 
 
Category Watch Item Settings/Configuration 
Question/Issue Cannot connect via Remote Connection Functionality 
Answer/Solution SYMPTOMS:
Using the Remote Connection Functionality, WebWatchBot clients cannot connect to the server. All settings are correct, however, the message "Cannot connect to remote server"

RESOLUTION/WORKAROUND:
On the server, check if the Windows Firewall service is running. If it is, try turning off the firewall, then test the connection from the client to the server again. If this works, configure Windows Firewall to allow connections on the remote connection port (by default 444) 
Permanent Link 158 
 
Category WebWatchBot Errors (Not Relating to Installation) 
Question/Issue WebWatchBot Service terminated because it was unable to initialize tcp/ip communications: Address already in use! 
Answer/Solution The error message "WebWatchBot Service terminated because it was unable to initialize tcp/ip communications: Address already in use!" usually means that another program/service is using port 444.

To check for a conflict, open a dos command prompt window and type "netstat -a". This will produce a list of all the ports in use on your system. For example:
TCP MACHINENAME:444 MACHINENAME:0 LISTENING
This shows that something has a lock on port 444.

And a line like this:
TCP MACHINENAME:444 localhost:2692 ESTABLISHED
Means that something is connected.

If you have the "Established" line, then something is already using that port - perhaps another instance of WebWatchBot. In this case, you can open the Windows task manager and search for a running process named "WWBGui.exe"

In the event of a conflict with another program, you can change the port numbers used by WebWatchBot. Since you cannot open WebWatchBot Manager, you will need to modify the registry.

1. Stop the WebWatchBot service (named WWBServer)
2. Open the registry editor: Start -> Run, type "regedit", enter.
3. Navigate to: HKEY_LOCAL_MACHINE\SOFTWARE\Exclamationsoft\WebWatchBot\5.0\General
4. Double click "TCP_SERVER_PORT", select "Decimal" (ensure HEX is not selected) and enter a new port number then click OK.
5. Navigate to: HKEY_CURRENT_USER\Software\ExclamationSoft\WebWatchBot\5.0\Client
6. Double click "TCP_SERVER_PORT", select "Decimal" (ensure HEX is not selected) and enter a the same port number you entered on step 4 then click OK.
7. Start WebWatchBot Manager - if you don't get the error then start the service when prompted.
 
Permanent Link 159 
 
Category WebWatchBot General 
Question/Issue How can I perform a round-trip check of an email? 
Answer/Solution 1. Create a SMTP Watch Item that sends a message to an email account that is specifically for testing. For verification, the email sent should contain text that will be searched on when downloaded.

2. Create a POP3 Watch Item that retrieves email from the test email account, and searches for the text included in the message.

3. Link the two together by putting them in a Transaction and order them so that the SMTP Watch Item runs first, and the POP3 Watch Item runs second. If one or both fail, the transaction will fail and an alarm can be triggered.
 
Permanent Link 160 
 
Category Watch Item Settings/Configuration 
Question/Issue WARNING: The WebWatchBot service was not found or you do not have permission to control Windows Services. 
Answer/Solution Check that the service is installed: Start -> Control Panel -> Administrative Tools -> Services. Look for the service named "WWBServer".
1. If it does not exist, you need to reinstall WebWatchBot with an account that has administrative rights and the ability to control Windows Services.
2. If it does exist, but it shows a state of "Disabled", you should reboot then check that the service has started upon reboot.
3. If it does exist and is running, then your Windows user account does not have access to control Windows services. Check with your network/system admin.
4. If it does exist and is stopped, try starting the service. If you cannot start the service, then your Windows user account does not have permission to control Windows services. Check with your network/system admin. 
Permanent Link 161 
 
Category WebWatchBot Errors (Not Relating to Installation) 
Question/Issue WARNING: The WebWatchBot service was not found or you do not have permission to control Windows Services 
Answer/Solution In order for WebWatchBot to check the status of the WebWatchBot service, the user account running WebWatchBot Manager must have permission to control Windows Services.

On Windows Vista with UAC (User Access Control) enabled., this error message can occur if WebWatchBot Manager is run normally (even a user account in the Administrators group).

To resolve this issue, run WebWatchBot Manager "as Administrator". To do this, open Windows Explorer/My Computer and go to the WebWatchBot install location: c:\program files\webwatchbot 5. Right-click on Wwbgui.exe and select "Run As Administrator". You can also create a shortcut on your desktop to easily open WebWatchBot in the future.
 
Permanent Link 162 
 
Category NetMailBot General 
Question/Issue NetMailBot successfully sends a message to my Exchange server, but the email is never received. 
Answer/Solution SYMPTOMS
NetMailBot successfully sends a message to my Exchange server, but the email is never received. The log from NetMailBot shows that the email is accepted by the mail server.

CAUSE
IMF (Intelligent Message Filter) is blocking the email from being sent.

RESOLUTION/WORKAROUND
Check the event viewer, application log for informational messages from IMF, stating that messages are rejected/deleted from a particular computer.
Configure IMF to allow messages to be sent by a computer/ip address/email address. Consult your Exchange/IMF documentation for more guidance. 
Permanent Link 163 
 
Category WebWatchBot General 
Question/Issue Why are there false positives? Some sites go down when they are not, why? 
Answer/Solution SYMPTOMS:
False positives are sometimes received.
WebWatchBot reports a server or website as down when it is not.

CAUSE:
The computer that WebWatchBot is installed on is being overtaxed, causing a cascading affect on what is being monitored. With less available resources, monitoring of Watch Items can take longer, causing them to fail and report false positives.

RESOLUTION:
1. The console does not need to remain open in order for WebWatchBot to monitor. Close the console when not in use.
2a. If you have WebWatchBot for SQL Server installed: If the database is on the same server as WebWatchBot, relocate it to a different machine.
2b. If you are using WebWatchBot with MSDE: Consider using SQL Server. Download SQL Server 2005 Express (FREE) from Microsoft: http://msdn.microsoft.com/vstudio/express/sql/default.aspx. Testing has shown SQL Server 2005 to have considerable performance increases over its predecessors.
3. Don't run other applications on the same machine as WebWatchBot. Other applications and programs can consume resources which deprive WebWatchBot of necessary resources and can cause Watch Items to fail.
4. Install WebWatchBot on a more powerful machine. More memory can be useful, but it really comes down to the CPU.
 
Permanent Link 164 
 
Category Watch Item Settings/Configuration 
Question/Issue How do I log into an OWA (Outlook Web Access) Site? 
Answer/Solution Instructions for logging into OWA, where integrated and basic authentication are enabled:

With the WebWatchBot Transaction recorder, enter the OWA site url in the form of: http://site/exchange/username

Where username, in the URL, is the name of the user's AD account.

In Watch Item settings, click the "Settings" button. The HTTP Settings window will open. Select the "Advanced" tab, and enter the username and password. 
Permanent Link 165 
 
Category WebWatchBot General 
Question/Issue Can WebWatchBot monitor websites with frames? 
Answer/Solution The simple answer is no. Framed website pose a particular problem when a site uses web based logins and forms since multiple pages need to be rendered at one time.

A possible workaround is to monitor one frameset at a time; however, this can be problematic and results may vary. 
Permanent Link 166 
 
Category WebWatchBot General 
Question/Issue Can I switch from MSDE to SQL Server 2005? 
Answer/Solution Yes. If you are experiencing problems with the limitations of managing your database on MSDE, you should upgrade to SQL Server 2005. Microsoft has an excellent article describing how to do it: http://www.microsoft.com/technet/prodtechnol/sql/2005/msde2sqlexpress.mspx 
Permanent Link 167 
 
Category WebWatchBot Errors (Not Relating to Installation) 
Question/Issue Database Watch Type: Cannot connect to mySql database 
Answer/Solution mySql ODBC driver version 3.51.10 contains a bug which prevents connection with error message "Access Denied" or "Catastrophic Error". To resolve by downgrade to another driver version or install the newest version of the driver. 
Permanent Link 168 
 
Category WebWatchBot Known Issues - Resolved 
Question/Issue SMS Email Alerts Sent as HTML for WebWatchBot v5.1.x Pro 
Answer/Solution Email Alerts: If upgrading from a version previous to v5.1 or upgrading Professional to Enterprise and email alerts are configured to send out as SMS, email alerts were not being sent as SMS but rather as HTML.

This was fixed in v5.1.2 
Permanent Link 169 
 
Category WebWatchBot Installation 
Question/Issue Error 87 installing WebWatchBot with MSDE 
Answer/Solution SYMPTOMS
WebWatchBot with MSDE will not install and returns an error 87

CAUSE/CONDITIONS
When trying to install SQL Server 2000 Desktop Engine (MSDE 2000) on a Windows 2000 Server Domain Controller, the progress bar rolls back at the end and the setup fails. The following conditions must be true for this to occur:
1. The server on which MSDE is being installed is not the first Domain Controller in the domain.
2. The Primary (or first) Domain Controller is not available.

With verbose logging enabled (i.e, WebWatchBot5.1.1MSDE.exe /L*v c:\temp\msde.log; replace version number with the one you are installing), you will notice the following error in the setup log:

Starting custom action InstallSQLAgentSecurity InstallSQLAgentSecurity failed (MACHINENAME,LocalSystem,87). Action ended 13:58:26: InstallFinalize. Return value 3.

WORKAROUND/SOLUTION
1. Ensure that the Primary Domain Controller (PDC) is available when installing MSDE 2000 on a Backup Domain Controller.
2. Ensure the service "Server" is enabled and running.
3. Ensure the service "File and printer sharing" is enabled and running.

If none of these solutions work, you have the option of downloading and installing the free SQL Server 2005 Express from Microsoft (http://msdn.microsoft.com/vstudio/express/sql/default.aspx), then installing WebWatchBot for SQL Server (http://www.exclamationsoft.com/ExclamationSoft/download/instructions/html.asp?product=WebWatchBot&fe=no)
 
Permanent Link 170 
 
Category WebWatchBot General 
Question/Issue What is the name of the WebWatchBot service? 
Answer/Solution The WebWatchBot service name in services.msc is WWBServer. The executibles for this service are: EXService.exe and WWBServer.exe. 
Permanent Link 171 
 
Category WebWatchBot General 
Question/Issue The WebWatchBot service does not appear in the services.msc control panel applet 
Answer/Solution If WebWatchBot was re-installed, reboot the computer, then check for the service again. 
Permanent Link 172 
 
Category WebWatchBot Installation 
Question/Issue Install Fails with error message "The instance name specified is invalid" 
Answer/Solution This error message is displayed when SQL Server is installed (either SQL Server 2000 or MSDE), or if it was installed at one time and was not properly or fully uninstalled. Some applications, like ours, install MSDE without any user intervention, making it difficult to know that it has been installed.

Look for the directory \Program Files\Microsoft SQL Server. If it exists, then SQL Server 2000 or MSDE is installed.

If SQL Server 2000 or MSDE are installed, you will need to download and install WebWatchBot for SQL Server. 
Permanent Link 173 
 
Category WebWatchBot Errors (Not Relating to Installation) 
Question/Issue Error Code: 5 - Message: Access is denied. 
Answer/Solution PROBLEM
ERROR: Could not load template file: C:\Program Files\WebWatchBot 5\resource\template_alert_html.html - Error Code: 5 - Message: Access is denied.

CAUSE
The WebWatchBot service (named: WWBServer), by default, runs under the local SYSTEM account (Windows User Account) which is different than your currently logged in user account.

This user account, by the error given, does not have access to the file and/or directory noted.

SOLUTION/WORKAROUND
Either change the Windows user account for the WebWatchBot service to one that has the required permission, or grant permission to the local SYSTEM account.

Once the change is made, restart the service and the error should no longer appear.
 
Permanent Link 174 
 
Category WebWatchBot Installation 
Question/Issue How do I install WebWatchBot on two or more machines that point to one SQL Server? 
Answer/Solution You can install WebWatchBot on two or more machines and point them all at the same SQL Server instance.

You will need to rename each database so that you can have one or more concurrent WebWatchBot databases running on one SQL Server.

Here are the steps to take:
1. Install your first instance of WebWatchBot. A database named “WebWatchBot” is created.
2. Start WebWatchBot Manager
3. Stop the WebWatchBot service: Tools -> Stop Service
4. Rename the database, i.e. “WebWatchBot1”, “WebWatchBotProd”, etc.
5. Change the connection string that WebWatchBot uses to connect to its database on SQL Server
a. Open the registry editor: Start -> Run, “regedit”
b. Navigate to: HKEY_LOCAL_MACHINE\SOFTWARE\ExclamationSoft\WebWatchBot\5.0\General
c. Change the string value “CONNECTION_STRING”. For example, a connection string looks like: DRIVER=SQL Server;SERVER=MACHINENAME\SQLEXPRESS;Database=WebWatchBot;UID=wwb;PWD=wwb$1. Change the database name from “WebWatchBot” to “WebWatchBot1” (or the name you changed it to in SQL Server).
d. Click OK and close the registry editor.
6. Start WebWatchBot Manager – the database will be connected to. If it fails, go back and verify each step.
7. Start the WebWatchBot service when prompted or select the menu options: Tools -> Start Service.
8. Install your second instance of WebWatchBot. A database named “WebWatchBot” is created.
9. Repeat for additional instances of WebWatchBot. 
Permanent Link 175 
Previous [ 7 ] Next