Step 6 - Common Upgrade Errors
| The issues below may be encountered *during* the upgrade: - If you receive "Update step failed: Copy of app dir appears to have failed."
- Ensure you run the Novo Config Tool as Administrator.
- Unshare any shared folders or files.
- Unlock any locked files that may be open.
- Check the Novo Config Tool Log for errors (c:\NovoConfigToolLog.txt)
- The following error in the Novo Config Tool Log usually indicates the image file paths are too long: "The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters."
- To resolve this issue:
- Browse to {Novo Root}\app\admin\virtual folder and copy the imgs folder to a temp location.
- Delete the contents from the {Novo Root}\app\admin\virtual\imgs folder.
- If the upgrade is successful, you will need to copy the contents of the imgs folder in the temp location back into the {Novo Root}\app\admin\virtual\imgs folder.
- The following errors indicate the user that is logged into the server {Current User} does not have enough permissions to perform the upgrade.
- Access to the path 'C:\Documents and Settings\{Current User}\Local Settings\Temp\1\NovoUnzipDir\NovoRoot' is denied.
- Error moving directories Access to path '{Novo Root}\app' is denied.
- To resolve these issues give full permission to the following folder:
- Windows Server 2008: C:\Users\{Current User}\AppData\Local\Temp.
- Windows Server 2003: C:\Documents and Settings\{Current User}\Local Settings\Temp.
- The Novo Config Tool stalls while "Registering DLL's..."
- Ensure you run the Novo Config Tool as Administrator.
- Stop IIS.
- Open the command prompt and register the kb.dll and aspsmartupload.dll in the {Novo Root}\app\com folder.
- Restart IIS.
The issues below may be encountered *after* the upgrade: - Novo Scheduler Service stops
- Restart at mmc may seem to restart the service but no log entry is generated. An attempt to restart may result in a Windows error that the service did not stop in a timely manner which leaves the service in a stopped state; starting the service manually then produces a log entry and scheduled reports are sent
- AD Login values are changed from userPrincpleName to sAMAccountName (or visa versa) causing new users to be created in AD
- ASPX pages are inaccessible
- If your site is set to the Shades_of_Grey theme (note the underscores "_"), after the upgrade you may receive the following error in the event log when you try to browse to ASPX pages: "Theme 'Shades_of_Grey' cannot be found in the application or global theme directories.
- Receive an "Object Required" error when trying to attach a file to an article or request.
- Copy the {Novo Root}\app\com\aspsmartuploadutil.dll and place it in the C:\WINDOWS\system32 folder. Note: If you have a 64-bit machine, you may need to place it in the C:\WINDOWS\SysWOW84 folder.
- Open the command prompt and register the aspsmartupload.dll in the {Novo Root}\app\com folder.
- When searching you receive "Application Error: [Microsoft][ODBC SQL Server Driver][SQL Server]Full-text table or indexed view has more than one LCID among its full-text indexed columns."
- You receive the following error when trying to browse to the website or virtual directory:
Server object error 'Asp 0177 : 80040111'
Server.CreateObject Failed
/{DomainName}/inc/common_obj.asp, line 18
80040111 - Stop IIS.
- Open the command prompt and register the kb.dll and aspsmartupload.dll in the {Novo Root}\app\com folder.
- Restart IIS.
- Custom timer rules do not work after upgrading
- The .bat files for timer rules used to be located in the {novo root}\app\com folder. In version 5.0 the .bat files were moved to the {novo root}\NovoScripts folder.
- Check and see if there is a {novo root}\NovoScripts folder. If there is a NovoScripts folder with the appropriate .bat files then take the following actions:
- On the web server click Start > Administrative Tools > Task Scheduler, and open the scheduled task for any one of the .bat files.
- Edit the scheduled task so the path is pointing to the {novo root}\NovoScripts folder and not the {novo root}\app\com folder.
- Repeat the above step for other scheduled tasks if needed.
- There is no NovoScripts folder and the .bat files are not in the {novo root}\app\com folder take the following actions:
- In the {novo root} directory create a "NovoScripts" folder.
- Open the backup file that was created during the upgrade (app.backup...) and navigate to the "com" folder.
- Copy and paste the following files to the "NovoScripts" folder:
- cssupdate.bat
- cssupdate.bat.orig
- escalation.bat
- escalation.bat.orig
- runassetmanagement.bat
- runassetmanagement.bat.orig
- runmemorized.bat
- runmemorized.bat.orig
- runtimerudr.bat
- runtimerudr.bat.orig
- wget.exe
- Click Start > Administrative Tools > Task Scheduler and change the path for each scheduled task that runs a .bat file.
|