Leave feedback
  • Question

    StreamServer wont start after upgrade from 5.6.0 to 5.6.1 build 383

Enter a new topic
  • Mijno van der Ploeg Mijno van der Ploeg
    0 likes 1574 views

    Hi,

    We upgraded a local (VMWare) environment from version 5.6.0 to 5.6.1 build 383. The upgrade manual wasn't usable (it isn't possible to import a domain from an older version) so we did a deinstallation of the old version followed by a new installation.

    We created a new: ser, runtime repository, web content repository, DB+ repository and archive repository. We imported the Runtime Repository and Web Content Repository.

    So far so good. We created and succesfully started a service gateway application and two small streamserver applications (one statusmessenger and one attachments (preformatin in) application).

    However the main application doesn't start. We do not get a clear error message.

    We do see one error message in the platform.log:

    1215 104720 (0148) 1 ODBC: Failed executing: [1]: SQL State = "23000", Error Message = "[STRS][ODBC SQL Server Wire Protocol driver][Microsoft SQL Server]Cannot insert duplicate key row in object 'dbo.ServiceKey' with unique index 'IX_uniqueservicekeyvalue'. The duplicate key value is (82ce8170-f1b4-422c-9d8d-d6fdc49cb91a, ServiceURI, http://schemas.streamserve.com/uid/service/scfinfoservice/1.0/1C81C3FD-2FB4-A24B-98E6-E17F60F3B21D).", (Native Error = 2601); [2]: SQL State = "HY008", Error Message = "[STRS][ODBC SQL Server Wire Protocol driver][Microsoft SQL Server]The statement has been terminated.", (Native Error = 3621)

     

    Has anyone got an idea what could be wrong?

     

     

    Monday 15 December, 2014

    Attached files

  • Hervé BIN Hervé BIN Partner
    0 likes

    Hello,

     

    do you find a solution, because I have the same problem... :(

     

    Thank you

    Friday 10 April, 2015
  • Mijno van der Ploeg Mijno van der Ploeg
    0 likes

    Hi yes i did discover the bug that was causing this. In our case the problem was caused by the service enabled message in the main project. If you have this in your project just select the option: None as a 'base input connector to' (or something like that) on the runtime (service) settings of this message.

    This particular version of streamserve has got a bug that occurs if this option is anything else than none.

    This is solved in the latest build.

     

    I hope this will help you.

     

    Kind regards,

    Mijno

    Saturday 11 April, 2015