• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Internal server error 500 on new server Windows 2008

J

jerry2

Guest
Hi there

I migrated from 8.6.03 to 8.6.03, but this time it is Windows 2008 x64 server. The site sometimes works, sometimes it doesn't work, every refresh brings the page or:

- System

- Provider

[ Name] Active Server Pages

- EventID 5

[ Qualifiers] 49152

Level 2

Task 0

Keywords 0x80000000000000

- TimeCreated

[ SystemTime] 2008-09-19T05:59:10.000Z

EventRecordID 4141

Channel Application


Security


- EventData

Datei /default.asp Unerwarteter Fehler. Abfangbarer Fehler (C0000005) in einem externen Objekt. Das Skript kann nicht fortgesetzt werden.

Any ideas if Plesk has any problems with Windows 2008 x64?
 
Looks like a permissions issue. If it's a brand new site, I'd delete and recreate it using a different "ftp name". The new perms and users will be created appropriately, which ought to solve the problem.
 
I did try many times :-( Doesn't work. As if myODBC3.51 wouldn't work with the site :-( Now I get Error "80004005'
 
u can disable custom error documents from the setup section of the control panel to have the actual error message displayed
 
I have found out the problem. IIS 7.0 ADO is not the same as IIS 6.0 ADO. If I use RS.MOVE 10 I crash application pool! Even if I have 20 records and move is legitimate (same code works in IIS 6.0). Just thought you should know.
 
Back
Top