Yes, i've checked the forum. Couldn't find a similar post.


Since the first day of WF we have this 'odd' problem.
We have a -correct- (!!!) master file. It's works fine.

When making a temporary hold, and another one. And then a match etc.etc.
In other word, the 'chain' get longer.

We ( sometimes ! ) get "error parsing Master file ....... " while trying to edit or add a part of the 'chain'.

We know this is because the editor thinks is absolutely neccesary to process all requests (!?)
It shouldn't, there are queries in the chain running 30 min+.
But even if it did, it should just take a long time.

No, it seems to get an 'time-out', resulting in an unfitting error "error parsing Master file".

Before you all start asking questions:
This can also be reproduced without a 'chain'.
Right now it's very 'busy' on the Datawarehouseserver. I now get this error with just one "report".
Or even when making a define over the master file.
We've increased the "Web Componnent" "connection Timeout (seconds)".
That actually helps, a bit. But it doesn't solve the problemen.

Also, adding a xretrieve = off works.

But this can not be designer behaviour...


My only question:
Does this sound familiar to anyone? Any clues.

We're sure ( an so is the IBI-Sales guy ) that it's a time-out of sort that causes this error.
Once again : there is nothing wrong with the master file it self, handcoding works fine.

Greets,

This message has been edited. Last edited by: Kerry,

Dave,

I would recommend raising a Tech Support case on this.

T

Dave,

Sorry to say, but is is the way the product is designed.
You're talking about DevStudio here. If you build a chain of things in a fex, then when you try to open a certain part of that chain, then DS has to process everything before that point to come up with the correct results. Which is why XRETRIEVAL OFF works fine. In my humblest of opinions DS should actually do the XRETRIEVAL automatically when processing 'for the nonce' so to speak. Instead it probably does the processing with a recordlimit ... I would follow T's advice and ask for a settable (or selectable) solution within DS.

@Tony A

Tech support has already been discussed with out IBI-contacts.

@GamP
Well, we've acually automated it.
By checking the fexname ( ADHOCRQ ) it possible to see wether it's run by de DS or via the website. Good way to seperate development from production. But even with xretrieval it does not always work.

Thanks so far.

But I'm still wondering. Does nobody else have this?
And why do we have a choice 'live data' or 'test data' if it's still really processed.
Again, with a chain, I get it.
But with the -first- report over a Masterfile, I don't. Parsing shouldn't need the real database to find out which fields are available...