+ Reply to Thread
Results 1 to 4 of 4
Thread: Patching from 4.0 to 4.1
-
05-07-2007 04:56 PM #1fret_24 Guest
Patching from 4.0 to 4.1
I'm getting an error when I try to run the patch to upgrade from v4.0 to v4.1. The details of the error are below. There's a problem with a file path.
An error occurred while installing the patch.
Could not find a part of the path 'E:\Surveys\Install\Patches\Checkbox Web 4.1/Install/Patches/Checkbox Web 4.1/LDAPAuthenticationProvider.xml'.
-
05-07-2007 05:20 PM #2
Administrator
- Join Date
- Mar 2007
- Posts
- 385
In the past we have seen this issue when users encountered issues during the patching process. In particular they did not have write access to the ~\config\security.xml file and as a result the new entry for the LDAPAuthenticationProvider is not added. If you open your security.xml file do you seen an entry similar to the following? If not please try adding it manually.
<provider default="false" type="authentication" name="LDAPAuthenticationProvider" filePath="FULLY QUALIFIED PATH TO CHECKBOX INSTALL DIRECTORY/config/LDAPAuthenticationProvider.xml" configDataType="Checkbox.ActiveDirectory.Providers .LDAPAuthenticationProviderData,Checkbox" />
-
05-07-2007 07:25 PM #3fret_24 Guest
Interesting. I added that line and I'm still getting the same error.
FYI, when I first attempted the install I got a write error because I had removed write permissions to the config folder after I installed v4.0 (as per the instructions). I added full permission back for the appropriate users and then got to this error. Also, all of the file paths in the security.xml file read like the one below, problem? I got rid of the extra forward slash, but that didn't work either.
E:\Surveys\/config
-
05-07-2007 08:19 PM #4fret_24 Guest
I think I got it working. There were some paths in the web.config file that had the same problem (\/config). I fixed them, but that caused a major meltdown. That meltdown was due to the LDAPAuthenticationProvider.xml file not copying properly from the patches folder to the security folder. None of the pages would work. I copied that file and ran the sql patches directly on the server and after an IIS restart all was fine again.
Maybe that will help someone in the future.


LinkBack URL
About LinkBacks
Reply With Quote
