Zembian

Problem

Unable to insert autotext entries in document footers in Microsoft Word 2003. All autotext entries were missing and only am empty box displayed when the button was pressed. A new Normal.dot would fix this but I needed to preserve a custom toolbar and several macros in the current Normal.dot

Solution 

1) Exit Microsoft Word 2003. Rename Normal.dot to something else .dot

Example : Normalbak.dot

2) Start Word, it will create a new default Normal.dot

3) Again shut down Word. Start Word and open Normalbak.dot

4) In Word click Tools > Templates and Add-Ins, click the Organizer button in the bottom left corner of the dialogue box

5) Following details on the following link to copy back your macros etc.

Styles and AutoText are not copied to a new template based on the Normal.dot template in Word 2002

Problem 

On a previous Windows XP SP2 build VWD Express 2008 would crash when I selected the new split view.

Solution 

This post referred to a problem with Office 2000 and although I am running Office 2003, it is not 2007 which seemed to be the key.

Compatibility problem between VS 2008 and Office 2000 and how to fix it

I checked out my path environment variable and did not have any references to Office 2003.

Just to see what would happen I added the follow :

C:Program Files\Microsoft Web Designer Tools\VWD

as the first item in the path variable (Note : Default install path). One reboot later and the split view was working. Therefore it did seem to be a problem with the version of fpcutl.dll Visual Web Developer Express was using.

Since encountering this issue I recently had machine reinstall, same Windows XP SP 2, same Office 2003 and installed VWD Express 2008. This time no there were no problems at all. Still it is worth trying the path changed if a reinstall is not available to you.

Problem 

Trying to get BlogEngine 1.3 set-up in a proper windows login environment did not go as smooth I hoped. The errors I have seen range from Server Unavailable to IIS Metabase errors for my chosen user.

Find many posts referring to the ASNET user my first problem was to set that, although I now realise the default user would have been fine. The key to this is within the IIS directory security change the location to your local PC name, now you can just type ASPNET into the object name and click Check Names.

After following the install guide and permissions settings BlogEngine was not working and was stuck with Metabase errors but at least selecting my user wasn't a problem now. 

Solution

The following post "Failed to access IIS metabase." with ASP.NET 2.0 solved most of the issues (post 8)

I followed steps 1-5 :

1. Unregistered all the versions of ASP.NET with command "C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis –ua".

2. Deleted the ASPNET account from "Local Users and Group – Users".

3. Then registered ASP.NET 2.0 with IIS using "C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis –i".

4. Gave permissions to the ASPNET account using "C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis –ga machinename\ASPNET".

5. Reset the IIS and that resolved the issue for ASP.NET 2.0.

Then go back to the BlogEngine install instructions and set the permissions for machinename\ASPNET on the BlogEngine directory and APP_DATA.