If you get an error from the url in a browser, the problem is on the
server side, not the Flex client.

Tracy

 

________________________________

From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On
Behalf Of Clinton D. Judy
Sent: Tuesday, March 04, 2008 11:45 AM
To: flexcoders@yahoogroups.com
Subject: RE: [flexcoders] WSDL connection failing

 

That's how I get that second error. Normally I see the xml stuff, when
appending ?wsdl to the end of the url, but that's the error I see
instead.

 

From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On
Behalf Of Ramnish Kalsi
Sent: Tuesday, March 04, 2008 11:26 AM
To: flexcoders@yahoogroups.com
Subject: Re: [flexcoders] WSDL connection failing

 

Could it be a DNS issue. Are you able to access wsdl via browser ?

--ramnish

On 04/03/2008, Clinton D. Judy <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
> wrote:

I've seen several 'solutions' to this problem that don't seem to solve
what I'm doing here. Maybe someone here can help. I have a Flex
application on an asp.net backend. The backend exposes itself as a
series of webservices, asmx files that connect to VB files that connect
to MS SQL servers.

 

Since this morning, the application does not work. The error code in
Flex states "Unable to load WSDL. If currently online, please verify the
URI and/or format of the WSDL
(https://www.linkhere.com/REFERENCES.asmx?wsdl)
<https://www.linkhere.com/REFERENCES.asmx?wsdl%29> ". But I haven't
touched this program in weeks. I know it was working yesterday, and it's
not working today.

 

If I go to the link, I get this: "Server Application Unavailable - The
web application you are attempting to access on this web server is
currently unavailable.  Please hit the 'Refresh' button in your web
browser to retry your request. Administrator Note: An error message
detailing the cause of this specific request failure can be found in the
application event log of the web server. Please review this log entry to
discover what caused this error to occur."

 

My DBA looked at the application log, and can't find anything there. So
I'm still stumped at where the problem actually lies. Anyone have any
good leads?

 

 

Clinton Judy

Web Developer

Glenn O. Hawbaker, Inc.

 

 

 

Reply via email to