nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

6.5 regeneration problem

mannyroble

I've just recently migrated content from TeamSite 6.1 to TeamSite 6.5 and I am getting the following message when I try and regenerate a page:

Forms Publisher: Preview and Generate
Error: The following error occurred while creating file Y:default\main\internet\WORKAREA\eroble\personal\banking\checking_comparison.asp: The file name or path is incorrect or too long. The templated file was not generated.

The kicker is that when I did the same change to the same file on 6.1 it worked just fine. Has anyone had this problem before? I've looked at all the log files I can think of, but there isn't really a hint of what the problem might be Smiley Sad

Manny

Find more posts tagged with

Comments

Adam Stoller

Is that the actual error message? If so - the problem looks like you're missing a '/' (or '\') after the "Y:"

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

mannyroble

Hi fish,
I wish the problem were that easy to fix. If I were missing the backslash I would not be able to view the pages virtualized within TeamSite at all. It is certainly a very puzzling error becuase there are no inidcations in any of the logs that something is wrong. Do you have any suggestions of where else to look for a clue?

Thanks,
Manny

SpecificMonthRecordFilter.zip

Adam Stoller

No ideas off the top-of-my-head sorry - I try to stay as far away from windows as possible and fortunately my current [long term] project is on Solaris ;-)

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

mannyroble

Here's something strange - it all works now Smiley Sad

I usually post a question on the forums as a last result - but page regeneration seems to be working. I hadn't done anything else since I posted last Friday.

This really worries me because this problem could happen again and I can't just say lets wait a few days and it will start to work again. Go figure, but at least I still have screenprints of my error to prove I wasn't dreaming this whole thing up.

Thanks for the sugestions though - I'd rather work on Solaris as well, but sometimes the decision is not up to you Smiley Wink

Manny