We are getting the following error in B.I. Dashboard and self service very occasionally:

ERROR: -12: Server disconnected, cause 32050 Eda state -12

We get this error occasionally in ReportCaster:

Error connecting to the WebFOCUS Reporting Server EDASERVE: EDA SQL STATUS (-12)

Short of opening a case (which I will do shortly), has anyone else been experiencing this kind of error?

I searched for "32050" on Tech Support and only came up with one relevant document - (Case: 11152079) and the solution was

quote:

The temp directory was full therefore there was no room to write the
FOCSORT file. Customer deleted files from the EXPORT HOME directory
and FOCSORT is now has room. The problem reported is no longer occurring

This is not the issue on our Windows server - I checked and the temp directory (D:\ibi\WebFOCUS53\temp) contains very few files and there's lots of space available on the drive.

Francis

When you say you get this in caster: is it when you are running a batch job or when you are using the casters user interface to set up jobs.

When using the interface Caster is very tempremental in that it loses the authenication token very often. I don't know if this is -12 problem but I will check next time.

This kind of intermittent problem may be down to network timing issues in that when busy it might time out.

Regards

John

John, it occurs when running an RC schedule.

I also suspect that the error may be due to a network issue. If this is the case it's going to be difficult to resolve...

Francis, I had a similar thing happen to me a couple of weeks ago when I was running a large fex under WF 5.3. It seemed to me that when it was a big fex, a simple error resulted in this -12 thingy. I was able to solve the problem by doing one of two things:

1 - Break the request down to small chunks and unit test each chunk.
2 - Run the request using 7.1 or 7.6.

It turned out that I was using a parameter that was not assigned a value. A very simple error, but it just kept giving me a -12. 7.6 showed me the "real" error in seconds.

D,

The problem occurs intermittently, with small and large fexes. Hitting refresh mostly works, which suggests we're not having exactly the same issue as you were.

Thanks,

32050 is one of those catch all errors, the one chosen when there is no specific reason coded for. The label for the code is FATAL_REMOTE_ERR (I know that doesn't tell you much). It is likely that the error is on the server side, not the client, so check the server edaprint log the next time you see it.