Troubleshooting iMIS

"One or more errors occurred" when accessing the Staff site

Problem:

You might see the following error when trying to access the Staff site on a fresh install or a system that was upgraded to iMIS 2017:

One or more errors occurred.
One or more errors occurred.
One or more errors occurred.

Solution:

Do the following:

Verify the EntityManagerDefaultBaseUri and ImisWebServerUrl strings in the web.config files are using a fully qualified domain name (FQDN), not localhost or the machine name.

Web config files can be found at:

..\AsiPlatform\Asi.Scheduler_(iMIS App)\web.config
..\Program Files (x86)\ASI\(iMIS Dir)\Net\web.config

Make sure the FQDN resolves to a private IP address on the server. If necessary, add a hosts file entry to resolve the FQDN to the local loopback IP address 127.0.0.1.
Make sure the Default Web Site in IIS has a valid SSL certificate assigned to the HTTPS binding.
Check to see if TLS 1.0 is disabled on the server. You can verify that by running the IISCrypto utility on the server. For more information, see Additional dependencies.

If TLS 1.0 is disabled on the server, make sure the following registry entries are set on the server to enforce strong encryption:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft.NETFramework\v4.0.30319] "SchUseStrongCrypto"=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft.NETFramework\v4.0.30319] "SchUseStrongCrypto"=dword:00000001

Get-ItemProperty -Path 'HKLM:\SOFTWARE\Microsoft\.NetFramework\v4.0.30319' 
	-Name 'SchUseStrongCrypto'
Get-ItemProperty -Path 'HKLM:\SOFTWARE\Wow6432Node\Microsoft\.NetFramework\v4.0.30319' 
	-Name 'SchUseStrongCrypto'

Run the following in PowerShell to set the registry entries on the server:

# set strong cryptography on 64 bit .Net Framework (version 4 and above)Set-ItemProperty 
	-Path 'HKLM:\SOFTWARE\Wow6432Node\Microsoft\.NetFramework\v4.0.30319'
	-Name 'SchUseStrongCrypto' -Value '1' -Type DWord
# set strong cryptography on 32 bit .Net Framework (version 4 and above)Set-ItemProperty 
	-Path 'HKLM:\SOFTWARE\Microsoft\.NetFramework\v4.0.30319' 
	-Name 'SchUseStrongCrypto' -Value '1' -Type Dwordo

Updating all tables that reference renumbered SEQN values

Problem:

Applying Service Pack P causes all the SEQN columns in multi-instance Customizer tables to be reordered if any of them contain a SEQN value of 1,000,000,000 (one billion) or more.

This can cause problems where those SEQN numbers are used or stored in tables or other data sources as reference to specific rows.

Solution:

If SEQN numbers must be renumbered, a table is created that maps the old numbers to the new numbers, so that any third-party application using the SEQN numbers can update their data accordingly. This table is named CustomMISeqnMapping.

You must use the CustomMISeqnMapping table to update all tables that reference the renumbered SEQN values. For example, let's assume you have a multi-instance customizer table called ReferencedSEQNTable. Also assume you have another table that stores references to the SEQN values in ReferencedSEQNTable called ReferencingSEQNTable, in a column named ReferencedSEQN.

The following SQL can modify the SEQN values so that they reference the correct rows:

-- Use Mapping Table to 'fix' referenced SEQN values
UPDATE r
	SET ReferencedSEQN = NewSEQN 
	FROM ReferencingSEQNTable r
		INNER JOIN CustomMISeqnMapping m ON m.TableName = 'ReferencedSEQNTable'
			AND m.ID = r.ID 
			AND m.OldSEQN = r.ReferencedSEQN
	WHERE r.ReferencedSEQN  m.NewSEQN;

Note: Replace the names of the example referencing table, column and referenced customizer table with actual names of the referencing table, column and referenced customizer table.
You must do this for every table and column that references a customizer table SEQN value.

The following SQL code can be run to determine beforehand whether SEQN values will be renumbered:

DECLARE @maxSql nvarchar(max);
SELECT @maxSql = N'';
SELECT @maxSql += CASE WHEN @maxSql = N'' THEN '' ELSE N'    UNION ALL ' END + NCHAR(10) +
		N'    SELECT MAX(COALESCE(SEQN, 0)) AS MaxSEQN FROM ' + QUOTENAME(TABLE_NAME) + NCHAR(10)
	FROM UD_Table
	WHERE ALLOW_MULTIPLE_INSTANCES = 1;
SELECT @maxSql = N'SET NOCOUNT ON; ' + NCHAR(10) + 	
		N'WITH MaxSEQNs AS ( ' + @maxSql + N')' + NCHAR(10) + 
		N'SELECT @maxSeqnOUT = MAX(COALESCE(MaxSEQN, 0)) FROM MaxSEQNs;'
DECLARE @maxSeqnValue int;
EXEC sp_executesql @maxSql, N'@maxSeqnOUT int OUTPUT', @maxSeqnOUT = @maxSeqnValue OUTPUT;
IF @maxSeqnValue >= 1000000000 -- Only renumber if they've got seriously high SEQN values
	SELECT 'SEQN Values will be renumbered'
ELSE
	SELECT 'No Changes will be made'

Changing the MaxInvalidPasswordAttempts value to 6 or higher results in users being locked out of iMIS

Problem:

If the MaxInvalidPasswordAttempts value in the web.config file is modified to a value of 6 or greater, users will be locked out of iMIS. They will see the following message:

The username or password you entered is incorrect.

Solution:

PCI requires limiting access after six logon attempts. The MaxInvalidPasswordAttempts value in the web.config file must be 5 or fewer in order to meet this requirement.

This requirement is introduced in Service Pack B for PCI compliance.

Credit card encryption error

Problem:

You receive the following error message during an upgrade to iMIS:

There was an error during credit card encryption. This upgrade is incomplete, and you must restore from a backup. iMIS will now exit.

Solution:

This error indicates the encryption check failed during an upgrade of the database. iMIS cannot repair this database, so you must restore from your backup.

Customization to task list items not taking effect

Problem:

When making a change to a feature using the Set up module function, you expect the changes to take effect after restarting Advanced Accounting Console, but the changes do not appear.

Solution:

This problem occurs when a customization causes changes to the left navigation items, requiring a cache refresh. A cache refresh occurs on regular intervals, typically 15 minutes, but you can also stop and restart all websites that contain your iMIS applications to correct the problem.

Do the following to correct this problem:

Close the Advanced Accounting Console.
Wait 15 minutes, or the amount of time specified for the default refresh cache interval.
If you do not want to wait 15 minutes, go to IIS. Stop and then restart all websites that contain your iMIS applications.

Data source (ODBC) not found on Vista computers

Problem:

On a Windows Vista or Windows 7 workstation, you can start Advanced Accounting Console normally, but when you attempt to log on to iMIS, you receive an OdbcSQL/31 0 - IM002 error, indicating that a datasource name was not found and there is no default driver specified.

Solution:

This problem is caused by trying to run Advanced Accounting Console without first setting the shortcut for Advanced Accounting Console to Run as administrator.

Do the following to set iMIS to Run as administrator:

Close the Advanced Accounting Console.
Ensure that your User Account says Administrator.
Locate the Start menu shortcut for Advanced Accounting Console.
Right-click the shortcut and choose Run as administrator.
If prompted to allow the Omnis7.exe program to run, click Allow.
Log on to the Advanced Accounting Console to ensure that the problem is fixed.
Perform steps 1 through 6 for any additional Advanced Accounting Console shortcuts on your computer.

Database is locked and cannot be restored

Problem:

When you try to restore the iMIS database, SQL Server reports that the database is locked and cannot be restored.

Solution:

You must temporarily stop Internet Information Services (IIS) before attempting to restore the iMIS database. Otherwise, the service can lock the database and prevent the restoration.

Run the following command from a command prompt to ensure that IIS is stopped:

iisreset –stop

Once you have restored your database, you can run the command iisreset –start to restart IIS.

Note: If you changed the name of the database during the restore, such as restored from a different database, you must open the iMIS DB Maintenance Utility (go to Start > ASI > iMIS > Tools) and click Prepare iMIS Database.

Determining Service Pack levels

Problem:

You cannot determine the current Service Pack of your SQL Server environment, which might be needed for verifying system requirements or working with ASI Technical Support to troubleshoot a problem.

Solution:

To determine the current Service Pack level of your Windows operating system, you can use your SQL Server management environment to run the following SQL Query:

SELECT @@ version

To determine the current Service Pack of your SQL Server environment, you can use your SQL Server management environment to run the following SQL Query:

SELECT SERVERPROPERTY('ProductLevel')

Email output or event invites not sent or received

Problem:

Email outputs from iMIS are not being sent. These emails could be merge process outputs, notifications to users, for example, website error messages that are sent to the designated webmaster for your iMIS-based web content.

Solution:

This problem can occur due to several causes:

Your organization’s SMTP server was not specified correctly during installation of iMIS.
The domain name of your organization’s SMTP server has changed since you installed iMIS.
Your organization’s enterprise virus protection might have persistent port blocking rules against mass-mailing worms that were triggered if iMIS tried to send email notifications to you from an IP address that did not correspond to a trusted IP address.

Isolating the cause of the problem depends on which type of notification is not working correctly:

Outlook event invitations are handled by your Exchange webmail proxy server.
All other email outputs are handled by the SMTP server that is configured for each iMIS-related ASP.NET application.

Licensed users exceeded

Problem:

You receive the following error message while using iMIS:

Number of licensed users exceeded. Please try again later.

Solution:

This error is caused by an extraneous entry in the iMIS UserProcess table. If the number of users actually logged in does not exceed your named license counts, do the following to correct the problem:

Have all users log out of iMIS.
Use your SQL Server management environment to perform one of the following fixes:
- Delete all rows from the UserProcess table.
- Truncate the UserProcess table.

Log on or Change Password appears unexpectedly

Problem:

You expect a particular iMIS page to appear as the result of taking some action, but what appears instead is a page asking you to log on or to change your password. This error occurs only after your iMIS session has been idle for a long time.

Solution:

See Optimizing timeouts on iMIS servers for how best to adjust your ASP.NET settings for your situation.

Page not available error after long idle time

Problem:

You expect a particular iMIS window to appear as the result of taking some action, but what appears instead is a Page Not Available error. This error occurs only after your iMIS session has been idle for a long time.

Solution:

See Optimizing timeouts on iMIS servers for how best to adjust your ASP.NET settings for your situation.

Page not found error

Problem:

You expect a particular iMIS window to appear as the result of taking some action, but what appears instead is a Page not found error.

Solution:

To resolve the problem, you need to add the iMIS .NET Application server to the Trusted Sites in Internet Explorer.

Do the following to correct this problem:

In Internet Explorer, go to Tools > Internet options.
On the Security tab, select Trusted sites.
Click Sites.
Enter your iMIS .NET Application server in the Add this website to the zone field.
Click Add to add to the trusted Websites list.
Click Close.
Apply your changes.

Pop-up windows never open

Problem:

When you click a button in an iMIS window, nothing happens. Usually this is a button that you would expect to display a new window of some sort.

Solution:

Most iMIS UI content is a web page displayed in a browser control, even when using Advanced Accounting Console instead of a web client. As with any web-based application, some UI elements are actually pop-up browser windows. If you have any type of pop-up blocking settings enabled in your browser, or if you are using some third-party pop-up blocking software, this will prevent some iMIS windows from being displayed properly.

You must disable all pop-up blocking behavior in your browser for content that it receives from the iMIS application server tier or public website tier. If you have third-party pop-up blocking software, you must likewise configure it to enable pop-ups from any iMIS source.

Problems publishing and creating new content

If you have problems publishing and creating new content, your host might be missing Windows Server roles it needs:

Add Web Server and Application Server roles to each iMIS server.
Add Web Server roles to each web server.

Report Viewer errors

iMIS offers SQL Server Reporting Services (SSRS) support through the ReportViewer control and uses its Reset method, which was not in the original distribution of the control. Unfortunately, several Microsoft installers ship the older version of the control and place it in the GAC, where it is found before the newer version in the iMIS \bin folder.

You have an older version if you encounter an error like the following:

"Microsoft.Reporting.WebForms.ReportViewer” does not contain a definition for “Reset' and no extension method “Reset” accepting a first argument of type
"Microsoft.Reporting.WebForms.ReportViewer” could be found (are you missing a using directive or an assembly reference?)

To get the newer version, search the web for Microsoft Report Viewer Redistributable 2005 SP1 (Full Installation), which is available as a free download from several sites.

Note: Be sure you get the 2005 pack (the 2008 SP1 package cannot correct the problem). Also be sure that you select Full, not Upgrade.

Reporting, queries slowed by table locks

Problem:

When running lengthy ad hoc queries or reports, or when using third-party tools for reporting from the iMIS database, locks are placed on iMIS tables. This prevents iMIS users from performing updates or inserts until the reports finish.

Solution:

The problem is with lock escalation and the transaction isolation level in SQL Server. If a query affects a large percentage of rows in a table, the shared page locks are escalated to a table lock to reduce locking overhead.

There are two ways to deal with this problem:

Best approach – Separate your transaction processing from reporting functions, so that the long-running SQL queries are run against a static database:
- Create periodic copies of the iMIS database to use for reporting.
- Run all reports against the copied database, while transactions go against the original database.

This is the best approach because your long report queries are run against a static database. Using NOLOCK might cause erroneous values in reports if dirty reads or phantom rows have affected the result set of the report query.

Alternative approach - Add the NOLOCK keyword to long-running SQL queries to keep locks from lasting as long. This forces SQL Server to change the transaction isolation level to READ UNCOMMITTED. This does not issue shared locks at either the page or the table level and does not honor exclusive locks, all of which can result in erroneous query results because of possible dirty reads and phantom rows.

To add the NOLOCK keyword to ad hoc SQL queries (or custom scripts), add the string (nolock) to the end of the FROM clause. For example:

Select ID, LAST, ADDRESS from Name (nolock)

To configure iMIS to use the NOLOCK keyword automatically on specific long-running reports, create a NOLOCK keyword for large report runs.

Obtain the iMIS SQL Server login password for the SQL Server instance on which the iMIS database exists.

Note: Some reports that have custom reporting engines (RunProcedure specified in report spec) will ignore the NOLOCK keyword. This typically affects reports that join two or more tables.

Log on to Advanced Accounting Console as MANAGER.
Select Utilities > Report Specs. The Report Specifications window is displayed.
From the list of reports, select a report that is taking a long time to run and locking records.
Click Parameters. The Detail Report Parameters window is displayed.
Click Edit.
In the Parameters field, enter NOLOCK.
Repeat this process for all affected reports.
Close the Detail Report Parameters window.
Close the Report Specifications window.
Select File > System Setup. The System Setup window is displayed.
Click SQL Security Setup. The SQL Security Setup window is displayed.
Click Edit.
In the NOLOCK keyword field, enter NOLOCK.
Click Save.
Enter your sa Password when prompted.
Click Create SQL Logins to add the NOLOCK keyword to logins on that instance.
Enter the password and accept any messages about shutting down iBO on the host.

SecureConnectionFault application errors related to certificate validation policy are logged on the server and displayed in the browser

A tighter certificate validation policy for secure communication with the iMIS service requires that the certificate is in date, has been issued by a recognized certificate authority and is for the domain by which the service is being accessed. Using a certificate that does not meet this validation policy results in application errors being logged on the server and displayed in the browser. The error logged on the server is of type SecureConnectionFault and provides additional details.

If the iMIS website is accessed from a browser installed on the application server, then a Secure Connection error will be displayed, along with a reason and guidance for resolving the error; otherwise, a generic error is displayed. The cause of the error can be reviewed in the server Application log.

The SecureConnectionFault error is introduced in Service Pack J.

Silent install of Advanced Accounting Console

Answer files are specific to the version of the setup.exe file that was used to create them. You cannot use answer files that were created from a previous release of iMIS.
If a silent installation fails for a new installation of the Advanced Accounting Console, it is generally safe to troubleshoot the issue with the answer file and then attempt the silent installation again. However, at that point you are outside of the automated process and it might be easier to manually run the installer on any workstations that failed the automated silent install.
If a silent installation fails for an upgrade of an existing Advanced Accounting Console, you should not try to modify the answer file and run the silent installation again, because it is likely by this point that some Advanced Accounting Console-related files have already been removed from the workstation and you could encounter more errors. Instead, you should manually run the iMIS Installer on workstations that failed a silent upgrade attempt.
In any scenario where you record an answer file on one computer and then run a silent installation using that answer file on a different computer, there are potential points of failure due to differences in the configuration of the two machines. Some typical examples are:
- You record an upgrade of the Advanced Accounting Console on a computer where the iMIS client is installed in the default C:\Program Files (x86)\ASI\iMIS path, and then you run a silent installation on a target computer where the Advanced Accounting Console is installed in a different path.
- The answer file was recorded on a computer that already had an Advanced Accounting Console (an upgrade installation), but the target computer does not have an Advanced Accounting Console installed already (a new installation), so the installation requires more information than what was recorded in the answer file.
- The target computer does not meet all the system requirements and prerequisites.
When you manually edit an answer file, you should take special care to change only values that are obviously file paths, database connection information, iMIS server URLs, license values, and so forth. Modifying other non-obvious values can result in infinite loops within the iMIS installer and other undesirable behavior.
It is advisable to test your silent installations on non-production computers that are closely analogous to your production target computers before actually running the silent installations on production computers.
The setup.log file contains three sections that are useful for troubleshooting:
- [InstallShield Silent] identifies the version of InstallShield Silent used in the silent installation. It also identifies the file as a log file.
- [Application] identifies the installed application’s name and version, and the company name.
- [ResponseResult] contains the result code indicating whether the silent installation succeeded. An integer value is assigned to the ResultCode keyname in the [ResponseResult] section. InstallShield places one of the following return values after the ResultCode keyname:
  - 0 Success.
  - -1 General error.
  - -2 Invalid mode.
  - -3 Required data not found in the Setup.iss file.
  - -4 Not enough memory available.
  - -5 File does not exist.
  - -6 Cannot write to the response file.
  - -7 Unable to write to the log file.
  - -8 Invalid path to the InstallShield Silent response file.
  - -9 Not a valid list type (string or number).
  - -10 Data type is invalid.
  - -11 Unknown error during setup.
  - -12 Dialogs are out of order.
  - -51 Cannot create the specified folder.
  - -52 Cannot access the specified file or folder.
  - -53 Invalid option selected.
The iMISinstall.txt file contains a detailed installation log for general iMIS installation troubleshooting. Whenever data is read from the answer file used in a silent installation, you will see a message in this log like the following:

12:02:58 | SilentReadData section: asiDatabaseInfo-0 key: sgSQLServer
12:02:58 |      found  sgSQLServer:  MYMACHINEHOST\SQL2005CS

This example shows that the iMIS Installer silently read and set the value of sgSQLServer to MYMACHINEHOST\SQL2005CS.

If a silent installation fails, the last information in this log will typically be an error message followed by an abort. The error message should help you isolate what went wrong during a silent installation:
If a silent installation fails, the last information in this log will typically be an error message followed by an abort. The error message should help you isolate what went wrong during a silent installation:

12:02:58 | bad db date in silent mode..aborting
12:02:58 | OnAbort called

Tips to consider:

If there appears to be a problem with the result of a silent installation, you can review the following log files to help troubleshoot the problem:
- The silent installation log file (setup.log by default) located by default in the same folder as the setup.exe file. This location and file name might be different as described below.
- The IMISinstall.txt file located in C:\Windows\Temp.
Although you can manually edit an answer file to produce slightly different variants of the same general silent install, you might get unexpected results in some cases. Editing an answer file for the same general type of installation to change some minor details, such as which iMIS database to use, is generally easy to do. But choosing entirely different components to install results in substantially different answer file contents, so it’s impractical to edit an answer file to add or remove iMIS components. It is a better practice to run the iMIS Installer in recording mode to create different types of installations.
If you prefer the answer file be placed in a location other than the default C:\Windows folder, use the -f1 parameter as follows when you run the setup.exe file in recording mode. For example:

C: \temp\setup.exe -r -f1C:\temp\setup.iss 
C: \temp\setup.exe -r -f1"C:\<Directory with a space in it>\setup.iss"

Note: Make sure you have no space between the -f1 parameter and the file path that indicates the target folder for the setup.iss file. Also, the -f1 parameter must use an absolute file path that starts with a drive letter.

If you prefer the answer file to have a different name than the default setup.iss file, which can be convenient if you want to keep a setup.exe file and several different answer files in the same network folder, you can specify the desired file name in the -f1 parameter when in recording mode. To use that particular answer file when running a silent installation, use the -f1 parameter again to specify which answer file to use during the installation.

For example, assume that the setup.exe file for the new iMIS release is located in a network drive that is mapped to drive letter U: on every workstation on the network. You want to record a new answer file for installing only the Advanced Accounting Console client from that setup.exe file. You would first run the following command on a workstation that does not contain an Advanced Accounting Console to record a specially-named answer file for doing silent installs or upgrades of only the Advanced Accounting Console for this release:

U:\iMISInstaller\setup.exe -r -f1U:\iMISInstaller\iMISDesktop.iss

Then on each workstation where you want to install or upgrade the Advanced Accounting Console, you would run the following command:

U:\iMISInstaller\setup.exe -s -f1U:\iMISInstaller\iMISDesktop.iss

If you prefer the silent installation log file to be placed in a different location than the folder that contains the setup.exe file, or to have a name different than the default setup.log file, use the -f2 parameter. Make sure you have no space between the -f2 parameter and the file path that indicates the target folder for the log file. For example:

U:\iMISInstaller\setup.exe –s -f1U:\iMISInstaller\iMISDesktop.iss –f2U:\iMISInstaller\Logs\userXdesktop.log

Note: The -f2 parameter must use an absolute file path that starts with a drive letter.

TCP/IP performance is slow

Problem:

Overall performance of a back-end tier or of a Full user’s Advanced Accounting Console seems slow.

Solution:

The default protocol for SQL Server connections is Named Pipes, so performance might be slowed on a network where TCP/IP is the primary network protocol.

For sites whose primary network protocol is TCP/IP, you usually can enhance performance by using the process described in your SQL Server documentation for setting all hosts and workstations involved in iMIS network traffic to use the TCP/IP protocol instead of the Named Pipes protocol.

Upgrade error for non-ANSI join operators

Problem:

During an upgrade from a previous release of iMIS, you receive an error message stating:

a query uses non-ANSI join operators

The upgrade fails.

Solution:

This problem occurs only in Microsoft SQL Server 2005 environments and is most likely to occur if you are running your current iMIS database in SQL 2000 compatibility mode.

The upgrade scripts for iMIS in a SQL Server 2005 environment require all objects in the iMIS database to be using the ANSI-standard join clauses introduced in Microsoft SQL Server 6.5. This error is generally caused by a custom trigger or stored procedure using the old-style join syntax that overloads the WHERE clause to provide both joins and restrictions. Specifically, the problem is caused by the *= and =* outer join operators, but it is good practice to ensure that all such joins are declared using an ANSI-standard join clause.

Do the following to correct this problem:

Restore your original backup of the iMIS database.
Review the restored database for custom triggers and stored procedures, and ensure that all such triggers use only ANSI-standard join clauses (INNER JOIN, LEFT OUTER JOIN, and so on).
Run the upgrade procedure again.

Windows open/change slowly

Problem:

New windows take a long time to appear, especially if you have not performed any action in iMIS for 20 minutes or longer.

Solution:

See Optimizing timeouts on iMIS servers for how best to adjust your ASP.NET settings for your situation.

Wrong ordinal error from DB Maintenance: Analyze Database

Problem:

When you run the Analyze Database function of the DB Maintenance utility on an upgraded iMIS database, you receive Wrong Ordinal messages on one or more table columns.

Solution:

This error is normal on upgraded iMIS databases, and it is mostly harmless and can be safely ignored in most cases. This error can cause problems for example if you attempt to bulk load an affected table using the bcp utility and the format files created by ASI. Tables with this reported error will not successfully bulk load unless you first modify the ASI-supplied format file to reflect the actual column order of the affected table instead of the default expected column order specified in the ASI-supplied format files.

Although this error is mostly harmless (except in the case of bulk load operations), you can correct the error by rebuilding the table.