Database Conversion after Installing Critical Update for SP2

ta5

I made (in a test environment) the upgrade according to

http://www.mibuso.com/forum/viewtopic.php?t=13152


When the DB is opened the next time with new finsql.exe, I had to confirm that I want to convert the db.
My questions:

What is beeing converted? Why is fin.exe also in the Hotfix? (It is supposed to be a sql thing only)

Thanks in advance.
Thomas

Phenno

Not sure what that convert fully do (there is some flags in database that says what version of database is).
One is sure, you cannot open converted SP2 (or every SP2) db with non-SP client. And, I talk about executables.

I think that there is no such non-compatibility between SP1 and SP2.

ta5

By the way:
Has somebody experience with this Critical Update?

It seems that synchronization does not work anymore. For example I add a new sql server login in management studio and then try to add a new db login in navision. I get an error concerning the syncronization. When I switch back to the original executables from SP2 it works like a charm. This makes no sense to me ](*,) ](*,)

Regards
Thomas

Phenno

ta5 wrote:

By the way:
Has somebody experience with this Critical Update?

It seems that synchronization does not work anymore. For example I add a new sql server login in management studio and then try to add a new db login in navision. I get an error concerning the syncronization. When I switch back to the original executables from SP2 it works like a charm. This makes no sense to me ](*,) ](*,)

Regards
Thomas

There are few threads here about that issue.

ta5

which ones do you mean?
(sorry, I think I have read them without any hint to this problem)

nunomaia

I have installed this critical update and I haven’t any problems

ara3n

I ran into the same issue with the hotfix on sql 2005. The only option was synch each single user. I guess we have to wait for SP3.

ta5

The option "Synchronize Single User" is always disable in my test installation. What's the reason?

Sorcerer

first you have to open the database / windows logins and have to mark at least one user before the synchronize each user function is reachable.

ta5

now it works.
thx

Layla

Well I have tried to add new login through Ent. Manager and than to synchronize all logins (I'm using Navision 4.0SP2 with hotfix with SQL2000 both non SP and SP4). Now situation is as folows:

If you add a user (login) that starts with a letter before S(Superuser) synchronization proces for all user fails (SQL Error 4604), but if you add a user (login) that starts with a letter AFTER S(Superuser) synchronization process is successful.
Database has been migrated from 3.60 to 4.0SP2. Now this is very funny behavior. Anybody has any idea about the possible cause?

Phenno

few links where you can find more informations about differences in sinchronization SP1 => SP2+ (and problems that comes with it.).

http://dynamicsuser.net/files/12/docume ... y3851.aspx
http://dynamicsuser.net/forums/thread/2442.aspx

ta5

Phenno wrote:

http://dynamicsuser.net/files/12/docume ... y3851.aspx

Very helpful doc!
Was this also published on partnersource? I have not seen it before and even if I have a search now, I dont't find it on partnersource.

Phenno

ta5 wrote:

Phenno wrote:

http://dynamicsuser.net/files/12/docume ... y3851.aspx

Very helpful doc!
Was this also published on partnersource? I have not seen it before and even if I have a search now, I dont't find it on partnersource.

I, really, don't know.