Important Notice from AspDotNetStorefront
It is with dismay that we report that we have been forced, through the action of hackers, to shut off write-access to this forum. We are keen to leave the wealth of material available to you for research. We have opened a new forum from which our community of users can seek help, support and advice from us and from each other. To post a new question to our community, please visit: http://forums.vortx.com
Results 1 to 4 of 4

Thread: Difference between ML7.0.1.0 ML 7.0.2.5

  1. #1
    Nilkanth is offline Junior Member
    Join Date
    May 2007
    Posts
    12

    Default Difference between ML7.0.1.0 ML 7.0.2.5

    Hello,

    I have ML 7.0.1.0 with code customization and now have updated code to ML 7.0.2.5 version. For some reasons the database the database does not work with the ML 7.0.2.5.

    Anyone knows what are differences between 7.0.1.0 ML 7.0.2.5 in term of database structure. Are there additional table compare to 7.0.1.0 ML version.

    Thank you very much,

    Nil

  2. #2
    ASPAlfred is offline Senior Member
    Join Date
    Nov 2007
    Posts
    2,244

    Default

    I can't tell you exactly the difference between those two. ML 7.x is 4+ years now, so it's been a while. However, if you can tell us the errors, we'll see if we can help.

  3. #3
    Nilkanth is offline Junior Member
    Join Date
    May 2007
    Posts
    12

    Default

    Hi,

    Thanks for reply,

    I have upgrade the code and now gets below error message.

    Server Error in '/' Application.


    Could not find stored procedure 'aspdnsf_getEventHandler'.
    Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

    Exception Details: System.Data.SqlClient.SqlException: Could not find stored procedure 'aspdnsf_getEventHandler'.

    Source Error:

    An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

    Stack Trace:

    [SqlException (0x80131904): Could not find stored procedure 'aspdnsf_getEventHandler'.]
    System.Data.SqlClient.SqlConnection.OnError(SqlExc eption exception, Boolean breakConnection) +2030802
    System.Data.SqlClient.SqlInternalConnection.OnErro r(SqlException exception, Boolean breakConnection) +5009584
    System.Data.SqlClient.TdsParser.ThrowExceptionAndW arning() +234
    System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) +2275
    System.Data.SqlClient.SqlDataReader.ConsumeMetaDat a() +33
    System.Data.SqlClient.SqlDataReader.get_MetaData() +86
    System.Data.SqlClient.SqlCommand.FinishExecuteRead er(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) +311
    System.Data.SqlClient.SqlCommand.RunExecuteReaderT ds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async) +987
    System.Data.SqlClient.SqlCommand.RunExecuteReader( CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result) +162
    System.Data.SqlClient.SqlCommand.RunExecuteReader( CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method) +32
    System.Data.SqlClient.SqlCommand.ExecuteReader(Com mandBehavior behavior, String method) +141
    System.Data.SqlClient.SqlCommand.ExecuteReader(Com mandBehavior behavior) +70
    AspDotNetStorefrontCommon.DB.GetRS(String Sql) +296
    AspDotNetStorefrontCommon.AspdnsfEventHandlers..ct or() +104
    AspDotNetStorefront.Global.6boFjG62I() +710
    AspDotNetStorefront.Global.cnLP9Is5q(Object , EventArgs ) +413
    AspDotNetStorefront.Global.Application_BeginReques t(Object sender, EventArgs e) +68
    System.Web.SyncEventExecutionStep.System.Web.HttpA pplication.IExecutionStep.Execute() +148
    System.Web.HttpApplication.ExecuteStep(IExecutionS tep step, Boolean& completedSynchronously) +75

  4. #4
    ASPAlfred is offline Senior Member
    Join Date
    Nov 2007
    Posts
    2,244

    Default

    You have to make sure that the 'upgrade to latest' script has been executed against your DB also. You're missing that stored proc that's why you're getting the error.