Moe Posted August 29, 2006 Posted August 29, 2006 (edited) I am using server advanced and I am getting a variety of erratic errors. Some do not make sense. For example on a search page I get the following error in Firefox but not in IE: An unexpected error has occurred File: Line: Column: Here is an error that appears sometimes but not others in Firefox or IE: The resource http://XXX.EDU&-find could not be loaded because the content-type was invalid (MCS-605) File: start.xsl Line: 85 Column: 300 Line 85 uses the document() function. I thought the problem was occuring because I was on a dual processor server but now I have a new machine with 1 processor. What could be happening? Thanks, Moses Edited August 29, 2006 by Guest
Wim Decorte Posted August 30, 2006 Posted August 30, 2006 The resource that's listed in your error doesn't seem like a valid URL for getting data from FMSA...
Moe Posted August 30, 2006 Author Posted August 30, 2006 I realize that. It's part of the error. Sometimes that page works properly and sometimes it doesn't. It's completely random, not dependent on circumstances. I have an update on this issue. I restarted the web publishing engine and now the pages are working normally. However, I am not convinced the problem is fixed for good, and I am running a critical application. Any advice would be highly appreciated.
Wim Decorte Posted August 30, 2006 Posted August 30, 2006 hard to say without a full picture, but I would focus on the XSLTs. In my experience FMSA itself, especially on Windows (2003) is very stable. since the URLs that the XSLTs produce don't seem correct it would indicate a problem within that stylesheet.
beverly Posted August 30, 2006 Posted August 30, 2006 hard to say without a full picture, but I would focus on the XSLTs I agree! sometimes it is a missing HTML end tag. Remember that the XSLT is XML and must be valid XML.
Moe Posted August 31, 2006 Author Posted August 31, 2006 (edited) First off, thanks for your replies, but how can this be the XSLT? I'll admit that my code is convoluted, but when the problem comes and goes mysteriously, and then disappears completely when the publishing engine is restarted, how can you blame the code? It's got to be the server, right? Edited August 31, 2006 by Guest
Martin Brändle Posted August 31, 2006 Posted August 31, 2006 Do you use FMSA 7 or 8? FMSA 7 has a well-known problem with document().
Recommended Posts
This topic is 6660 days old. Please don't post here. Open a new topic instead.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now