Hi, Everytime I close Navision I get this error: ------------ fin.exe has generated errors and will be closed by Windows. You will need to restart the program. An error log is being created OK-button --------------- And the next time I start up Navision, it has to go the the process of ‘recovering list of free blocks…’ The fdb is highly modified, so it will be hard to pinpoint I think, but maybe if someone has some general things for me to look for… Thanks for any help in advance, Kelly
Just a little more explanation, please … Is it only on one station or on all the stations ?
I am running single user from my workstation. The file is on a server but I am opening directly not as a service. I run windows 2000. I have several versions of Navision Financials/Attain on my laptop, some of the fdb’s are on servers, some are on my hard drive, but this is the only one that does this. Hope that helps, Thanks Kelly
I’m guessing here, but could it be some of the code in the LoginEnd trigger in codeunit 1?
that’s what I was thinking… trouble is I didn’t write those modifications, so I attacking this almost as blind as you. Guess I’ll have to remove them one at a time until the problem goes away! Thanks!
Hi Kelly, If I got u right, u r trying to open a database(x.fdb) file residing on the Server from your workstation(not the same m/c where the database is residing) as a local database file. File–>Database–>Open, selecting the path. You can’t open a database not residing on your m/c thru’ this method. you can either connect as a “Service”(In u r case u rn’t doing that). The other thing is that your database(NS) is split into multiple-files on different drives. This could be one reason. Regards[^]
Although I agree that there are good reasons (performance being one) why you will not want to run databases on network drives, there is nothing that prevents you from doing that as long as you have the necessary permissions on that drive. - Jens
You don’t have to remove the modifications one by one - for a start at least. First, export codeunit 1 in FOB format, and import a new unmodified codeunit 1 from a clean database. If the error persists, then the problem lies elsewhere, if the error goes away, then import the codeunit 1 you exported before, and go hunting. I would look to the LoginStart and LoginEnd triggers first.
quote:
Originally posted by Jens Rainer
Although I agree that there are good reasons (performance being one) why you will not want to run databases on network drives, there is nothing that prevents you from doing that as long as you have the necessary permissions on that drive. - Jens
I open databases on the network drive all the time as single user from my workstation. This has never been a problem. I cannot keep all my clients databases on my hard drive, I would run out of room. I don’t worry about performance too much because I am the only one on the database and I am doing development, so I don’t want anyone else on anyway.
I will test with a clean object to see if the error persists. I already commented out the modifications in the loginstart & loginend triggers and still the error happens. But I did find that if I login, do nothing and close Navision, I don’t get the error. I will try the clean object and go from there. Thanks everyone!
Could it be that Navision is trying to store the ZUP file on a network drive that is inaccessible?