Recurring 'No database instance'

Hello,

I've got a bit of an odd problem,

I've got a nopCommerce 3.9 website up and running.

Its all great and fast, it's had orders fine and has been running well... all apart from one issue.

Every seemingly random period ranging from 2 weeks to a few days the whole website breaks overnight and returns "No database instance". The only way i've managed to fix the site is to completely export the whole database, create a new one and then import the one that had broke. I give it the same username and password as before, alter the database name in the Setting.txt  and then the website loads up fine.

It's as if the database credentials have an expiry date, but I cannot find any information regarding this.

We've started to blame our host 1and1 but we're not 100% sure it's there fault. I also use the Nop Uptown Responsive Theme from nop-templates.com although I don't think that would be causing the issue.

I've attached a few helpful images below, if theres any other images which would be useful please ask.

If anyone could provide any insight to this issue I would be very grateful.

Thanks,

David

DavidFoley wrote:


Please check

https://www.nopcommerce.com/boards/t/26946/no-database-instance.aspx

Thanks for the link,

A couple of users mentioned that there password had expired, but provided no method of checking or altering this.

Is there an option in nopCommerce to turn off password expiration?

Thanks

DavidFoley wrote:

For the password expiration, I think it's part of SQL Server. I mean when you create user in sql server to connect your db (also use in connection string), there is a option as "Enforce password expiration". You should unchecked this option if you use user login to connect using connection string.

I found one more case to reproduce this error. I get this error while SQL Server services has stopped and you try to process request. You will get the same error. I'm not sure this case is suitable for you or not but might be you can think in that direction.

DavidFoley wrote:

I would also suggest you that, whenever your site gets down, check your SQL server service first.