Preparation
Server requirement summary
SQL Server
- SQL 2000 or SQL 2005
- Latest SQL service pack
- If SQL 2005, test database in SQL2005 compatibility mode
- Database in simple recovery mode
- Datafiles should be 1/4 to 1/3 free space to allow for growth.
- Good time to create a new datafile if they have only one
- iMIS users and Name/Name_Security in sync
- If .NET is in use, extra records in UserMain can interfere with the upgrade. Still investigating a fix.
.NET app server
- IIS installed, preferably not to default location
- www service
- smtp optional if they have another server to send mail for them, otherwise required
- ftp optional according to usage
- Indexing service installed
- On Windows 2008, this is under File Server role, but File Sharing is not required.
- SQL tools installed
- Latest service pack installed
- Must match version of SQL Server
- SQL Express edition is not sufficient
- iMIS installer and any patches downloaded and expanded
- .NET Framework 3.5 installed
- Windows Update run until no more patches discovered
- "SQL XML 4 Security Update" (KB 954430) will sometimes show up even after being installed. If you're sure it succeeded, you can go ahead.
Gotchas
Never install or upgrade live first
Nearly every upgrade hits at least one snag before the upgrade runs to completion. Always, always have a backup.
Hyphen in server name
Upgrade to iMIS15 will fail with a hyphen in the SQL Server name. Resolution was to create a TCP/IP server alias without hyphens using cliconfg. ASI installation document recommends against using (local), hyphens, numbers, or special characters.
Special characters in sa password
The upgrade to iMIS15 fails with Special Characters in SA password - If the SA password has some special characters in it.
- Known problems: ampersand (&), carat (^)
- Known to work: exclamation point (!)
UserMain out of sync with Name
If .NET modules of iMIS are already in use, or have been in the past, records in the UserMain table may be out of sync with Name, and cause a problem in the upgrade.
Casual license required before upgrade
Upgrade to iMIS 15.1 does not accept Casual license key when entered in the installer. This is a known issue SMRISSUE 193144. The solution is to enter the iMIS15 license with the CASUAL license key in 10.6 and then upgrade.
- Update: in 15.1.2, the first step of the upgrade will not proceed until the license is entered.
- As long as the iMIS 15 license doesn't drop any modules used in production, you can generally enter the new license in the iMIS 10 database so you don't have to enter it again on each upgrade attempt.
- If you can't add it to live for whatever reason, script the license key values so they can be run multiple times on repeated upgrade attempts.
iMIS 15 e-Series
The iMIS e-Series application Wizard now requires the iMIS System Admin username and password and the iMIS Application Server URL.
Permissions on parent site
The website root above each iMIS Casual and Public virtual directory must also allow ASPNET to read files, because ASPNET will try to read web.config in the parent folder.
Internet Explorer 7/8 Enhanced Security Configuration
If IE 7/8 is configured with Enhanced Security (the default), then the iMIS Casual and Public sites must be listed in Trusted Sites. This will even affect the iMIS desktop.
Vista and Windows Server 2008
Permissions
- You must run AsiMultiInstanceUtility.exe as Administrator (Run as Administrator...) or they won't be able to create services and indexes
- You must run Omnis7.exe as Administrator the first time, or any time you are creating a new Server URL. This allows Omnis7 to create the proper ODBC DSN.
- ICACLS must run in an Administrator Command Prompt (Command Prompt -> Run as Administrator)
- Note that CACLS is mentioned in some instructions including ASI documentation. ICACLS should always be used if it is available.