Facebook
Twitter
- Server operating system version
- Windows Server 2016 Standard
- Plesk version and microupdate number
- Plesk Obsidian Version 18.0.49 Update #2, last updated on Jan 11, 2023 04:28 AM
I specialize in hosting stores built upon a particular shopping cart. It is coded, for the most part, in classic ASP. There is some .NET code that plays a role in encoding passwords.
These stores require very specific settings - nothing complicated, but you have to get them right. .NET has to be configured (along with ASP), 32-bit must be enabled, and the application pool must be "integrated". Not a big deal.
In July of last year I discovered that a site which had been present on the server since Sept 2020 would no longer play nice - we could no longer log in to the store admin. The error we received was "We have detected a compatibility issue", which is typically an indication that the above server settings are hosed. I reset the settings over and over, confirming them both via IIS as well as via Plesk. Could not resolve the issue any other way than moving the site to another server where it runs at the present time...
Fast forward to 2 weeks ago, and another site has revealed the same symptoms. I created a dev subdomain, established all of the same settings, copied the files over, and it works just fine. In the original domain, I have reversed and reset all of the needed settings (more than once) and it still failed. Nothing I am aware of had changed before this turned up, and I'm the only person responsible for any changes.
Today I created the domain over on the other server, pointed DNS to that copy of the site via an edit to the hosts file, and it works just fine (as expected.)
So I'm stuck. I don't want to keep having to interrupt stores and move them to a different server when they suddenly fail. How might I determine what has caused these two sites to stop properly running, despite there being no evidence of an incorrect setting?
These stores require very specific settings - nothing complicated, but you have to get them right. .NET has to be configured (along with ASP), 32-bit must be enabled, and the application pool must be "integrated". Not a big deal.
In July of last year I discovered that a site which had been present on the server since Sept 2020 would no longer play nice - we could no longer log in to the store admin. The error we received was "We have detected a compatibility issue", which is typically an indication that the above server settings are hosed. I reset the settings over and over, confirming them both via IIS as well as via Plesk. Could not resolve the issue any other way than moving the site to another server where it runs at the present time...
Fast forward to 2 weeks ago, and another site has revealed the same symptoms. I created a dev subdomain, established all of the same settings, copied the files over, and it works just fine. In the original domain, I have reversed and reset all of the needed settings (more than once) and it still failed. Nothing I am aware of had changed before this turned up, and I'm the only person responsible for any changes.
Today I created the domain over on the other server, pointed DNS to that copy of the site via an edit to the hosts file, and it works just fine (as expected.)
So I'm stuck. I don't want to keep having to interrupt stores and move them to a different server when they suddenly fail. How might I determine what has caused these two sites to stop properly running, despite there being no evidence of an incorrect setting?
