Problems, since updating to 3.70A or 3.70B

Pidi

We are using a 2.60F which run without any trouble under the 3.60 technical environment, native database.

Since we updated the whole thing to 3.70A, we got a couple of problems, mainly internal errors and worse performance. We tried the 3.70B about a week later (no one had told us, that there was a 3.70B available), but basicly nothing has changed. 10 - 15% of the users get a internal error 4 in modul 34, when they terminate the client after hours of work - every day! Doesn´t give you a real good feeling ...

Here ist the Error.Log

---

Version=131072
UI LCID=1031
General_AppName=Microsoft Business Solutions-Navision
Main_Intro_Bold=Interner Fehler 4 in Modul 34.

Wenden Sie sich an Ihren H„ndler, wenn Sie Hilfe ben”tigen.

Queued_EventDescription=Internal Error
EventType=NavisionInternalError
P1=Navision
P2=03.70.02.19516
P3=4
P4=34
ReportingFlags=1
FilesToDelete=C:\Dokumente und Einstellungen\s.bos\Anwendungsdaten\navinfo.txt

Besides that the all over performance is about 5% worse than with 3.60, and a search on a non-indexed field (which I know and understand is always slower) is now about 10 times slower, than before. The workaround for that is, to search on non-indexed fields only by using the primary key. OK - we can live with that, but are wondering, what they have changed in the database.

I really wouldn´t like to downgrade, and lose this wonderfull feature, to set breakpoints in advance ...

Does anyone have any idea?

Pidi

fb

You need 'Update 1 for 3.70B'. See item 7 in this list:

http://www.mbsonline.org/forum/topic.asp?TOPIC_ID=12967

ajhvdb

lucky bast... O:) you get an error number with a hotfix solution 8)

Pidi

Perfect ...
thanks a lot for the fast reply.

What a pitty, that my NSC had no solution for this problem.
Would you agree, that the hotfixed version of 3.70B can run at the same time, as the 3.70B itself? That would allow us to update the client during business times, instead of spending another night at the company.

Tanks again

Pidi

Pidi

after asking my NSC now for the hotfix 1 for 3.70B, they told me, that this one is only listed as an update to tax problems for Poland and Russia, and wouldnßt fix any of the mentioned problems.

I do not really believe them ...

Pidi

fb

I think there may be some confusion regarding the names being used: 'Update 1' is not the same as 'Hotfix 1'...

Have your NSC look up article "Update 1 for Microsoft Business Solutions - Navision 3.70 Service Pack B is available (890640)" in the Knowledge Base on PartnerSource.

Pidi

.. after nearly a week, today my NSC confirmed, that they were able to find that hotfix. That fix is a .zip with a couple of files, while half of these files are for SQL and the rest for the native DB. Besides that, there is a CFront.dll for native mode, which should be part of the SDK, so we don´t need it as well.

Since we are still using the Native DB, the files fin.exe and server.exe seem to be the only files, we should replace ...?

For all of such fixes it would be very helpfull, if the readme-file could recommend, if the clients can be updated one by one, so you get mixed clients during some period, or if all files have to be updated at once while the server is down. Unfortunately the disclaimer of that readme is longer, than the technical hints - well, actually there are non ...

Pidi