When I attempt to exeute categorylist.aspx from the web browser I get the following error
I have checked the DB tables dbo.CSK_Store_Category, dbo.CSK_Store_Product and the categories and products are listed. However, the dbo.CSK_Store_Product_Category_map table only has a record for the default product and category that comes with the package.
Running as localhost Umbraco 4.0.2.1, Commerce for Umbraco beta 1.0 , IIS7, SQL Server Express 2005, Vista business
Server Error in '/' Application.
There is no row at position 0.
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.IndexOutOfRangeException: There is no row at position 0.
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.
Commerce for Umbraco problem
I am new to Umbraco so please be patient.
When I attempt to exeute categorylist.aspx from the web browser I get the following error
I have checked the DB tables dbo.CSK_Store_Category, dbo.CSK_Store_Product and the categories and products are listed. However, the dbo.CSK_Store_Product_Category_map table only has a record for the default product and category that comes with the package.
Running as localhost Umbraco 4.0.2.1, Commerce for Umbraco beta 1.0 , IIS7, SQL Server Express 2005, Vista business
Server Error in '/' Application.
There is no row at position 0.
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.IndexOutOfRangeException: There is no row at position 0.
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:
I have found the solution to this problem
is working on a reply...