5 replies to this topic

[Marius Coetzee]

I'm in desperate need for anybody who can help me with this problem.
We've just converted a client from ISAM to SQL 7. Afterwards we had a problem with multikeyed files being auto-seq and SQL 7, which ProIV support solved with a patch.

After working fine for a day, some clients got an error writing to a file, while others had no problems.

Before we could start working on the problem we started to fail accessing the client's main menu. It comes up with the error: '001 - INVALID FUNCTION NAME - %1'. (There is no %1 function.) Thus far we've gathered that it only happen in functions where a (SQL) file is being accessed. In the ProIV Service Manager the process stays open with the message 'SQL CALL IN PROGRESS'. There is also another unknown process hanging here with the same message but we're unable to kill it. I don't know if this hanged function is causing our problem as I'm not allowed to reboot the server to kill the process.

If anybody got any help they can give me on this error it will be much appreciated - you can write it off as your good deed for the day.

I'm also waiting for ProIV support to come back to me on this problem.

Regards,

Marius

[Joseph Serra]

I believe the %1 is just the parameter where the function name should be. If you refer to the manual on how MSG works with % parameters, you will see that it is a way of passing parameters into an error message.

I am not sure why the parameter is not being filled in though...

[jcduym]

Indeed this is the Global Error Message 001 as defined in native Pro-IV. Seems like you are able (haven't a clue why) to start a function without supplying the function-name, or that it is blanked off while executing. This is possible: you can change @FUNCT while a function is executing. Used of old to create environment dependent help messages.

Hope gives you fresh ideas.

Jan

[Marius Coetzee]

Thanks Joseph and Jan for your reply.

I understand how MSG works - I found that I'm not using any. Even when I create a File Browser using Developer Studio and press the window key on the key field I get the error. Thus my theory that this problem only occurs on SQL files (tables).

I tested this by creating an ISAM file and a SQL file (table). I then used DS's File Browser Wizard to create a functions for both. Accessing the ISAM caused no problems, but I still got the error on the SQL file (table)...

I had a look at the ODBCs and created the attached trace. Otherwise I tried re-installing ProIV, rebooted the machine and killed everybody off SQL and ProIV - Currently I'm not a very well liked person and must find an answer before I'm killed.

Regards,

Marius the helpless

Attached Files

•  SQL.LOG   28.01KB   156 downloads

[jcduym]

Hi,
I did not really expect you to be using the message in your function: it is one of the messages in native for Pro-IV itself. What I find suspect about it is that it is the first global message. Could even be that the (internal) error does not have a number and that it defaults to the first! Then you DO have a bug.

In your trace there are a lot of 'return code 100 (SQL_NO_DATA_FOUND)' entries towards the end. Could it be that your database is failing? Were these valid results? Or are these blanking off the function name?

Suggest you run a fairly high level Pro-IV diagnostic trace on the C-ISAM and SQL case and compare the two. Look for blanks in the SQL case. Difficult to suggest which level: you will have to experiment here. This can give you a clue on what is goining on.

Jan

[Marius Coetzee]

Jan,

I send this problem off to ProIV support and after they’ve managed to get hold of me they solved my problem very promptly – before I could test anything you suggested.

The ProIV technical guys found out that the problem wasn’t a ProIV problem, but something external. As I understand it the error generated was so obscure that ProIV did in fact default to the first error message as you’ve mentioned, but it wasn’t a ProIV bug but a MS SQL 7.0 bug. They were so kind as to locate the patch and install it for me.

Luckily my database wasn’t failing.

Thanks for everybody’s help,

Marius