Error 3021 from M-series report -- REPOSTING

[feeling_better]

Today I woke up with a soft constant beep, beep, ... from my M-series auto after I turned off the machine. I do not know how long it had been beeping; but appears to work with no noticeable change. When I downloaded the data, the process went without errors, but the resulting output was like this

Error Information (2):
Error Number: -2147220088
Error Source: RespironcesEPReports
Error Description: rptComplianceReport - Error in InitData.

Error Information (1):
Error Number: 3021
Error Source: ADODB.Recordset
Error Description: Either B O F or E O F is True, or the current record has been deleted. Requested operation requires a current record.

[I had to insert spaces in 'B O F or E O F' above to allow this posting, without the space, the posting here was crashing! A possible bug in our forum sw]

Report Generation Failure

Printed by RespAR2ErrorHandling, Ver.1.0.191 4/12/2009 7:46

A wild guess: Was the beeping because I had to generate/send one of those FOSQ reports? It is about 11/12 months since I started on cpap. This alert caused some other bug to crash my report? I had only one days data on the card, since I had erased the card yesterday during the data diowload to my pc.

[builta]

Just a thought.

Try disconnecting the electrical connection from the machine. Count to 20, plug it back in. Wait for it to restart and see if it reports any errors.

[-SWS]

Sounds like the erase procedure didn't go right. I'd recommend reformatting the card, as if you were preparing it for a new patient.

Don't know if that card is vulnerable to "delayed writes" by the Windows OS. To be on the safe side, I'd recommend giving the reformatting operation plenty of extra time before pulling the card out. Pull the card out in the middle of an erase or reformatting procedure, and you may end up with a corrupted data card... and perhaps that error message.

[feeling_better]

Sounds like the erase procedure didn't go right. I'd recommend reformatting the card, as if you were preparing it for a new patient.

Don't know if that card is vulnerable to "delayed writes" by the Windows OS. To be on the safe side, I'd recommend giving the reformatting operation plenty of extra time before pulling the card out. Pull the card out in the middle of an erase or reformatting procedure, and you may end up with a corrupted data card... and perhaps that error message.

-SWS, I did erase the card and re-setup just now. But it is unlikely this mornings problem was from an held up delayed write, because the card remained in my notebook for longer than the usual time after I looked at the data yesterday. I would try another card for tonight anyway.

But just now I noticed that this morning when I downloaded two files were written! Once is the normal sleep compliance download, and the other was a FOSQ Test. The pdf from the former was what I had reported at the beginning of this thread. But the FOSQ test had something like the following in the report:

Subscales Score Normal Range Answers
Date: 4/12/2009 7:12:30 AM
F1: Activity Level 1.00 3.34 - 3.88 Q:5
0
Q:14
0
Q:15
1
Q:16
0
Q:22
1
Q:23
1
Q:24
1
Q:25
1
Q:26
1
F2: Vigilance N/A 3.16 - 3.84 Q:6
0
Q:7
0
Q:17
0
Q:18
0
Q:19
0
Q:20
0
Q:21
0
F3: Intimacy N/A 3.84 - 4 Q:27
0
Q:28
0
Q:29
0
Q:30
0
F4: General Productivity 1.00 3.38 - 3.9 Q:1
1
Q:2
1
Q:3
1
Q:4
0
Q:8
0
Q:9
0
Q:10
0
Q:11
0
F5: Social Outcome N/A 3.57 - 4 Q:12
0
Q:13
0
Total Score 5 16.33 - 19.41

I had never seen a FOSQ Test report in any downloads before, and I wonder what triggered the FOSQ test. I do not know if my error/FOSQ test had any correlation -- one triggering the other?

[StillAnotherGuest]

[I had to insert spaces in 'B O F or E O F' above to allow this posting, without the space, the posting here was crashing! A possible bug in our forum sw]

It sure seems that way, since that code should have been able to be posted using

Code: Select all

SAG

[GumbyCT]

Sounds like the erase procedure didn't go right. I'd recommend reformatting the card, as if you were preparing it for a new patient.

Yes, Sounds like a corrupt card or you removed it before the session terminated, (finalized). The software couldn't find the End of File. How long after you woke up did you remove the card?

Trying a known working card is an easy test.

Even if you don't have a card the machine will still work.

[GumbyCT]

Just curious if you are using Viewer or Encore Pro?

[feeling_better]

Sounds like the erase procedure didn't go right. I'd recommend reformatting the card, as if you were preparing it for a new patient.

Yes, Sounds like a corrupt card or you removed it before the session terminated, (finalized). The software couldn't find the End of File. How long after you woke up did you remove the card?

Trying a known working card is an easy test.

Even if you don't have a card the machine will still work.

GumbyCT, Thanks for responding. Please also read my reply to -SWS above of April 12.

First, to answer your next posting, I was using the EncorePro.

I may not have been clear in describing the sequence of events that led to the failure here.

1. The M1 was normally turned off (with the middle button) in the morning. Then I heard the repeating very soft short beeps. [BTW, the beeping was very hard for me to locate, since my machine is at the foot of my bed and the bed covers go over it. I had first gone thru every phone and other gadgets in the room looking for this barely inaudible beeps ] So, the beeps happened before the card was pulled out! It may very well have started some time in the middle of the night.

2. If the card was bad the night before, the machine would have beeped when I inserted the card the previous night. I am familiar with that happening when a bad card is inserted, or if the card is not properly seated.

3. When it was beeping the FOSQ sign on the bottom left was flashing. When there is a problem with the card and beeping, my experience has been that I see the card sign at the top right flashing. So that is why I thought 'FOSQ' compliance report alarm might had something to do with this failure...

4. When I downloaded the data into my pc (EncorePro) the resulting report had that error, and there was a new FOSQ Test report for the first time in about 11 months of my use.

So my guess here is: a. Either FOSQ alarm triggering caused this because of some software bug in the machine, or b. The card might have come unseated from its connector overnight due to vibration, etc, and when the machine wrote data into the card it got corrupted

BTW, this is no longer a problem for me. I usually report these for the possible benefits of others too; if this ever happens to somebody else, then we may be able better guess at the cause.

[GumbyCT]

BTW, this is no longer a problem for me. I usually report these for the possible benefits of others too; if this ever happens to somebody else, then we may be able better guess at the cause.

Good idea.

It is not clear to me exactly what the fix was?

[feeling_better]

It is not clear to me exactly what the fix was?

Gumby, Well, that was because I did not mention the exact fix I reformatted the card using the EncorePro sw, but was using another card for the last couple of days, since I did not want to take a chance of not seeing the data for two days in a row. I would try that old card again at some point.

[GumbyCT]

Well, that was because I did not mention the exact fix I reformatted the card using the EncorePro sw, but was using another card for the last couple of days, since I did not want to take a chance of not seeing the data for two days in a row. I would try that old card again at some point.

And I thought it was me!! You mean there is still hope? for me?

::I was tryin to be nice::

[geopal]

I am getting the same error in Encore Pro 1.8 when I try to report my full report.

I can view Interactive Compliance View (usage per day), but it is not enough.

I am missing all the analysis with apneas, ypopneas. These pages are called "Sleep Therapy Long Term Trend".

Tried to manually print each report but managed only to print the table with daily events per hour and "Patterns of use"

Any suggestions?

Here is a screenshot of the error i am getting

[geopal]

Anyone?

[feeling_better]

Anyone?

Have you tried what was suggested in this thread just before you posted -- erase the card and reinitialize your card with your patient name, use the card the next night and see if you can download the data and view. BTW, your image in the previous post is viewable as a thumbnail only.

[geopal]

Isn't all data erased when downloaded over Encore? After downloading first time, I tried back and received empty results...

Would it make any difference if there are 2-3 more compliances inside?

BTW apologies for the small image. Here is the proper one:

http://img32.imageshack.us/img32/8897/errorj.jpg