Classic client (SQL Server) object import/export hangs

dleroux

Has anyone run into this? Two days ago I imported a fob with a new (modified) report to the client's DB with no problems. Naturally once they had it they found a need for some minor formatting tweaks. So yesterday when I tried to import the tweaked report, finsql just hung after opening the dialog box showing that there was one object to import. It hangs trying to export objects as well - and both import and export hang on text as well as fob exports. In all cases it can recognize how many objects are involved, but I have to cancel the action and let Windows close the app (finsql).

The windows event log (my ususal friend for oddness) has been less than helpful. My bigger hammer (reboot the server) also proved ineffective. So, if anyone has any ideas, or if I've just missed the right magic search terms please throw me a bone.

](*,)

Thanks

vaprog

Here are the things I would do:

• Try with a clean zup
• wait for a long time
• try with a different windows profile
• restart SQL Server (What server did you restart?)
• check the SQL database

I strongly suspect that some now unavailable path was used the last time import/export was performed. Windows can be very patient in searching for some vanished drive or network connection. So 2nd and 3rd options are most likely to work.

davmac1

Any possibility you developed on a higher NAV version than the customer version. NAV can introduce new features that are not compatible with older versions.
Have you looked at the text of the object you successfully imported versus the text of the object that is hanging?
You might find a new line that is not part of the customer NAV version.

dleroux

Sorry for the delay, but it looks like it was indeed a versioning issue.