asmx .net 2.0 web service - .net-2.0

i created a web service, upload it to my site on a remote server.
i tried to browse it but i cant, i also tried to add web reference to his adress through vs08 but the same problem happened there.

Ok, based on your comment:
i didnt get any errors, only when
beowsing it i get a 404 page not found
error, the name space is
"http://www.poppetz.com/poppetz"; but
the service is actually in
http://www.popetz.co.il/Services/Poppetz.asmx
maybe this is the problem??? i
deployed it with vs08 through ftp –
Chen Kinnrot (2 mins ago)
The namespace of your service will have nothing to do with you being able to access it.
If you put a plain old test.html that echo "hello world" back to you and put that in the same directory as your service, can you access that?
ie: http://www.popetz.co.il/Services/test.html
Can you get access to the machine hosting the web services. If so, if you look in the IIS manager, can you see the ASMX in the web site you are expecting it be in?
If not, then start looking at the IIS configuration and make sure that web site directory is the same folder as you are dumping the web service files.

10x everyone, the server provider change some iis config and everything works...\

Related

Why are my REST methods not even reachable from Postman after moving the app with the REST methods to another machine?

With my app running locally (in Visual Studio), I can hit a REST method within it from Postman using either of these URLs:
http://shannon2.nrbq.ad:21609/api/inventory/sendXML/duckbill/platypus/poisonToe.xml
http://localhost:21609/api/inventory/sendXML/duckbill/platypus/poisonToe.xml
So localhost and the machine name both work.
But since I wasn't able to reach the method when calling it from a handheld device connected to my PC, I thought moving the server (REST) app to another machine on the network would clear up that problem.
However, not only can I not reach the REST method from the handheld, I can't even reach it from Postman! I get a "Could not get any response" response in Postman using any of the following URLs; I've tried, I think, every possible permutation:
https://martienda.nrbq.ad/api/inventory/sendXML/duckbill/platypus/test.xml
https://martienda.nrbq.ad:21609/api/inventory/sendXML/duckbill/platypus/test.xml
https://martienda.nrbq.ad/ccr.api/api/inventory/sendXML/duckbill/platypus/test.xml
https://martienda.nrbq.ad:21609/ccr.api/api/inventory/sendXML/duckbill/platypus/test.xml
https://199.96.39.231/api/inventory/sendXML/duckbill/platypus/test.xml
https:/199.96.39.231:21609/api/inventory/sendXML/duckbill/platypus/test.xml
https://199.96.39.231/ccr.api/api/inventory/sendXML/duckbill/platypus/test.xml
https:/199.96.39.231:21609/ccr.api/api/inventory/sendXML/duckbill/platypus/test.xml
...and none of them work (they all respond with the utterly demoralizing "Could not get any response"). What gives? What takes? Why all the hissing snakes? (apologies to Wm. Blake)
Note: If I use "http" instead of "https", I get a "404 - File not Found" error when using the IP Address (but still get "Could not get any response" when using the machine name).
Note: the REST app I can hit when the REST app is run locally is in CCR.API.Controllers and is decorated thus:
[Route("api/inventory/sendxml/{userId}/{pwd}/{filename}")]
Why has the server gone on strike?
Looking at URLs it seems you are hosting your application in either Visual Studio development web server or IIS express. (not necessarily true though). If its either dev server or IIS express then
With VS Dev server you will not be able to access urls/app from other machine but where it is hosted. See this link
If you are using IIS Express then you need to enable remote access. See this link
If you are hosting it in IIS then check firewall settings.

Intalio Ajax Forms pointing to localhost

Anyone working with Intalio|BPMS?
I'm trying to implement a process using the Comunity Edition, and I'm having a problem I can't seem to solve.
The process has an AJAX Form and if I go to ui-fw in the server using localhost everything works, but if I try to access the server remotely using the url it doesn't.
The iframe for the AJAX Form is pointing to localhost and not the url.
From the very bad foruns at Intalio, I've checked /tried:
deploy from the designer using the url
finding every mention of localhost in the process deploy dir, and also in the var/conf
Still no luck.
Any ideas anyone??
Thanks in advance
Ricardo, IIRC the form is deployed according to the settings you use in the deployment manifest. I believe you can also set an other host name in the deployment manifest to deploy to localhost, but declare a different host name for the form and processes.

PHP Slow to process soap request via browser but fine on the command line

I am trying to connect to an external SOAP service using PHP and have written a small php test script that just connects to the service and performs a simple request to check everything is working.
This all works correctly but when I run via a browser request, it is very slow taking somewhere in the region of 40s to establish the initial connection. When I do the same request using the exact same script on the command line, it goes through straight away.
Does anyone have any ideas as to why this might be?
Cheers
PHP caches the wsdl in /tmp. If you run from the command line first, the cache file will be owned by whatever user you're running the script as, and apache won't be able to read the cache. The wsdl will have to be downloaded and parsed every time which will be slow.
Check the permissions of /tmp/wsdl*.
Maybe external SOAP service trying to check your IP, and your server has ICMP allowed, when your local network - not.
Anyway, this question might be answered more clearly by administrator of external SOAP service :)
Is there a difference between the php.inis that are being used?
On a standard ubuntu server installation:
diff /etc/php5/apache2/php.ini /etc/php5/cli/php.ini
//edit:
Another difference might be in the include paths. Had this trouble myself on a local test server, it didn't actually use the soap class that was included (it didn't include anything, because the search paths weren't valid), but it included the built-in soap_client class.

How do I get more details on my request error on IIS7

I have deployed a REST service on an external server (IIS7). When I start the service from VS on the Dev server it works fine. But on the server i get:
Request Error, The server encountered an error processing the request. Please see the service help page for constructing valid requests to the service.
How do I get more details on this error? I have looked in the log files directory that is configured under Logging feature for this web site in IIS Manager, but there are no files at all for this site it seems.
You should look in the Windows Event Log using the Event Viewer application (eventvwr.exe). Output to the IIS log files may be buffered so their contents may be updated after a restart, or when IIS is set to do it. Restarting IIS is a surefire way to force this.
Here is a blog post on how to do this.
I'm aware of 3 ways to get nicer errors:
Set UseVerboseErrors in InitializeService method. However, this won't give you anything if your error occurs before InitializeService is called (which happens).
Set IncludeExceptionDetailInFaults to true using an attribute before your service class.
Set IncludeExceptionDetailInFaults to true using web.config.

running a .net web service on iis6 deployed on windows 2003 server sp2

To whom it may respond to,
We have deployed a web service to Windows 2003 Server SP2 , .net framework 3.5 .
"The service is not running , we are getting the error :
The website declined to show this webpage
HTTP 403
Most likely causes:
•This website requires you to log in.
What you can try:
Go back to the previous page.
More information
This error (HTTP 403 Forbidden) means that Internet Explorer was able to connect to the website, but it does not have permission to view the webpage.
For more information about HTTP errors, see Help."
We have played around with the permissions but the situation didn't change a bit.
We would be very glad ideas on it,
Thank you for your concern,
Best Regards,
Kayhan YUKSEL
Make sure you have aspnet_isapi.dll as your wildcard handler in the Virtual Directory setup. Properties --> Virtual Directory --> Configuration --> Insert... --> aspnet_isapi.dll, make sure you uncheck Verify that file exists.