1.2.9 x86 Upgrade Issue

[TroutfaceKilla]

Hi,
I have just tried to upgrade our 1.2.1 installation on a 32 bit W2K3 server to 1.2.9. but the service wont start.
Db is sql2005.
Looks like there's a db issue. Any ideas how to proceed?

C:\NetXMS\bin>nxdbmgr check
NetXMS Database Manager Version 1.2.1

Checking database (excluding collected data):
* Checking zone objects...                                            [PASSED]
* Checking node objects...                                            [PASSED]
* Checking interface objects...                                      [PASSED]
* Checking network service objects...                                [PASSED]
* Checking cluster objects...                                        [PASSED]
* Checking template to node mapping...                                [PASSED]
* Checking object properties...                                      [PASSED]
* Checking event processing policy...                                [PASSED]
Database doesn't contain any errors
Database check completed

C:\NetXMS\bin>nxdbmgr upgrade
NetXMS Database Manager Version 1.2.9

Upgrading database...
Upgrading from version 265 to 266
SQL query failed ([Microsoft][SQL Native Client][SQL Server]Incorrect syntax nea
r the keyword 'WHERE'.):
CREATE INDEX idx_event_log_root_id ON event_log(root_event_id) WHERE root_event_
id > 0
Rolling back last stage due to upgrade errors...
Database upgrade failed

C:\NetXMS\bin>

Thanks

Heres the debug output:
C:\NetXMS\bin>netxmsd -D3
Using configuration file "C:\NetXMS\etc\netxmsd.conf"
[14-Nov-2013 16:30:23.424] Debug callback set for DB library
[14-Nov-2013 16:30:23.424] Database driver "odbc.ddr" loaded and initialized suc
cessfully
[14-Nov-2013 16:30:23.487] Successfully connected to database netxms_db@localhos
t
[14-Nov-2013 16:30:23.487] Your database has format version 265, but server is c
ompiled for version 291
NetXMS Core initialization failed

thanks

[alk]

Check this topic: https://www.netxms.org/forum/general-support/upgrade-error-from-265-to-266/msg10052/#msg10052