This describes technical issues for which there are no known resolutions.
When using the GainSeeker Charts module to display and refresh a Dashboard window that contains the Chart dashboard control, GainSeeker may eventually generate an "Out of Memory" error. If this happens, there are two options:
Close and re-open the GainSeeker Charts module to reset the memory.
Increase the maximum number of GDI objects for Windows, which increases the length of time that your dashboard can be displayed before the memory error occurs. To do this:
Back up the Windows Registry or create a Windows Restore Point.
Edit the Windows Registry and change the GDIProcessHandleQuota
setting.
This Registry setting is typically found in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\Windows
or HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Windows.
Its default value is 10000, but you can increase it to a maximum
of 65536.
After editing this registry setting, restart the computer.
When running GainSeeker in Citrix on dual monitors with high resolution, modules such as LaunchPad may generate an error message with Exception Text that includes "System.NullReferenceException: Object reference not set to an instance of an object. at System.Windows.Forms.DisplayInformation.get_BitsPerPixel()".
According to the Citrix user forum (https://discussions.citrix.com/topic/238555-dual-monitor-issue-and-red-x/), this appears to be caused by a Citrix failure to define a "primary screen" under the following set of conditions:
Running under seamless mode
Having a Citrix client using dual screen with primary screen set on the right
Having a cumulated resolution X colorDepth of client dual screen superior to the maximal video memory allowed on Citrix server per client (this prevents Citrix from considering client dual-screen as only one extra-wide screen)
Some GainSeeker users have been able to work around this issue by disconnecting the second monitor and reducing their display resolution.
When the PC Collect window is maximized, a portion of the window is obscured by the taskbar in Windows 8. This does not occur when you position the taskbar vertically on the right side of your monitor.
GainSeeker ignores the Chart background color setting on a Normal Probability Plot chart. The Plot background color setting is used instead to fill the entire chart window.
When a desktop is saved with charts set to use multiple relative date periods, fixed dates are used when the desktop reopens.
When editing DMS data from a data table in GainSeeker Charts, saving the data does not update some of the columns in the data table. Specifically, the NCO Cost and Sample Cost cells do not update. To update these cells, press F5 or select the Window, Refresh Family menu.
On some computers that have multiple Ethernet cards, GainSeeker may simultaneously use two licenses to run two or more GainSeeker applications that are open on a workstation. This can be easily resolved by using a specific System-wide setting. For more information, see GainSeeker Ties up two licenses on a workstation
When GainSeeker is running with an ODBC database (Oracle, Microsoft SQL Server or MySQL), the DNote table can be modified to increase the length of DMS Notes. The default length of a DMS note is 480 characters (columns S1 and S2 are each 240 characters). You may increase columns up to 952 characters each to increase the number of characters available for each note. The maximum combined size for the columns is 1904 characters. The database can be modified through administrative software or by using the ALTER TABLE command. GainSeeker will notice the new column sizes and adjust accordingly.
If you omit the comma before a numeric parameter in a template formula, you will not receive a syntax error and you will get unexpected results.
For example, using the incorrect syntax
GainSeeker sometimes reported "Error 40026: Invalid result set state for Update" or "Microsoft SQL Server driver failed to create a new buffer (sixth and final try). Please contact Microsoft for new or updated driver)”.
The chance of this error can be reduced by changing the value for Show time to to Hundredths of seconds in the Administration module.
A customer reported that with MDAC 2.8 and above, connection pooling is automatically enabled. This customer had some success in limiting the number of errors by turning off the connection pooling. To turn it off, follow these steps:
From the Windows Control Panel, run the ODBC administrator.
Click on the Connection Pooling tab.
Find the driver that you are using, such as "SQL Server", and double-click it.
On the Set Connection Pooling Attributes screen, select Don't pool connections to this driver and click OK.
In GainSeeker version 7.5 we have also changed the way we error-trap this problem and have successfully run tests where the error will no longer occur.
Terminal Services on Microsoft Windows Server 2003 now supports RS-232 access to the serial port on the client PC. However, entering data via RS-232 in GainSeeker with the initial release of Microsoft Windows Server 2003 produced the error message "Run-time error '8020': Error reading comm device". Microsoft has released a hotfix for Windows Server 2003 and plans to incorporate this hotfix into a future service pack for Windows Server 2003. More information is available from Microsoft Support Knowledge Base article 838291 at support.microsoft.com/kb/838291.
Because of the third-party components used for sending email from GainSeeker, sending two emails in rapid succession sometimes results in the second email not being sent. To avoid this situation, you should insert a DELAY command between the two EMAIL commands. Typically, DELAY 1 is sufficient, although DELAY 3 is safer.
GainSeeker does not support duplicate defect descriptions in the Defect Management System. GainSeeker no longer allows duplicate defects to be entered. If multiple defects use the same name, GainSeeker may return unexpected results.
When using a previous version of GainSeeker with a Cms.ini that was modified by GainSeeker 7.5 or higher, the third line of the chart titles may display the title "^^888". Close the Charts and Reports module, remove the line title_3_spc=^^888 or title_3_dms=^^888 from Cms.ini and save the changes, and then launch the Charts and Reports module again. Upgrading your entire system to GainSeeker 7.5 or higher will also resolve this issue.
When using the legacy SQL Utility module (SQLUtil.exe)
in Freeform SQL mode or Execute SQL Command mode to manipulate data
in a SQL Server database, a query containing the ORDER BY clause on
a field that is not an index sometimes generates the error message
"01S02: [Microsoft][ODBC SQL Server Driver]Cursor type changed".
The SQL Utility has been modified in GainSeeker 7.401 to correct for
this error, but this error may still occur in some cases. If
you continue to receive this error when querying a SQL Server database
through the SQL Utility, then you should use one of the SQL Server
query tools to query the database instead of using SQL Utility.
In previous versions of GainSeeker running on an Oracle database, when using the SPC Data Entry module, a subgroup entered that was equal to one of the specifications might show as red on the air gage. This happens because of rounding errors when retrieving the specifications from an Oracle database. Some software modifications have been made to try and check for the rounding errors but may not work in all cases.
There is an incompatibility problem with some OLE Automation files. Newer versions of the Window Operating System files can cause the DMS tab not to load correctly in SPC Data Entry. To solve this problem, use the OLE Automation files shipped with the GainSeeker Suite. Those files are located in the SYSTEM folder under the GainSeeker installation folder. The following files are shipped with the GainSeeker Suite and known to work correctly
STDOLE2.TLB version 2.40.4275
ASYCFILT.DLL version 2.40.4514
OLEAUT32.DLL version 2.40.4514
OLEPRO32.DLL version 5.0.4514
The 'Check for Tables' function on the File Paths dialog and the Table Creation utility sometimes report that the 'Index for DData' does not exist when it does. To verify that the index exists for the DData table in Oracle or MS SQL Server, check with your DBA or look at the Indexes section with Enterprise Manager. For Pervasive/Btrieve databases, use the Pervasive Tools utility on the File Path dialog. Open the DData table and click the statistics button. The 'Total number of Keys' should be 2. If the Index exists, this message can be ignored.
Sometimes the SPC Data Entry module can get confused when it processes a formula that uses square brackets [ ] inside a string. Typically square brackets are used as a cell reference. When a cell reference is encountered in a formula, the reference is replaced with the actual value from that cell. Here are some rules to keep in mind when using square brackets inside formulas.
If you are using an invalid cell reference and you know it, e.g. [Z9] or [Square], then you should CONCAT it, e.g. CONCAT "[", "Z9]" or CONCAT "[Square", "]" (it doesn't matter how you split it up as long as you split it up).
If you are using a valid cell reference but you don't want us to replace the reference with the cell's actual value, then you should CONCAT it as well. For example, you have a string "the [N7] PLC register". If [N7] is a valid cell, then the reference will get replaced with its value. But, in this case you really want the text [N7] to appear because it refers to a PLC register. You should change the string to: CONCAT "the [", "N7] PLC register".
Starting in version 7.2 the ODBC template commands (e.g. Q_START), allow up to 10 connections. This is implemented as an optional new parameter in these commands. It is not necessary to edit existing templates to add this new template, but new templates must use the new parameter. However, some existing "complex" formulas may require you to edit them and add the new parameter. This happens if there are commas after the command that cause it to think that this parameter exists. In that case, you will get a message stating the connection number must be between 1 and 10. An example of this kind of formula would be: IF QSTART SVAR1, GOTO [A1], GOTO [A2]