Issue: Access Denied on Style Upgrade

I decided to revert and retry with beta 2 (which I had full success on upgrading before), and the result was the same, except it didn't install any Template Groups at all...

So still unsure what to do...

I'm led to believe you have another modification installed that is trying to run code at the hook template_compile, but instead it throws Access denied.

Might be http://www.vbulletin.org/forum/showthread.php?t=232993 as I've had it throw up a problem with the CMS, and I've disabled it.

I'll set to work on it when I have some time and disable the mods one at a time. Thanks for getting back to me.

More details. I've disabled all the plugins one at a time except for the CMS and the Blog. Disabling them resulted in the same problem with Beta 4. I also realised I'd had one other issue with Beta 4:

At stage: vault/install/upgrade_4p300b3.php
So there's something else that may impact the problem, not sure. I have run that script and then proceeded through the rest, and then get the error at finalupgrade. I do get that finalupgrade error with Beta 2, but not the above problem.

Anyways, here's the list of things that are installed on the site (Red are disabled):

BBR - Google Analytics Addon 1.0.3
CES Debug Switcher 1.1.0
CES VaultWiki 2.5.6
CES VaultWiki Categories 2.0.3
CES VaultWiki Images 1.1.3
CES VaultWiki Parser Extensions 1.1.1
CES VaultWiki Xpages 1.1.2
CES VaultWiki XRedirects 1.1.0
ibProArcade for vBulletin 2.7.0
Modification System 2.5
Post Thank You Hack 7.82
vBulletin Blog 4.0.2
vBulletin CMS 4.0.2
vBulletin Project Tools 2.0.1
VSa - ChatBox 3.1.6

I also have two plugins/products (both disabled as they were vB3) that add a couple of template changes.

The VSa ChatBox wasn't installed when I first had the wiki install issues.

Let me know if you need any other info, and your login to the site is still there should you want to look things over more closely. Thanks again for the help.

In 4.0.2, the way vBulletin compiles templates was changed significantly.

Fixed in the current ZIP. In vault/install/global.php, find:
Add after:

Thanks pegasus, will try out in the morning.

I tried it out, got through the install fine (though still had the file error I mentioned above about component not matching script). That went fine, but having issues trying to get the htaccess to work properly, getting a 404 even though I've used the inbuilt utility to create the htaccess code.