Demo site down

Posted: August 21, 2018 at 6:38 AM Quote #210835
Hello,

After upgrade demo store to 4.1, we noticed this error many times.


Here is error screen shot: http://prntscr.com/kl6po2

Complete error message:

An unhandled exception occurred while processing the request.
SqlException: The multi-part identifier "t3.__RowNumber__" could not be bound.
The multi-part identifier "t3.__RowNumber__" could not be bound.
The multi-part identifier "t2.__RowNumber__" could not be bound.
The multi-part identifier "t2.__RowNumber__" could not be bound.
The multi-part identifier "t1.__RowNumber__" could not be bound.
The multi-part identifier "t1.__RowNumber__" could not be bound.
The multi-part identifier "t.__RowNumber__" could not be bound.
The multi-part identifier "t.__RowNumber__" could not be bound.
The multi-part identifier "t.AllowComments" could not be bound.
The multi-part identifier "t.CreatedOnUtc" could not be bound.
The multi-part identifier "t.EndDateUtc" could not be bound.
The multi-part identifier "t.Full" could not be bound.
The multi-part identifier "t3.AllowComments" could not be bound.
The multi-part identifier "t.LanguageId" could not be bound.
The multi-part identifier "t.LimitedToStores" could not be bound.
The multi-part identifier "t.MetaDescription" could not be bound.
The multi-part identifier "t.MetaKeywords" could not be bound.
The multi-part identifier "t.MetaTitle" could not be bound.
The multi-part identifier "t.Published" could not be bound.
The multi-part identifier "t.Short" could not be bound.
The multi-part identifier "t.StartDateUtc" could not be bound.
The multi-part identifier "t.Title" could not be bound.
The multi-part identifier "t1.Id" could not be bound.
The multi-part identifier "t1.AllowComments" could not be bound.
The multi-part identifier "t1.CreatedOnUtc" could not be bound.
The multi-part identifier "t1.EndDateUtc" could not be bound.
The multi-part identifier "t1.Full" could not be bound.
The multi-part identifier "t1.LanguageId" could not be bound.
The multi-part identifier "t1.LimitedToStores" could not be bound.
The multi-part identifier "t1.MetaDescription" could not be bound.
The multi-part identifier "t1.MetaKeywords" could not be bound.
The multi-part identifier "t1.MetaTitle" could not be bound.
The multi-part identifier "t2.Id" could not be bound.
The multi-part identifier "t1.Published" could not be bound.
The multi-part identifier "t3.CreatedOnUtc" could not be bound.
The multi-part identifier "t1.Short" could not be bound.
The multi-part identifier "t2.AllowComments" could not be bound.
The multi-part identifier "t3.EndDateUtc" could not be bound.
The multi-part identifier "t3.Full" could not be bound.
The multi-part identifier "t2.EndDateUtc" could not be bound.
The multi-part identifier "t2.Full" could not be bound.
The multi-part identifier "t3.LanguageId" could not be bound.
The multi-part identifier "t1.StartDateUtc" could not be bound.
The multi-part identifier "t2.LanguageId" could not be bound.
The multi-part identifier "t2.LimitedToStores" could not be bound.
The multi-part identifier "t1.Title" could not be bound.
The multi-part identifier "t3.LimitedToStores" could not be bound.
The multi-part identifier "t2.MetaKeywords" could not be bound.
The multi-part identifier "t3.MetaDescription" could not be bound.
The multi-part identifier "t2.MetaTitle" could not be bound.
The multi-part identifier "t3.MetaKeywords" could not be bound.
The multi-part identifier "t2.Published" could not be bound.
The multi-part identifier "t2.Short" could not be bound.
The multi-part identifier "t3.MetaTitle" could not be bound.
The multi-part identifier "t2.StartDateUtc" could not be bound.
The multi-part identifier "t2.Title" could not be bound.
The multi-part identifier "t3.Published" could not be bound.
The multi-part identifier "t3.Short" could not be bound.
The multi-part identifier "t3.StartDateUtc" could not be bound.
The multi-part identifier "t3.Title" could not be bound.
Nop.Web.Framework.Infrastructure.Extensions.ApplicationBuilderExtensions+<>c.<UseNopExceptionHandler>b__1_1(HttpContext context) in ApplicationBuilderExtensions.cs, line 85

Stack Query Cookies Headers
SqlException: The multi-part identifier "t3.__RowNumber__" could not be bound.
The multi-part identifier "t3.__RowNumber__" could not be bound.
The multi-part identifier "t2.__RowNumber__" could not be bound.
The multi-part identifier "t2.__RowNumber__" could not be bound.
The multi-part identifier "t1.__RowNumber__" could not be bound.
The multi-part identifier "t1.__RowNumber__" could not be bound.
The multi-part identifier "t.__RowNumber__" could not be bound.
The multi-part identifier "t.__RowNumber__" could not be bound.
The multi-part identifier "t.AllowComments" could not be bound.
The multi-part identifier "t.CreatedOnUtc" could not be bound.
The multi-part identifier "t.EndDateUtc" could not be bound.
The multi-part identifier "t.Full" could not be bound.
The multi-part identifier "t3.AllowComments" could not be bound.
The multi-part identifier "t.LanguageId" could not be bound.
The multi-part identifier "t.LimitedToStores" could not be bound.
The multi-part identifier "t.MetaDescription" could not be bound.
The multi-part identifier "t.MetaKeywords" could not be bound.
The multi-part identifier "t.MetaTitle" could not be bound.
The multi-part identifier "t.Published" could not be bound.
The multi-part identifier "t.Short" could not be bound.
The multi-part identifier "t.StartDateUtc" could not be bound.
The multi-part identifier "t.Title" could not be bound.
The multi-part identifier "t1.Id" could not be bound.
The multi-part identifier "t1.AllowComments" could not be bound.
The multi-part identifier "t1.CreatedOnUtc" could not be bound.
The multi-part identifier "t1.EndDateUtc" could not be bound.
The multi-part identifier "t1.Full" could not be bound.
The multi-part identifier "t1.LanguageId" could not be bound.
The multi-part identifier "t1.LimitedToStores" could not be bound.
The multi-part identifier "t1.MetaDescription" could not be bound.
The multi-part identifier "t1.MetaKeywords" could not be bound.
The multi-part identifier "t1.MetaTitle" could not be bound.
The multi-part identifier "t2.Id" could not be bound.
The multi-part identifier "t1.Published" could not be bound.
The multi-part identifier "t3.CreatedOnUtc" could not be bound.
The multi-part identifier "t1.Short" could not be bound.
The multi-part identifier "t2.AllowComments" could not be bound.
The multi-part identifier "t3.EndDateUtc" could not be bound.
The multi-part identifier "t3.Full" could not be bound.
The multi-part identifier "t2.EndDateUtc" could not be bound.
The multi-part identifier "t2.Full" could not be bound.
The multi-part identifier "t3.LanguageId" could not be bound.
The multi-part identifier "t1.StartDateUtc" could not be bound.
The multi-part identifier "t2.LanguageId" could not be bound.
The multi-part identifier "t2.LimitedToStores" could not be bound.
The multi-part identifier "t1.Title" could not be bound.
The multi-part identifier "t3.LimitedToStores" could not be bound.
The multi-part identifier "t2.MetaKeywords" could not be bound.
The multi-part identifier "t3.MetaDescription" could not be bound.
The multi-part identifier "t2.MetaTitle" could not be bound.
The multi-part identifier "t3.MetaKeywords" could not be bound.
The multi-part identifier "t2.Published" could not be bound.
The multi-part identifier "t2.Short" could not be bound.
The multi-part identifier "t3.MetaTitle" could not be bound.
The multi-part identifier "t2.StartDateUtc" could not be bound.
The multi-part identifier "t2.Title" could not be bound.
The multi-part identifier "t3.Published" could not be bound.
The multi-part identifier "t3.Short" could not be bound.
The multi-part identifier "t3.StartDateUtc" could not be bound.
The multi-part identifier "t3.Title" could not be bound.
Nop.Web.Framework.Infrastructure.Extensions.ApplicationBuilderExtensions+<>c.<UseNopExceptionHandler>b__1_1(HttpContext context) in ApplicationBuilderExtensions.cs
Microsoft.AspNetCore.Diagnostics.ExceptionHandlerMiddleware.Invoke(HttpContext context)
Microsoft.AspNetCore.Diagnostics.ExceptionHandlerMiddleware.Invoke(HttpContext context)
Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware.Invoke(HttpContext context)
This post/answer is useful
3
This post/answer is not useful

Please login or register
to vote for this post.

(click on this box to dismiss)
Up-vote the answer, if it helps you! :)


Thank You
Raju Paladiya
-------------------------------------------------------
nopAccelerate - Faster, Reliable & Scalable nopCommerce

sales(at)nopaccelerate.com
http://www.nopAccelerate.com | http://www.xcellence-it.com
Posted: August 21, 2018 at 10:07 AM Quote #210848
Thanks for reporting! Please try one more time
This post/answer is useful
2
This post/answer is not useful

Please login or register
to vote for this post.

(click on this box to dismiss)
Interested in the dedicated Premium support services provided by core developers? Please visit http://www.nopcommerce.com/supportservices.aspx

Regards,
Andrei Mazulnitsyn
Posted: September 07, 2018 at 1:12 AM Quote #211635
Hi Andrei,

Same error now. demo store shows same error message

here is snap  
This post/answer is useful
2
This post/answer is not useful

Please login or register
to vote for this post.

(click on this box to dismiss)
Up-vote the answer, if it helps you! :)


Thank You
Raju Paladiya
-------------------------------------------------------
nopAccelerate - Faster, Reliable & Scalable nopCommerce

sales(at)nopaccelerate.com
http://www.nopAccelerate.com | http://www.xcellence-it.com
Posted: September 07, 2018 at 6:13 AM Quote #211650
I am facing the same issue
This post/answer is useful
0
This post/answer is not useful

Please login or register
to vote for this post.

(click on this box to dismiss)
Please vote for my comment if it is helpful for you.

Thank You
Ilyas Patel
Premium support services
  • Dedicated premium support services provided by core developers are intended for persons who run mission critical websites, work on projects with tight deadlines, or want to get dedicated support.
Professional services
  • Want to open a new store? Want to take your store to the next level? Need a custom extension? We can customize nopCommerce to fit your store perfectly. Request a quote to get started.
eCommerce CONFERENCE 2019
Learn more