locked
Setup Issue of Durable Timer sample RRS feed

  • Question

  • Hi all,

    after executig of setup of DurableTimer sample, the sample will fil with error: Cannot find Stored Procedure "CreateLockOwner".

    This SP does not exist inf DefaultSampleStore database.
    However the SP can be found in InstanceStore database.

    1. Can you provide the SQL-script which create all required staffs in the DB.
    2. Why WF doesn't provide just one database which can be used in all scenarios?

    Thanks

    Damir

    Saturday, October 24, 2009 7:42 PM

Answers

  • The sql instancestore scripts are in the following folders :
    C:\Windows\Microsoft.NET\Framework64\v4.0.21006\SQL\en

    There are .cmd files in the following folder that seem to work :
    WF_WCF_Samples\WF\Basic\Persistence\SQLStoreExtensibility\CS

    You will have to use a connection string similar to that one :
    Data Source=.\SQLExpress;Initial Catalog=InstanceStore;Integrated Security=True;

    Hope this helps!

    Karol Deland, Québec
    Sunday, October 25, 2009 2:50 AM
  • Thanks Carol for your feedback.

    Unfortunately my problem was caused by using of these scripts, because they have generated invalid database.
    I assumed that some of them are buggy. However, my problem was that I for some reason mixed scripts from Beta 1 and beta 2.

    After removing all and installing again all worked fine.

    Damir

    Wednesday, October 28, 2009 12:27 PM

All replies

  • The sql instancestore scripts are in the following folders :
    C:\Windows\Microsoft.NET\Framework64\v4.0.21006\SQL\en

    There are .cmd files in the following folder that seem to work :
    WF_WCF_Samples\WF\Basic\Persistence\SQLStoreExtensibility\CS

    You will have to use a connection string similar to that one :
    Data Source=.\SQLExpress;Initial Catalog=InstanceStore;Integrated Security=True;

    Hope this helps!

    Karol Deland, Québec
    Sunday, October 25, 2009 2:50 AM
  • Thanks Carol for your feedback.

    Unfortunately my problem was caused by using of these scripts, because they have generated invalid database.
    I assumed that some of them are buggy. However, my problem was that I for some reason mixed scripts from Beta 1 and beta 2.

    After removing all and installing again all worked fine.

    Damir

    Wednesday, October 28, 2009 12:27 PM