OK .. Today I tryed AGAIN to install everything from scratch under Windows 2008. SmarterMail5 error has been fixed and adding new e-mail accounts is not a problem. But after adding few users and websites I'm starting having this error:

[ArgumentException: '', hexadecimal value 0x13, is an invalid character.]

   System.Xml.XmlConvert.VerifyCharData(String data, ExceptionType exceptionType) +1797845

   System.Xml.DocumentXmlWriter.WriteString(String text) +35

   System.Xml.XmlWellFormedWriter.WriteString(String text) +1586215

   Microsoft.Web.Services3.Xml.XmlWrappingWriter.WriteString(String text) +17

   Microsoft.Web.Services3.Xml.XmlWrappingWriter.WriteString(String text) +17

   System.Web.Services.Protocols.Soap11ServerProtocolHelper.WriteFault(XmlWriter writer, SoapException soapException, HttpStatusCode statusCode) +909

   System.Web.Services.Protocols.SoapServerProtocol.WriteException(Exception e, Stream outputStream) +1277

   System.Web.Services.Protocols.WebServiceHandler.WriteException(Exception e) +125

   System.Web.Services.Protocols.WebServiceHandler.CoreProcessRequest() +487777

   System.Web.Services.Protocols.SyncSessionlessHandler.ProcessRequest(HttpContext context) +191

   System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +638

   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +177

.. of course I writed about this 10 days ago (http://forum.dotnetpanel.com/forums/t/3759.aspx) but I dont know why there was no response from DNP crew (I think supporting/testing DNP under Windows 2008 should interest DNP team since there is provider for this operating system and on main page there is huge banner informing user that IIS7 and Win2008 are supported).

As far as i know, DNP does not yet supporting windows server 2008 RTM.

So here:

    http://www.dotnetpanel.com/DotNetPanel/SupportedSoftware.aspx

should be info that RCX version is supported. I'm just suprised that no one from DNP team has not responded to my previous thread.

Yep. That's what i got from DNP support:

:/

Thanks for info

But anyway here:

http://www.dotnetpanel.com/DotNetPanel/SupportedSoftware.aspx

should be info for users who want to test/run DNP under Win2008 that DNP was tested only under some RCx version.

EDIT:

problem is in http://127.0.0.1:9002/esWebServers.asmx webservice in AddWebSite method

For anyone who is testing DNP under Windows 2008: this error is caused by wrong naming Application Pools when web page is created. Solution for this is to disable from policies Dedicated Application Pools and if You want to have dedicated app pool for some side just enable it after page has been created. Thats all :)

DNP team are working on this

GrZeCh:

For anyone who is testing DNP under Windows 2008: this error is caused by wrong naming Application Pools when web page is created. Solution for this is to disable from policies Dedicated Application Pools and if You want to have dedicated app pool for some side just enable it after page has been created. Thats all :)

DNP team are working on this

Getting this error too when trying to switch .Net versions -- DNP is incredibly buggy with Windows Server 2008.

 Have You turned on creating dedicated pools for users websites in Your DNP policies?

EDIT: Ah sorry .. You are getting this error while switching .NET versions and not creating websites. Are You trying switching maybe to .NET 1.1 ?

Hello guys,

We apologize for the confusion. DNP currently supports Windows 2008 RTM (Supported software page has been updated accordingly).

Could you please specify a scenario how the issue can be reproduced on the platform mentioned?

Thanks.

GrZeCh:

 Have You turned on creating dedicated pools for users websites in Your DNP policies?

EDIT: Ah sorry .. You are getting this error while switching .NET versions and not creating websites. Are You trying switching maybe to .NET 1.1 ?

Actually this doesn't just happen when switching Application Pools. Anytime you click the Update button when trying to modify Web Site Properties for some domains this error comes up (even if there are no changes made).

We get the SAME error all the time on Windows 2008. It happens when switching between application pools and is really annoying! The error has been posted here for months without reply!System.InvalidOperationException: Client found response content type of 'text/html; charset=utf-8', but expected 'text/xml'.
The request failed with the error message:
--

Server Error in '/' Application.
--------------------------------------------------------------------------------

'', hexadecimal value 0x13, is an invalid character.

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.ArgumentException: '', hexadecimal value 0x13, is an invalid character.

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:

[ArgumentException: '', hexadecimal value 0x13, is an invalid character.]
   System.Xml.XmlConvert.VerifyCharData(String data, ExceptionType exceptionType) +1797845
   System.Xml.DocumentXmlWriter.WriteString(String text) +35
   System.Xml.XmlWellFormedWriter.WriteString(String text) +1586215
   Microsoft.Web.Services3.Xml.XmlWrappingWriter.WriteString(String text) +17
   Microsoft.Web.Services3.Xml.XmlWrappingWriter.WriteString(String text) +17
   System.Web.Services.Protocols.Soap11ServerProtocolHelper.WriteFault(XmlWriter writer, SoapException soapException, HttpStatusCode statusCode) +909
   System.Web.Services.Protocols.SoapServerProtocol.WriteException(Exception e, Stream outputStream) +1277
   System.Web.Services.Protocols.WebServiceHandler.WriteException(Exception e) +125
   System.Web.Services.Protocols.WebServiceHandler.CoreProcessRequest() +487777
   System.Web.Services.Protocols.SyncSessionlessHandler.ProcessRequest(HttpContext context) +191
   System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +638
   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +177

--------------------------------------------------------------------------------

Version Information: Microsoft .NET Framework Version:2.0.50727.1434; ASP.NET Version:2.0.50727.1434

--.
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[ parameters)
at DotNetPanel.EnterpriseServer.esWebServers.UpdateWebSite(WebSite site)
at DotNetPanel.Portal.WebSitesEditSite.SaveWebSite()

The complete error we get it:

Come on DNP team, this has been reported such a long time ago with not even the simplest attempt for a fix. I have at least 20 - 30 domains I can reproduce this with.

I am experiencing this Hexadecimal errors also. Using windows 2008 server std. Below is a paste from current DNP system requirements page.

 Microsoft Windows Server 2003 (SP2 is recommended) or Windows Server 2008.

 Isn't it time these errors be gone. In my case I am using a stock Win 2008 std exclusively testing DNP.

This is such a big deal and I'm surprised that the DNP staff are just ignoring this altogether.

 We can't get a correct build to function under Windows 2003 let alone 2008. I've been trying to get one main feature to work for years now that DNP has yet to address. What's the primary purpose of a host automation package? Billing clients for usage of resources, bandwidth and hd space for web, mail, etc. Why can't we just get the show stopper bugs fixed before we try concentrating on additional features?