OPS Systems Knowledge Base

Supported Source Field Identifiers for Q12916

Les Poyner — Tue, 09 Mar 2010 08:13:47 GMT

Abstract:

Hach WIMS Direct Server-Side Interface to Custom Q12916 Aspen LIMS supports reading of the following fields from the text files:

COLUMN 1 : Date and time stamp
COLUMN 2 : Variable ID
COLUMN 3 : Result
COLUMN 4 : Symbol
COLUMN 5 : Data Approval (Y or N)
COLUMN 6 : Expanded Aspen Source Data 1
COLUMN 7 : Expanded Aspen Source Data 2
COLUMN 8 : Expanded Aspen Source Data 3

In order to set this up, first create additional information fields in the Hach WIMS client under System Setup -> System Tables -> This Facility -> Additional Info Tables -> and select the option Data Additional Info.

Create a New field:

Now run the interface and navigate to Configuration -> Advanced Configuration -> Additional Info tab and click the Configure Additional Info button.

When you click the box just below the title Source Field Identifier, the following screen will appear. Select the appropriate field you want imported to the additional info field you created.

Click the corresponding box below the title; Target WIMS Facility Identifier Field Identifier.

When attempting to install a collector for a Hach WIMS Indirect Interface using the MSI installation package provided by Hach, you get a message stating that "[Specific Interface] cannot be installed on systems with Windows Installer version smaller than 3.01" as shown here:

CAUSE:

The Hach WIMS Interface installers require a Windows Installer of version 3.1.xxx or higher. Many systems do not get updated or do not have access to Windows Updates and therefore do not have this already installed. This is especially common in isolated networks, such as those for SCADA systems in treatment plants, that do not have access to the Internet.
NOTE: If you are using an installation CD or DVD this requirement should be caught by the installation bootstrapper and installed prior to installing the interface. The Windows Installer 3.1 is included on the CD or DVDs provided by Hach.

SOLUTION:

Download the latest Windows Installer from Microsoft's Website (links provided below)
Copy it to a CD, DVD or USB Flash Drive (if the target computer does not have Internet access)
Install it on the target computer
Download available for Windows 2000 SP3 or later, Windows XP, Windows Server 2003:
Windows Installer 3.1 (v2) Redistr

Installing a Hach WIMS Indirect Server-Side Interface from an MSI file

Gavin Schmidt — Tue, 09 Mar 2010 03:10:26 GMT

Abstract:

The MSI file is much like the ISO image with two main exceptions:

You do not 'mount' the MSI image, just double click it

It does NOT include the prerequisites that the ISO image installs, therefore you must have the following already installed:

.NET 2.0 Framework

Microsoft Windows Installer 3.0 (See article Q12918)
Microsoft Security Update MS04-011

Once you have downloaded the MSI image, double click it and you will see the following screen:

(NOTE: If you have a previous version of this already install, step through the screens to Remove the old version first)

Now you can continue installation with the next screen being the EULA, the same as if you are installing from ISO image (see kb article Q12520)

OPS SQL (MS SQL) SQL Statement/Query Examples

Les Poyner — Mon, 08 Mar 2010 08:00:31 GMT

Abstract:

OPS SQL supports the ability to run SQL Statements (i.e. Select queries, update statements) using the SQL Console. To use the SQL Console you must be a Super User (or a Manager with the "Allowed to run SQL Console (if Manager):" User Setting checked).

To use the SQL Console:

Go to System Setup, Admin Console, Action Scripts Tab and click execute on the following line: Execute custom SQL commands against the current database. Experienced users only!

You will be presented with a window that allows you to execute SQL Statements directly against the database.

Examples:

1. Update using the REPLACE function:

Fix the Description field in the Vardesc table by replacing the single quote ( ' ), char(39) with `:
Update Vardesc Set Description = replace(description,Char(39),’`’)
Replace 'Influent' with 'Raw'
Update Vardesc set name = Replace(name, 'Influent', 'Raw')

Supported Source Field Identifiers for Q12211

Les Poyner — Mon, 08 Mar 2010 03:15:36 GMT

Abstract:

Hach WIMS Direct Server-Side Interface to Perkin Elmer Labworks LIMS supports reading of the following fields from PE Labworks Database :

SAMPLE.SAMPNO : Sample Number from SAMPLE table
SAMPLE.COLDATE : Sample Collection Date from SAMPLE table
SAMPLE.LOCCODE : Sample LOCCODE from SAMPLE table
RESULT.ACODE : ACODE from RESULT table
RESULT.ANALYTE : ANALYTE from RESULT table
RESULT.RESULT : RESULT from RESULT table
RESULT.RESULT2 : RESULT2 from RESULT table
RESULT.RLTUNIT : RTLUNIT from RESULT table
RESULT.QUALIFY : QUALIFY from RESULT table
VALIDATION: From either ANALYSIS.AVALUSER or SAMPLE.VALUSER, depending on the setting Verify result validation type under Configuration -> Source Configuration -> Advanced Settings. See article Configuration - Source Configuration Q12211 for more information.

Create a New field:

Now run the interface and navigate to Configuration -> Advanced Configuration -> Additional Info tab and click the Configure Additional Info button.

Database Name - name of the database instance.

Username - The username you want to use to connect to the database. This user should have permission to access the database and tables that contain data.

Password - The password associated with the Username and is used to connect to the database.

Advanced Configuration - these permit adjustment of the command and connection timeout.

Connection Timeout in Seconds - how many seconds the program s

Using Interface Browser Q12231

Les Poyner — Mon, 08 Mar 2010 02:46:18 GMT

Abstract:

Using the interface browser for Hach WIMS Direct Server-Side Interface to Perkin Elmer Labworks LIMS.

Step 1: It is important to ensure connectivity with the Labworks source database. If Labworks is on the same machine as this interface, then the browser can connect. If Labworksis on another machine, make sure it is possible to connect from the Hach WIMS machine to the Labworks.

Step 2: The browser connection must be properly configured in the Hach WIMS client:

Select System Tables -> Entire System -> Server-Side Interface Setup.

First, click the New Definition button to upload the definition file, the file name is: 12211.g2_server_lu
Second, add a New instance of this interface by selecting New.

To create a new entry:

Click New
Enter: the Name of Interface, Description, and select a Collector Time Zone.
Click on the Browser tab
Enter the Labworks Connection String, database Type, and Owner:

Here are some sample connection strings:

Interface Introduction

Les Poyner — Mon, 08 Mar 2010 02:23:47 GMT

Abstract:

The Hach WIMS Direct Server-Side Interface to OPC HDA imports summarized values into Hach WIMS from a standard OPC HDA Server (see http://www.OPCFoundation.org for more information about OPC HDA).

This interface can be used with EMERSON Process Management, Delta V SCADA system with an OPC HDA Server. Historically, we have had to install the interface on the Delta V system and push data to the Hach WIMS client using either Microsoft or Oracle OLEDB connection. More information about Delta V Systems can be found at http://www2.EmersonProcess.com.

This Interface can be used with ICONICS, TrendWorX (which is an OPC HDA Server) with one exception: TrendWorX does not allow OPC HDA Item browsing with the WtHDAClient.dll that the Interface uses (see article 12279). Instead, the first Tag is repeated over and over if you try to browse the Tags. The Interface will still work, you just won't be able to use the Tag Browser in Hach WIMS Client. To get around this issue a new utility was created, TWX2OPSXML. This utility reads in an ICONICS TrendWorX Data Logger XML Configuration file and exports an OPSDATAXML file that can by used by the browser (see article 12281).

Software Requirements Specific to Q12260

Les Poyner — Mon, 08 Mar 2010 02:23:37 GMT

Abstract:

This interface has unique system requirements in order to run correctly. Whenever possible, it is best to install this interface on the same computer where the OPC Historian (OPC HDA) is running. Please note the following.

The interface has WtHDAClient.dll library included with it, this dynamic linked library should be located in the same folder as the application. The Interface uses the WtHDAClient.dll to communicate with an OPC HDA Server.

In order for this interface to run, OPCENUM must be running as a service and OPCDAAUTO.DLL must be properly installed. Both OPC components can be downloaded from the OPC Core Components at the OPC Foundation: http://www.opcfoundation.org/SiteMap.aspx?MID=Downloads. Click on the Redistributables link. You must have a user login with the foundation to download files.

Supported Variable Configurations for Interface Q12211

Les Poyner — Mon, 08 Mar 2010 01:55:23 GMT

Abstract:

Supported variable configurations for the Hach WIMS Direct Server-Side Interface to Perkin Elmer Labworks LIMS.

To configure a variable to hold values from Aspen LIMS, select Edit/View Variables in the client and select the Interface tab.

Then click Interface To radio button. The drop down box next to the option is now enabled, click the drop down arrow and choose the Labworks interface name (name given when configuring the interface).

The Sample.LocCode and Analysis.ACode must be entered, the Analytes.AlnName field is optional. An explanation to properly configure these three fields can be found under Supported Variable Configurations for Interface Q12211 - Advanced Settings.

Which Result Field to Import From - valid values are: RESULT, RESULT2, and RAWRESULT. If field is left blank, the default RESULT will be used. In the Perkin Elmer Labworks database, there are three fields that contain results. These are reflected here. This is an example of values from those three fields:

NOTE: Not all Labworks database have the RAWRESULT field depending on your Labworks configuration/version. If the RAWRESULT field is not a field in your database, please set the RESULT.RAWRESULT field in Source Configuration to Does Not Exist.

Import Unvalida

Supported Variable Configurations for Interface Q12211 - Advanced Settings

Les Poyner — Fri, 05 Mar 2010 08:22:41 GMT
Abstract:
The section Supported Variable Configurations for Interface Q12211 explained the basics of setting up a variable. This section will go into more details on what is acceptable for configuring a variable to handle data from Perkin Elmer Labworks database.
There are three possible use cases for importing values from Perkin Elmer Labworks into Hach WIMS Client:
Case 1: Single test sample, this uses Sample.LocCode and Analysis.ACode only as demonstrated in the variable setup below.
In this example we do not specify the Analytes.AlnName, our value comes from RESULTS field, and we want values whether validated or not.

Case 2: Result from a series of tests, this uses Sample.LocCode, Analysis.ACode, and Analytes.AlnName to identify our data point, as shown below.
In this example we have a series of tests defined in $IC. This variable is configured to receive the Nitrate value from the $IC series. Shown below is a snapshot from the Perkin Elmer database for ACODE=$IC. We can see this series has six (6) tests, one of which is Nitrate. This is the value we want returned, so we will get 20.3 for Nitrate.

Hach WIMS Client will report just the Nitrate values:

Release Notes for Interface Q12211

Les Poyner — Fri, 05 Mar 2010 08:12:28 GMT
Abstract:
Hach WIMS Direct Server-Side Interface to Perkin Elmer Labworks LIMS (Q12211)
Version 1.0.4 (Build 84, Released on 3/5/2010)
Updated LIMS2OPSSQL Common Framework to Build 24
Fixed issue with the browser sometimes returning a CAS# for the AlnName (Fortress item 3479)
Changed Source Configuration to correlate to the Source Data terminology (Fortress item 3480)
Changed multiple selection method to be the same as other similar objects in Hach WIMS Client (Fortress item 2741)
Version 1.0.3 (Build 79, Released on 11/9/2009)
Fixed version error (Fortress item 3122)
Fixed importing values from ACodes with multiple tests (Fortress item 3131)
Fixed problem with importing values and getting error message "Subscript out of Range" (Fortress item 3133 - Note: Unable to dupllicate error, but narrowed problem down to the LIMS_UD2 field being blank instead of null. If problem persists, set the Which Result Field to Import From = RESULT in Hach WIMS client, Variable Setup)
Browser - removed feature that selects value on double click, now double click does nothing. Selection is done by clicking on values, for multiple values there is no need to hold any key down, just simply click the options needed. Click again to de-select (Fortress item -3122)
Version 1.0.2 (Build 78, Released on 10/22/2009)
Upgraded interface to Common Framework Build 85
Version 1.0.1 (Build 73, Released on 10/16/2009)
Included bug fixes and feature additions from common framework build 83, and LIMS2OPSSQL type build 19
Added support for importing of these source fields and writing them as Hach WIMS additional info fields
Added "View Applied Conne

Release Notes for LIMS2OPSSQL Type of Hach WIMS Direct Server-Side Interface

Les Poyner — Fri, 05 Mar 2010 08:06:53 GMT
Abstract:
Build 24
Added to framework ability to configure LIMS Interface for a LIMS_LOC and several LIMS_TEST with LIMS_UD1 blank (3478)
Corrected issue with Limit-To-List, when checked, so that if the text value is not in the list, the value is written to comments (3482)
Build 20
Added internal structures needed to ignore case when evaluating the cross reference map from the source system to Hach WIMS (2990)
Added internal structures needed to show results of "View Applied Connection String" from interface's Source Configuration form (2821)
Text Paramater Variables with Limit To List are now properly written based on the current list configuration of each variable (2805)
Hach WIMS Comment writter implemented (2983)
Fixed a bug that caused interface import session to break when a result with an unexpected number of spaces was returned by the source system (3083)
Fixed a bug that caused interfaces to write data according to MDL rules when if Allow Symbol was false (3086)
Fixed a bug that caused overflow during reporting of statistics for import sessions that lasted less than 1 second (3024)
Build 7
Initial Release to Public

Database Server Hardware Requirements for WIMS Pro and Enterprise

Scott Dorner — Thu, 04 Mar 2010 03:13:00 GMT
Abstract:
Hach WIMS Pro and Enterprise supports Oracle or MS SQL server database management systems. See Software Requirements for supported versions. Hardware requirements for the database server are set by the database management system's requirements. Hardware recommendations are dependent on operating system, number of users, amount of data being tracked, other applications using the same database server, etc and are difficult to quantify. However, the general rule is the more RAM, number of CPUs, CPU speed, and disk space the better as budgets allow.
The following links are provided from the Oracle and Micorsoft sites for your information:
Hardware and Software Requirements for Installing SQL Server 2005
Hardware and Software Requirements for Installing SQL Server 2008
Oracle9i Database Installation Guide Release 2 (9.2.0.2.1) for 64-Bit Windows
Oracle9i Database Installation Guide Release 2 (9.2.0.1.0) for Windows

See Also:
How fast does the WIMS (OPS SQL) database grow based on the number of points I track?
Hach WIMS Architecture
Hardware Requirements for Hach WIMS Client 7.x.x

Symbol MC50 Spec for WIMS Portable

Scott Dorner — Wed, 03 Mar 2010 05:18:19 GMT
Abstract:

2D IMAGER ENGINE

Aiming element (VLD)

650 nm +/- 5 nm

Field of View

32.2° (Horizontal); 24.5° (Vertical)

Focal distance from front of engine

5 inches (Near); 9 inches (Far)

Illumination element (LED)

635 nm +/- 20 nm

Image file formats

BMP, TIFF, JPEG

Minimum print contrast

Minimum 25% absolute dark/light reflectance measured at 650 nm; 35% MRD measured at 675 nm

Optical resolution (gray scale)

640 (Horizontal) x 480 (Vertical) pixels

Pitch angle

+/- 60° from normal; +/- 50° from normal

Roll

360°; +/- 20° from vertical

License Tab under System Information

Find your Hach WIMS Serial Number

Michael Bynum — Tue, 02 Mar 2010 07:34:59 GMT

Abstract:

There are 3 Methods to finding your serial number.

Method 1:

Launch Hach WIMS.
From the Logon Screen, double click "System Info..." in the bottom right corner.
Clicke the License Tab at the Top.
Your Serial Number is located in the top box.

Method 2:

From inside the Client go to Help->About Hach WIMS
Your Serial is located under License Information:

Method 3:

From the Client go to Utilities->System Information

Clicke the License Tab at the Top.

Your Serial Number is located in the top box.

Supported variable configurations for interface Q12705

Les Poyner — Tue, 02 Mar 2010 07:27:14 GMT

Abstract: Supported variable configurations for the Hach WIMS Indirect Server-Side Interface to WonderWare Historian (InSQL).

To configure a variable to hold values from the source data, select Edit/View Variables in the Hach WIMS client and select the Interface tab.

Then click Interface To radio button. The drop down box next to the option is now enabled, click the drop down arrow and choose the interface name (name given when configuring the interface).

Now you are ready to configure a signal tag to the source data. The Tag name and a Statistic are all that are mandatory.

This is the history table followed by the tag found in the source data. The table name is needed because it is possible to have the same tag name in multiple tables.

This is a listing of all the statistics supported by this interface. This includes the following statistics for a specified time period.

Using Inteface Browser Q12737

Les Poyner — Tue, 02 Mar 2010 07:23:41 GMT

Abstract:

Using the interface browser for Hach WIMS Indirect Server-Side Interface to WonderWare Historian (Formerly InSQL).

Step 1: In the Hach WIMS client, select Edit/View Variables and click the Interface tab.

Step 2: The browser connection must be properly configured. In the Hach WIMS client:

Select System Tables -> Entire System -> Server-Side Interface Setup.

Select the Edit button for the interface entry that you want to enable the browser for.

Click on the Browser tab and enter the location of an OPSDATAXML file generated by the Collector. The browser will search this file for the available Tag Names. Make sure Browser Enabled is checked and click OK button.

You are ready to view tags from the HMI. Click on System Setup -> View/Edit Variables and click on the Interface tab.

Click the button with a ? (question mark) on it as shown below:

The browser will load:

Select the appropriate Source Tag and click OK.

Using Inteface Browser Q12826

Les Poyner — Tue, 02 Mar 2010 07:22:52 GMT

Abstract:

Using the interface browser for Hach WIMS Indirect Server-Side Interface to Rockwell RSView32.

Step 1: In the Hach WIMS client, select Edit/View Variables and click the Interface tab.

Step 2: The browser connection must be properly configured. In the Hach WIMS client:

Select System Tables -> Entire System -> Server-Side Interface Setup.

Select the Edit button for the interface entry that you want to enable the browser for.

Click on the Browser tab and enter the location of an OPSDATAXML file generated by the Collector. The browser will search this file for the available Tag Names. Make sure Browser Enabled is checked and click OK button.

You are ready to view tags from the HMI. Click on System Setup -> View/Edit Variables and click on the Interface tab.

Click the button with a ? (question mark) on it as shown below:

The browser will load:

Select the appropriate Source Tag and click OK.

Configuration - Source Configuration Q12535

Les Poyner — Tue, 02 Mar 2010 07:20:49 GMT

Abstract:

To configure your source connection to the OPSDATAXML files generated by the Hach WIMS Rockwell RSView32 Collector (Q12528):

Open Source Configuration.

Set the folder location of the OPSDATAXML files to import.

Supported variable configurations for interface Q12535

Les Poyner — Tue, 02 Mar 2010 07:15:50 GMT

Abstract: Supported variable configurations for the Hach WIMS Indirect Server-Side Interface to Rockwell RSView32.

To configure a variable to hold values from the source data, select Edit/View Variables in the Hach WIMS client and select the Interface tab.

Then click Interface To radio button. The drop down box next to the option is now enabled, click the drop down arrow and choose the appropriate interface name (name given when configuring the interface).

Now you are ready to configure a signal tag to the source data. The Tag name and a Statistic are all that are mandatory.

This is the node followed by a colon and then tag name found in the source data.

This is a listing of all the statistics supported by this interface. This includes the following statistics for a specified time period.

AVERAGE	Take the average of the data points
TOTAL	Take the sum total of all values

Release notes for interface Q12535

Les Poyner — Tue, 02 Mar 2010 06:54:53 GMT

Abstract:

Version 1.0.0 (Build 16, Released on 3/2/2010)

Initial release for distribution.

Using the Rockwell RSView32 Collector (Q12528)

Les Poyner — Tue, 02 Mar 2010 06:44:00 GMT

Abstract:

Using the Hach WIMS Rockwell RSView32 Collector to convert Historical data into OPSDATAXML files.

The Hach WIMS Indirect Server-Side Interface to Rockwell RSView32 does not communicate directly with the Rockwell RSView32 HMI. Instead, a collector will connect to the database and convert the SCADA source data into OPSDATAXML files. The Hach WIMS Indirect Server-Side Interface to Rockwell RSView32 will then import data in these files into the Hach WIMS Client.

In the default installation; the Interface, Collector and RSView32 dBase IV files reside on the same machine. You may also configure the Collector and RSView32 dBase IV files to be on the same machine but have the Interface on another machine. In the indirect configuration, make sure that the Collector's OPSDATAXML files are in a location that the Interface can access (i.e. a shared network drive).

To start the Collector from the Interface click on Configuration/Collector Configuration.

From here you can either configure the Collector or start it. Click on Collector Configuration Settings to configure the collector.

If you choose to start the Collector before it has been configured, you will be presented with a warning message indicating that it has not been configured yet. You can dismiss the message and proceed to configure the Collector.

The Collector will not start collecting data until it has been configured. In the configuration screen you have two tabs of configuration settings. The "General Settings" tab contains information on how you want the Collector to run.

Custom Collector Configuration for Collector Q12528

Les Poyner — Tue, 02 Mar 2010 06:38:55 GMT

Abstract:

The Collector will not start collecting data until it has been configured. In the configuration screen you have three tabs of configuration settings. The "General Settings" tab contains information on how you want the Collector to run.

Control Buttons at the top:

Apply Settings: Applies the settings selected for all tabs
Close: Closes the Window without applying settings
Note: Once the interface has been configured, click Apply Settings and Close. The next screen will allow you to save settings

Configure Source Data - Use this screen to configure the Collector's connection to the Rockwell RSView32 dBase IV source data.

RSView32 Data Folder -Main folder that may contain data files (dBase IV) or additional folders (referred to as "Nodes"). The additional folders will contain the dBase IV files
RSView32 Node Folder with Source File - Drop down list of all folders under the main folder
User ID - optional, used in order to connect to the source data using Microsoft Jet
Password - optional, used in addition to the User ID, to connect to source data
Time Zone Offset - optional, if Data Source Uses UTC Times is unchecked, need to enter UTC offset here
Connection Timeout - enter number of seconds to timeout from trying to connect to source
Comman Timeout - enter number of seconds to timeout when querying data from sou

Relase notes for collector Q12528

Les Poyner — Tue, 02 Mar 2010 04:26:35 GMT

Abstract:

Version 1.0.0 (Build 18, Released on 3/2/2010)

Initial release for distribution.

Source data explained

Les Poyner — Tue, 02 Mar 2010 04:22:19 GMT

Abstract:

The Rockwell Automation RSView32 source data tested where in dBase IV files with long and short file names. The files are in pairs; one contains the tag names and indexes and are identified by "Tagname" or "T", and the other file pair contain data and are identified with "Wide" or "W".

A long file name for tags looks like: 2009 07 01 0000 (Tagname).DBF and would be the same in short form as 090702AT.DBF

A long file name for data (WIDE) looks like: 2009 07 01 0000 (Wide).DBF and would be the same in short form as 090702AW.DBF

The Hach WIMS Indirect Server-Side Interface to Rockwell RSView32 connects to these files using the Microsoft Jet OLEDB driver. In order to connect to these files, Microsoft Jet requires the file names to be in the short format. All data files are copied to a folder under the Hach WIMS interface application and renamed to the short format if necessary. Here is an example of a connection to Microsoft Jet:

Provider=Microsoft.Jet.OLEDB.4.0;Data Source=C:\Data\EMC-WWTP;Extended Properties=dBASE IV;User ID=Admin;Password=;OLE DB Services =-2;

The main data point for dBase IV files is C:\Data and our node is EMC-WWTP. The node is a feature in Rockwell RSView32 that allows various tags to be collected in different folders under the main data point. So, in our example we might have EMC-WWTP, EMC-WWTP-02, and EMC-WWTP-03. We might have the same tag name under each node because the tag name pertains to a specific device in different locations.

Both Tagname and Wide files are need to gather data. The Tagname file tells us the index of that tag. The Wide file contains data in a wide format, columns correlate to the tag index. For example:

We want to get data for the t

Interface Introduction

Les Poyner — Tue, 02 Mar 2010 03:36:50 GMT

Abstract:

The Hach WIMS Indirect Server-Side Interface to Rockwell RSView32 imports summarized values into Hach WIMS. The interface imports summarized values from dBase IV files created by Rockwell Automation's RSView32 HMI system. Here is a snapshot of their product demo:

To find more information about Rockwell Automation, visit their website at http://www.rockwellautomation.com/rockwellsoftware/performance/view32/

Monthly Data Entry Design - Error 3021 BOF or EOF is True

Michael Bynum — Mon, 01 Mar 2010 04:51:42 GMT

Abstract:

Issue Symptoms:

The Symptoms of this issue occure when you go to Design->Monthly Data Entry Design. You are presented with the error. When you push ok, you are presented with a normal design screen except the Form Name is txtFormName. You are able to add new MDE forms and edit them but pushing any button on the form gives you this error.

This issue generally happens right after upgrading from OPS32.

Solution:

This error is a little misleading. The Record Set that it is looking at is not the Monthly Data Entry Records. It's actually Looking at the Location Records. To fix the error simply add a record under System Setup-> Location Setup.

Error trying to browse SQL Server with the Object Explorer in MS SQL Server Management Studio.

Doug Schultz — Fri, 26 Feb 2010 04:49:28 GMT

Abstract:

Problem:

You get the following error when trying to browse SQL Server with the Object Explorer in MS SQL Server Management Studio:

Unable to cast COM object of type 'System.__ComObject' to interface type 'Microsoft.VisualStudio.OLE.Interop.IServiceProvider'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{6D5140C1-7436-11CE-8034-00AA006009FA}' failed due to the following error: No such interface supported (Exception from HRESULT: 0x80004002 (E_NOINTERFACE)).

Solution:

There are many possible solutions to this problem.

The first thing to try is to unregister and then re-register two dll's and then reboot.

1. Re-register ieproxy.dll:

regsvr32 /u "C:\program files\internet explorer\ieproxy.dll"

regsvr32 "C:\program files\internet explorer\ieproxy.dll"

For windows 7 Replace the 2 lines above with the following 2 lines.

regsvr32 /u "C:\program files (x86)\internet explorer\ieproxy.dll"

regsvr32 "C:\program files (x86)\internet explorer\ieproxy.dll"

2. Re-register actxprxy.dll:

regsvr32 /u "C:\windows\system32\actxprxy.dll"

regsvr32 "C:\windows\system32\actxprxy.dll"

3. Reboot your computer.

If this doesn't solve the problem, here are a few useful links.

http://social.msdn.microsoft.com/Forums/en-US/sqltools/thread/d5d3e5fc-d8ce-4f42-b7ea-9bbbb7756a20

http://support.sourcegear.com/viewtopic.php?f=5&t=12680&p=52790&hilit=management+studio#p52790

Why upgrade to WIMS/OPS SQL?

Scott Dorner — Fri, 26 Feb 2010 01:15:23 GMT

Abstract:

Do I have to upgrade to Hach WIMS/OPS SQL ?

No. However, if you are looking for a long term solution, we strongly advise you upgrade to Hach WIMS (previously OPS SQL) so that you can keep up with the most current changes in EPA regulations, electronic reporting formats, etc. As you upgrade your hardware you might find the OPS 32 with the MSAccess database will not be compatible with the new hardware and OS structures (such as Vista), then you will need to upgrade to an appropriate edition of Hach WIMS. Eventually, the OPS 32 software will be phased out as new machines will not be able to run it. Until that time Hach will continue to provide technical support; however, we will not be adding any new features, we will only be fixing bugs.

What is the benefit to upgrade to Hach WIMS?

The benefit to upgrading your system is having the latest features and functions within a more robust and stable database platform. Along with the superior architecture of WIMS with native utilization of Microsoft SQL Server including stored procedures, triggers, and tuned indexes, some of the new, powerful, features of WIMS include:

Meeting your Electronic Reporting Requirements (eDMRs)
Audit Trail for a complete record as to who and when data is entered, changed or deleted.
More Variable Types: one minute, five minute, fifteen minute, one hour, four hours and daily.
Time Stamped Data & Events
Design and control Multiple Logbooks assigned to individuals or groups
Events can be recorded providing tools for inspection logs, Industrial Pretreatment and more

The needs and requests of our customers are always a high priority however; the answer to some requests MIGHT be to upgrade your software to an appropriate Edition of WIMS. We have done our best to make this upgrade as painless as

How fast does the WIMS (OPS SQL) database grow based on the number of points I track?

Scott Dorner — Thu, 25 Feb 2010 07:53:11 GMT

Abstract:

It has been determined that it takes on average between 130 (on the low end) to 200 (on the high end) Bytes of actual disk space required to store 1 row of data (WIMS datapoint). Each datapoint write transaction also generates 1 row of audit trail of approximately the same size. Where your system falls between the high end and low end is determined by lots of factors, which include disk allocation unit size, density of text-data, and density of index.

To calculate an "estimate" of how fast your database will grow, follow this example :

Everyday, I store 96 datapoints for 100 variables (these would be 15 minute variables), plus about another 400 datapoints for misc variables. Therefore, I store about 10,000 (96 *100 +400) data points a day.

Storage required to store 10000 data points:

[low end] = 2 * (10000 * 130 Bytes) = 2 * 1300000 Bytes ~ 2 * 1.24 Megabytes ~ 2.5 Megabytes
[high end] = 2 * (10000 * 200 Bytes) = 2 * 2000000 Bytes ~ 2 * 1.91 Megabytes ~ 3.8 Megabytes

Your daily storage requirement is going fall somewhere between high end and low end numbers above.

If your maximum database size limit is 2 GB , it will take approximately :

[low end] 820 days to fill up the database
[high end] 540 days to fill up the database

NOTE : Empirical measurement tool as seen in article :

Michael Bynum — Wed, 24 Feb 2010 10:07:29 GMT

Abstract:

While installing the Hach WIMS DBMS (MS SQL Server 2005 Express) component from your Hach WIMS DVD on a Windows Server (2003 or 2008) environment you might get the following error message:

This is because the default local password policy is preventing the installer from setting the SA user's password.

You can temporarily disable this policy while the installation is running and hit the "Retry" button to let the installation complete successfully. After installation is finished, you can restore the policy to the desired setting:

Note:

If the setting is set on a domain controller you may need to run GPUdate to force the changes to propigate.

New Hampshire Drinking Water Report Templates - In Progress

Scott Dorner — Wed, 24 Feb 2010 08:37:17 GMT

Abstract:

NH_DW_MOR_Filtered_Surface_Water_Systems.hwr NH MOR for Filtered Surface Water System: Preview

New Hampshire Department of Environmental Services Monthly Operating Report for Filtered Surface Water Systems
MWY 02/23/2010

Click here for instructions on downloading a template.

Hach LAB Cal Datasheet

Gavin Schmidt — Wed, 24 Feb 2010 05:31:55 GMT

Abstract:

(Click thumbnail above to view / download datasheet)

Description:

Hach LAB Cal Datasheet

Cost Effective Sample Scheduling and Tracking

PLEASE NOTE: To read this datasheet, you must have Adobe Reader installed on your computer.

If you do not have Adobe Reader, you can download it for free from www.adobe.com

Hach BOD Manager Datasheet

Gavin Schmidt — Wed, 24 Feb 2010 05:29:46 GMT

Abstract:

(Click thumbnail above to view / download datasheet)

Description:

This datasheet outlines the Hach BOD Manager features and capabilities

PLEASE NOTE: To read this datasheet, you must have Adobe Reader installed on your computer.If you do not have Adobe Reader, you can download it for free from www.adobe.com

Hach WIMS General Brochure

Gavin Schmidt — Wed, 24 Feb 2010 05:29:18 GMT

Abstract:

(Click thumbnail above to view / download datasheet)

Description:

General information on Hach Water Information Management(TM) (Hach WIMS)

PLEASE NOTE: To read this datasheet, you must have Adobe Reader installed on your computer.

If you do not have Adobe Reader, you can download it for free from www.adobe.com

NDM

Doug Schultz — Tue, 23 Feb 2010 09:21:46 GMT

Abstract:

NDM returns the Number of Days in a Month

SYNTAX:

NDM(MonthOffset)

MonthOffset: The Zero based offset from the Start Date of the report or a date string. Common values:
0 = Current month
1 = One month after current month
2 = Two months after current month

EXAMPLES:

Start Date of Report is 02/01/2010

AVERAGE	Take the average of the data points
TOTAL	Take the sum total of all values
MINIMUM

Formula	Returns	Explanation
NDM(-1)	31	1 month before start of report is January 2010 which has 31 days.
NDM(0)	28	Current month is Feb 2010 which has 28 days.
NDM(1)	31	1 month after start of report is March 2010 which has 31 days.
NDM("6/25/2010")	30	June 2010 has 30 days.

Vermont Wastewater Spread Report Templates

Scott Dorner — Tue, 23 Feb 2010 06:17:06 GMT

Abstract:

VT_WW_Large_Act_Sldg_WWTF.hwr TCEQ DLQOR : Preview

VERMONT WASTEWATER PERMIT PROGRAM OPERATIONS REPORT FOR LARGE ACTIVATED SLUDGE WASTEWATER TREATMENT FACILITIES (WR-43 Report)
Author: SPD 01/14/2010

NOTES:

See Download Report Template for detailed instructions on how to download templates.

Preview of Hach WIMS 7 release

Scott Dorner — Mon, 22 Feb 2010 04:26:44 GMT

Abstract:

Preview of upcoming WIMS 7 release

Where: 2008 OPS SQL User's Conference
Date: September 30, 2008
Presenter: Scott Dorner, OPS Systems
Presentation Material: WIMS7_NewFeatures.ppt
NOTE: The video shows the new features in Hach WIMS (AKA OPS SQL 7.0) that were added since OPS SQL version 6.x. In the video, WIMS is referred to as OPS SQL 7.

Compliance Engine
New Help System
Multi-Sheet Reports

8 minutes 45 seconds OPS.TV Video Cast

V6001 = SKIP

NOTES:

Skip is typically used to hold values historically. For example, a parameter variable is input for 3 years, on Jan 15th, 2010 we start to calculate the value but we do not want the calc engine to overwrite the values we have input. We can setup historical equations utilizing SKIP to hold the values:

Historical Equations

Scott Dorner — Thu, 18 Feb 2010 07:59:35 GMT

Abstract:

Edit/View Variables - Historical equations are used to change the equation (formula) for a variable based on the date.

For example, V10 should be V1 + V2 starting on 1/1/2000 and V1 - V2 before 1/1/2000. If the equation for V10 is simply changed to V1 + V2 you could never calculate data before 1/1/2000 without destroying the data in V10. By using historical equations, when V10 is calculated, it will always calculate using the equation specified for the time frame.

Entering Historical Equations

In Variable Edit, on the equation tab, click the button. If no historical equations have been entered for the current variable, the current equation will automatically be added as the first historical equation with a start date of 1/1/1980. Click Add New and select the new Equation Start Date (i.e. 1/1/2000). Enter the new equation (V1 + V2) and Exit. WIMS will now use the equation V1- V2 before 1/1/2000 and V1 + V2 on or after 1/1/2000. A variable can have an unlimited number of historical equations.

Tip: Use the SKIP f

Release notes for interface Q12180

Les Poyner — Thu, 18 Feb 2010 02:46:41 GMT

Abstract:

Hach WIMS Direct Server-Side Interface to Wonderware Historian (InSQL)

Version 1.0.8 (Build 74, Released on 2/18/2010)

Removed testing code and repackaged

Version 1.0.7 (Build 71, Released on 2/8/2010)

Upgraded interface to SCADA2OPSSQL Framework Build 47

Version 1.0.6 (Build 62, Released on 10/21/2009)

Upgraded interface to Common Framework Build 85

Version 1.0.5 (Build 46, Released on 9/10/2009)

Fixed queries added in 1.0.4 that were failing (FIRST, LAST, DIFF)

Version 1.0.4 (Build 45, Released on 9/9/2009)

Fixed query to apply low range and high range filtering

Version 1.0.3 (Build 38, Released on 6/18/2009)

Added to query " wwRetrievalMode='Cyclic' AND wwRowCount = '1440' " (where 1440 is number of minutes between start and end date/time

Version 1.0.2 (Build 35, Released on 6/12/2009)

Fixed problem with trying to connect to large source systems
Changed browser, added "TAG" table to options for listing tag names

Version 1.0.1 (Build 22, Released on 5/12/2009)

Initial release

Configuration - Automated Import Configuration

Jan Bob — Wed, 17 Feb 2010 07:13:58 GMT

Abstract:

Each interface can be configured to run as a service. This is when you want to schedule an automatic retreival of data, without user intervention.

The Automated Import Configuration screen allows you to configure the schedule, whether to submit calculation requests, the Last-Ran Date, and the import operation mode:

Automated Import Schedule - configure when the interface service is scheduled to run:

Daily -the interface will run ONCE per day, at the specified schedule. E.g., to run it at 2:30 am, you would enter "2" into the hours box and "30" into the minutes box. Note that time is entered in "military" format. To enter 4:45 pm, you would enter "16" into the hours box, NOT 4.
Hourly - the interface will run every hour at the specified minute after the hour
Minutely- the interface will run every X minutes where X is a number between 1 and 1440. E.g., to run it every 5 minutes, you would enter "5".

Calculations After Automated Import - select this option if you would like the Hach WIMS AdoCalc service to recalculate all variables within every facility after an import operation completes.
Default Last Run Date - this is the point in time from which the interface service will try to retrieve data, up until the current point in time. After a successful run, the current time will become the last run time. By default, this is set to one day prior to the current day.

E.g., assume today is Fegruary 25, 2009, if you have just installed the interface and have 3 months of historical data you want imported into

Release notes for interface Q12695

Les Poyner — Wed, 17 Feb 2010 03:07:44 GMT

Abstract:

Hach WIMS Direct Server-Side Interface to Mettler Toledo OverDrive

Version 1.0.1 (Build 15, Released on 2/17/2010)

Fixed problem creating a specific Location that caused the program to error, and created a variable without a location (Item 51706)

Version 1.0.0 (Build 12, Released on 12/10/2009)

Initial release

SQRT function does not calculate correctly when cascade MDL rule is checked

Doug Schultz — Tue, 16 Feb 2010 10:05:01 GMT

Abstract:

There is a known issue when using the SQRT Function in a variable equation if the cascade MDL rule is also checked. The function is intended to report the square root of a number, however, in this case it returns the number itself, not the square root.

Symptoms:

Solution:

Instead of using SQRT(V4725) use SQRT(V4725+0)
If you use SQRT(C4725+0) and Variable 4725 is blank then 0 will be returned.

Ado Calc behaves erratically when a variable references a variable in a different database in which there are no calculated variables.

Jan Bob — Tue, 16 Feb 2010 09:16:35 GMT

Abstract:

Ado Calc (Hach WIMS Calculation Engine) behaves erratically when a variable references a variable in a different database in which there are no calculated variables.

Symptoms:

For example if Variable 1 in database OPSWWTUTOR is a calculated variable and it references Variable 6 in database OPSHRLAB then Variable 1's equation would be V1=V6@OPSHRLAB.
Now if you entered some data in January for V6 in OPSHRLAB and then went into a MDE (monthly data entry) form in OPSWWTUTOR that has V1 on it and brought up the month of January. Now if you click on the Calculate all variables button your data for V1 will not show up, click it a second time and then your data for V1 will show up. In some cases the first time you click on the Calculate button, your data for V1 will dissappear but then if you click it again your data for V1 will reappear.

Workaround:

If you are going to be referencing data in another database, make sure you create at least 1 variable in the 2nd database that has Calculated as its type. The equation can be simple (SKIP will do the trick).

Configuration - Source Configuration Q12695

Les Poyner — Mon, 15 Feb 2010 01:51:03 GMT

Abstract:

This is the source configuration screen for the Hach WIMS Direct Server-Side Interface to Mettler Toledo OverDrive.

In order to configure source connection from the interface, click Configuration and select Source Configuration.

The next screen will display parameters on two tabs. The first is Database Connection:

Configuration Template - one template is included in OverDrive interface; for MS SQL. These will fill in the most common values for the database connection.
DBMS Type - Select the Aspen LIMS system type from one of these:

Oracle
Microsoft SQL Server

OLE DB Provider - this will be filled in with Configuration Template and DBMS Type, and can be modified if needed.
Data Source - this field specifies, in loose terms, the "Database/Datasource server name" where your Aspen LIMS system is configured to store data.
Source Tables Owner - Owner or schema (Oracle) of the OverDrive database tables
Database Name - name of the database instance
Username - The username you want to use to connect to the database. This user should have permission to access the database and tables that contain data.
Password - The password associated with the Username and is used to connect to the database.
Advanced Configuration - these permit adjustment of the command and connection timeout.

Release notes for interface Q12839

Les Poyner — Fri, 12 Feb 2010 06:08:14 GMT
Abstract:
Version 1.0.2 (Build 16, Released on 2/12/2010)
- Fixed problem with interface not recognizing High Range and Low Range values (Fortress 3447)
Version 1.0.1 (Build 14, Released on 2/9/2010)
- Upgraded interface to SCADA2OPSSQL Framework Build 47
Version 1.0.0 (Build 9, Released on 1/22/2010)
- Initial release

OPS Systems Knowledge Base

Supported Source Field Identifiers for Q12916

Installing a Hach WIMS Indirect Server-Side Interface from an MSI file

OPS SQL (MS SQL) SQL Statement/Query Examples

Supported Source Field Identifiers for Q12211

Using Interface Browser Q12231

Interface Introduction

Software Requirements Specific to Q12260

Supported Variable Configurations for Interface Q12211

Supported Variable Configurations for Interface Q12211 - Advanced Settings

Release Notes for Interface Q12211

Release Notes for LIMS2OPSSQL Type of Hach WIMS Direct Server-Side Interface

Database Server Hardware Requirements for WIMS Pro and Enterprise

Symbol MC50 Spec for WIMS Portable

Find your Hach WIMS Serial Number

Supported variable configurations for interface Q12705

Using Inteface Browser Q12737

Using Inteface Browser Q12826

Configuration - Source Configuration Q12535

Supported variable configurations for interface Q12535

Release notes for interface Q12535

Using the Rockwell RSView32 Collector (Q12528)

Custom Collector Configuration for Collector Q12528

Relase notes for collector Q12528

Source data explained

Interface Introduction

Monthly Data Entry Design - Error 3021 BOF or EOF is True

Error trying to browse SQL Server with the Object Explorer in MS SQL Server Management Studio.

Why upgrade to WIMS/OPS SQL?

How fast does the WIMS (OPS SQL) database grow based on the number of points I track?

New Hampshire Drinking Water Report Templates - In Progress

Hach LAB Cal Datasheet

(Click thumbnail above to view / download datasheet)

Hach BOD Manager Datasheet

(Click thumbnail above to view / download datasheet)

Hach WIMS General Brochure

(Click thumbnail above to view / download datasheet)

NDM

Vermont Wastewater Spread Report Templates

Preview of Hach WIMS 7 release

Preview of upcoming WIMS 7 release

Historical Equations

Release notes for interface Q12180

Configuration - Automated Import Configuration

Release notes for interface Q12695

SQRT function does not calculate correctly when cascade MDL rule is checked

Ado Calc behaves erratically when a variable references a variable in a different database in which there are no calculated variables.

Configuration - Source Configuration Q12695

Release notes for interface Q12839