I have this rather urgent problem I asked about on the "common" discussion list yesterday, but having got no reply yet I have to take it to the next level .

You see I think I have been working with a damaged or malfunctioning copy of OI 3.3 for a long time, also distributing copies to users. I may have managed to restore the system to normal now, but I don't know for sure. There is one remaining irregular feature in the system that worries me. I need your help to find out if it's harmless or not. I simply cannot afford letting a malfunctioning system loose on our 150 users.

The symptom that troubles me is that Rebuild System Index finishes with an error message. The message is just "FS" (no number). Does that mean that

(1) some error occurs,

(2) somebody (at RevSoft?) in their programming forgot to concatenate the error number, and

(3) the error condition is rather special because otherwise lots of people would have got it too?

There are a few more details on the symptoms I've managed to get rid of, etc, here.

- Oystein -

Øystein Reigem, Humanities Information Technologies, Harald Haarfagresgt 31, N-5007 Bergen, Norway. Tel: +47 55 58 32 42. Fax: +47 55 58 94 70. E-mail: [email protected]

Hi Oystein,

AFAIK an 'FS' error message with no code indicates some sort of problem with a file at the OS level.

For example it could be because of something like a repository entry refering to a missing .BMP or .DLL file.

For some reason I think @File.Error gets set which leads to the message (but of course it's not a LH filing error hence no FS number). I think Revsoft fixed this in a later release but I could be mistaken.

Try running an AppBackup on your system and see if it gives you any errors of this type so you can see which repos entity is causing this.

[email protected]

Sprezzatura Ltd

World Leaders in all things RevSoft

Carl,

AFAIK an 'FS' error message with no code indicates some sort of problem with a file at the OS level. For example it could be because of something like a repository entry refering to a missing .BMP or .DLL file.

For some reason I think @File.Error gets set which leads to the message (but of course it's not a LH filing error hence no FS number). I think Revsoft fixed this in a later release but I could be mistaken.

I have tried to upgrade to 3.4 and 3.5, but at least in 3.5 I get the "FS" message. But the version I upgraded was the one before I got rid of the other symptoms (LH Verify, "ATX*…$PUBLIC", etc). Should I try to upgrade my current, presumably cleaner version? (The one where the only remaining problem seems to be the "FS" message.)

I have two apps REGIMUS and WINR that inherit from SYSPROG by default. (WINR is very small and fairly new - just a few experiments.) I now did something new: I tried to run Rebuild System Index from each of the apps. Earlier I've just run it from REGIMUS. I only get the "FS" message in REGIMUS. Is that significant?

Try running an AppBackup on your system and see if it gives you any errors of this type so you can see which repos entity is causing this.

I ran AppBackup on each of the three apps REGIMUS, WINR and SYSPROG. In REGIMUS and WINR I found a few BMP and GIF entities where the image files had been moved/deleted. I just deleted the entities because I don't need them at all. That made no difference. I still get "FS" in REGIMUS. (In WINR I get no "FS" message, but as I said before I've only run Rebld Sys Ix in REGIMUS until now so I don't know if I'd got it before deleting entities.)

AppBackup'ing SYSPROG produced this list:

Code - Detail

FS105 - OI2NOTES.DLL

FS105 - BMPS\CONN.ICO

FS105 - BMPS\DATASET.ICO

FS105 - BMPS\MSG.ICO

FS105 - BMPS\PATTERN.BMP

FS105 - BMPS\QUERY.ICO

FS105 - BMPS\sqlmgr.ico

FS105 - WINEXE\oicgi

If you see something worrisome her you'll have to advice me on how to clean up. But since there is no "FS" message in SYSPROG I guess we can forget about it?

Any other suggestions?

- Oystein -

PS. Did you (you and Andrew) get my mail (today and yesterday)?

Oystein,

The symptom that troubles me is that Rebuild System Index finishes with an error message. The message is just "FS" (no number).

This can happen if Set_FSError is called but @file.error has not been set up. It can also happen if an MFS fails an operation that is called from a BASIC+ THEN/ELSE construct (such as OPEN, READ, and WRITE) without setting @file.error.

Cameron Purdy

[email protected]

Cameron,

This can happen if Set_FSError is called but @file.error has not been set up.

I have never used Set_FSError in my programming. The only Set_FSError in my source code is in Exec_Sql (written by you?).

It can also happen if an MFS fails an operation that is called from a BASIC+ THEN/ELSE construct (such as OPEN, READ, and WRITE) without setting @file.error.

I use no MFS's - except SI of course.

So where do I go from here?

- Oystein -

View this thread on the Works forum...