Failed to add DSN - WINCF3

Customer Support Customer Only Discussion
1

I got below error when trying to add a new ODBC DSN - Ms Access on WINCF3

anyone on that server please try and let me know that i’m not the only one having this problem :frowning:

===error===
Failed to add DSN
3/27/2008 4:11:20 AM
Windows H-Sphere engine version: 3.0.1154.2910
Server name: JI-MSSQL10
Server IP: 64.71.235.90
Psoft.HSphere.Transport.Protocols.ProtocolException: System.Net.WebException: The request failed with HTTP status 404: Not Found.

Server stack trace:
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 Psoft.HSphere.Resources.IIS.ColdFusion.CFAdminService.AddTrustedODBCSocket(String dsnName, String adminPasswd) in d:\projects\hsphere\winbox-hs30b\new-build\winbox.NET\Main\Resources\IIS\ColdFusion\CFAdminService.cs:line 83
at Psoft.HSphere.Resources.IIS.ColdFusion.CFMXdsn.Create() in d:\projects\hsphere\winbox-hs30b\new-build\winbox.NET\Main\Resources\IIS\ColdFusion\CFMXdsn.cs:line 39
at Psoft.HSphere.Resources.ResourceWrapper.CreateResource(Parameters parameters) in d:\projects\hsphere\winbox-hs30b\new-build\winbox.NET\Main\Core\Resources\ResourceWrapper.cs:line 739
at Psoft.HSphere.Resources.ResourceManager.Create(Parameters parameters) in d:\projects\hsphere\winbox-hs30b\new-build\winbox.NET\Main\Core\Resources\ResourceManager.cs:line 296
at Psoft.HSphere.Services.Service.CallMethod(String methodName, Parameters parameters) in d:\projects\hsphere\winbox-hs30b\new-build\winbox.NET\Main\Core\Services\Service.cs:line 178
at Psoft.HSphere.Services.Service.ProcessRequest(Request request) in d:\projects\hsphere\winbox-hs30b\new-build\winbox.NET\Main\Core\Services\Service.cs:line 188
at Psoft.HSphere.Resources.ResourceManager.ProcessRequest(Request request) in d:\projects\hsphere\winbox-hs30b\new-build\winbox.NET\Main\Core\Resources\ResourceManager.cs:line 227
at System.Runtime.Remoting.Messaging.StackBuilderSink.PrivateProcessMessage(MethodBase mb, Object args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object& outArgs)
at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)

Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.EndInvokeHelper(Message reqMsg, Boolean bProxyCase)
at System.Runtime.Remoting.Proxies.RemotingProxy.Invoke(Object NotUsed, MessageData& msgData)
at Psoft.HSphere.Transport.ProcessRequestHandler.EndInvoke(IAsyncResult result)
at Psoft.HSphere.Transport.SessionManager.ProcessRequestCallback(IAsyncResult asyncResult) in d:\projects\hsphere\winbox-hs30b\new-build\winbox.NET\Main\Core\Transport\SessionManager.cs:line 193

2

Just try again, I have seen it a few times giving a ‘404’ error ut according to psoft it shouldn’t even be using the asp pages anymore, only a SOAP API

3

still problem :frowning:

4

Kindly, send us a DSN details. We will create it manually on server side.

Actually you can not create CF DSN from CP. HSPHERE wants some changes in server settings to allow it but we can not do it . It will create more issues on server.

Just send us a ticket with DSN details and we will create it for you. You will not able to see it in your HSPHERE account but it will work for your domain.

5

this is not the way it is supposed to be …

this will make us look bad because:

  1. customers see error and think that there is a problem with the server that we can not solve
  2. customers will have to wait everytime they need new dsn as they have to contact us and then we contact you

I really hope this kind of problem go away :frowning:

6

If you send details it will help us to track it down, we have found that it seems to only be happening on old “plans” (I dont mean old server, I mean you may need to load up your plan go throuhg it all and resubmit it)

7

stephen, you can check ticket RS #EKR-16719-281

I reloaded the plan, but still no luck :frowning: