Templating Error under TS 7.2.1

System

Upgrade from TeamSite 6.7.1 on new hardware
Working with a clean install of TS 7.2.1 on Windows 2008 R2 with IIS 7
We have ported the backing store across and the configuration files updating and/or merging as needed.

I am encountering two errors that I think are related.

First, when I do "File->New Form Entry" from within a category/type it will present me with the error

"Unable to create a new form of type CATEGORY/TYPE under the branch //[servername]/default/main/branch/subbranch. This form was not configured for this branch or you do not have permission to access it."

However, if I move up to the top of the workarea or even just up one level into the category directory, it presents me with the list of available forms and I can choose the type I was in previously and it all works.

Second error occurs when I have filled in the form and saved the DCR (which works fine) when I click the Generate or Preview buttons I get the error:

"Please select a form entry."

However, if I leave the form entry screen, select the newly created DCR and select "Actions->Generate Page", it will allow me to correctly generate the file.

None of the log files appear to update when these errors are displayed and I have checked the templating.cfg file and it is correct with no restrictions.

Suggestions and help would be appreciated as I have no idea what is going on.

----

Update: Additional information.

It turns out that if you edit the generated file and the DCR opens for editing, you can then successfully use both the preview and generate buttons within the DCR form.

It also appears that this same issue occurs in TS 6.7.1 but it does on pop the error message, it just silently fails to work.

Migrateduser

Solved:

This turned out to be a case of incorrect case in the templating config file compared to the file system. In the templating config file we had "Category/type" (note case) and in the file system the directory pair were named "category/type". Since we are running windows, the case didn't matter when you are selecting the form type to create from the selection screen, however, if you go into the "category/type" directory it does a lookup into the templating.cfg file and does not find a match because it is doing a case sensitive lookup there.

The fix was twofold:

1) Fix the case in the templating.cfg file.
2) Fix the case of the Extended Attributes on the generated files.

If you only do step 1, then all newly generated files will have the correct attributes, but any existing generated files will have the incorrect case in the extended attributes which will cause a similar error when you try to edit them. They essentially become uneditable items.