Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Help deploying a simple Web Service
Message
From
26/11/2003 15:27:29
 
General information
Forum:
ASP.NET
Category:
Web Services
Miscellaneous
Thread ID:
00853840
Message ID:
00853843
Views:
14
>I have a simple web service. It reads an Access table and returns an XML string containing the data for the provided ID.
>
>It runs fine on my machine using the local IIS.
>
>To deploy it, I copied the entire folder (..\wwwroot\WSDemo2) to a remote server. Now I know that the system will have a problem with the hard coded path to the data (which was the only thing I thought I would need to fix) but I can't even get the .asmx page to display on IE.
>
>When I do, I get an error:
>
>Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.
>
>But I have the following in my web.config file:
>
> [ customErrors mode= "Off" ]
> [!-- [customErrors mode="RemoteOnly" /] --]
>
>(Note I used the square brackets instead of angle brackets in the example since the UT doesn't allow me to use the angle brackets in messages.)
>
>Any ideas why I can't see the correct error message?
>
>Also:
>- Any ideas on what path I should use for the .MDB file so it can be found on the server?
>- Am I deploying this the wrong way? Note that I copied the entire folder to the web server. And the server supposedly has all the Dot Net framework installed and is used by others to demo Dot Net code.

As far as the files that is required on the server, only the ASMX file and the BIN directory two files are required. We usually create a http://www.mydomain.com/WebService virtual directory where WebService corresponds to your location of the ASMX file. Under that directory is the BIN directory with the two DLL files.

Yes, as you said, you'll have to send the new DLL files to the server from a compilation that will represent the actual server path required for your application.

As for your Web.config file, try only having one at the root of your Web server. That will be easier to debug. Once that resolved, you'll be able to scale it down to the required directory if you wish. I don't know more at this point why it doesn't work. As you said, it would help if the required message would appear.
Michel Fournier
Level Extreme Inc.
Designer, architect, owner of the Level Extreme Platform
Subscribe to the site at https://www.levelextreme.com/Home/DataEntry?Activator=55&NoStore=303
Subscription benefits https://www.levelextreme.com/Home/ViewPage?Activator=7&ID=52
Previous
Reply
Map
View

Click here to load this message in the networking platform