Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - par.abrahamsson

#1
Solved or, at least we came through the problem. We deleted the data in the tables reporting the errors and then the db-upgrade worked.
#2
Hi! After upgrade from 2.0 to 2.1 (Windows Server 2008 R2 with SQL Server 2008 R2) the services wont start and when reading logs it's because the DB is in wrong version.

Trying to rung dbmbgr upgrade ends in this:

Upgrading database...
Upgrading from version 410 to 411
Converting table tdata_25: failed
Rolling back last stage due to upgrade errors...
Database upgrade failed

#3
Sorry to disturb once again but the update worked with 1.2.1, not the most recent version.
#4
Thank a lot! Works fine. No need for 64-bit for the moment.
#5
New clean install with 1.2.2 and the Alarm Viewer still crashes.
#6
I don't think this is solved. We're migrating to new hardware and I just installed both server, databas (empty) and client tools on a new server and the Alarm Browser crashed there too.
#7
Is this solved? We still cant use our Alarm Browser. If it's solved and should work in 1.2.1 I'll have to investigate more on our side.
#8
One reason to use the old Alarm Viewer is the fact that it can log in automatically. We use it to display the alarm status in displays around our office and the computer that runs the Alarm Viewer is set to automatically restart every morning and make an automatic login and because of that we never have to touch it.

And yes, we have the same crash-problem since the last upgrade.