SOAP-ERROR: Parsing WSDL: Couldn't load from mantisconnect [duplicate] - soap

This question already has answers here:
ERROR: WSDL - SOAP-ERROR: Parsing WSDL: Couldn't load from [duplicate]
(4 answers)
Closed 9 years ago.
Recently I am trying to integrate two system we use now.
We have a customer feedback website that using Helpspot (http://www.helpspot.com/) and the other is Bug tracker Mantis server. we hope some of customer feedback can be added into mantis . Since mantis have a WSDL mantisconnect, so I wrote some code with nusoap to interact with the mantis wsdl. It worked fine..I can update issue or do rest of other things.
But when I uploaded the same code to the Helpspot server, it stop working...
and I got this error msg:
Fatal error: Uncaught SoapFault exception: [WSDL] SOAP-ERROR: Parsing
WSDL: Couldn't load from
'http://Mymantis/api/soap/mantisconnect.php?WSDL' : Extra content at
the end of the document in
/www/eh17275/public_html/custom_code/RequestPush-MantisBT.php:36 Stack
trace: #0
/www/eh17275/public_html/custom_code/RequestPush-MantisBT.php(36):
SoapClient->SoapClient('http://testmant...') #1
/www/eh17275/public_html/custom_code/RequestPush-MantisBT.php(75):
RequestPush_MantisBT->push('test') #2 {main} thrown in
/www/eh17275/public_html/custom_code/RequestPush-MantisBT.php on line
36
the Line 36 in my code is =>$client=new soapclient('http://Mymantis/api/soap/mantisconnect.php?WSDL');
I googled whole day and most of people encountered this error usually because they wrote their own SOAP server, but in my case, I just wrote a client and the code worked.
and the WSDL on my mantis server is up. I can see this page http : / /mymantis/api/soap/mantisconnect.php and I even want my friend at home to check the page and they can see it. So I think the factor of internet service setting can be elimiated.
Is there any people have any thought about this?
Thx for reading

Maybe you are simply trying with a wrong URL ?
The URL you tested was http://Mymantis/api/soap/mantisconnect.php?WSDL but IMO it should end with ?wsdl.
I tested with the online demo site :
http://www.mantisbt.org/demo/api/soap/mantisconnect.php?WSDL does nothing
http://www.mantisbt.org/demo/api/soap/mantisconnect.php?wsdl works and renders the awaited WSDL document

Related

Magento 2 Error This page isn’t working is currently unable to handle this request. HTTP ERROR 500

i used magento 2 but error as below
aryanorganics.com is currently unable to handle this request.
HTTP ERROR 500
tried to all previous stactoverflow answer still not work.
please give me support
As you tried it on Windows, it could come from this as well, as Windows is not case sensitive with files, and ubuntu is.
You should try looking at the server logs to have more information.
Or else put those lines in your index.php, it should show you the errors and help you debugging it (there is a developper mode you can enable in Magento but I prefere adding all those lines to get more informations) :
ini_set('error_reporting', E_ALL);
ini_set('display_errors', 1);
ini_set('display_startup_errors', 1);

PageExpiredException occurs after closing of ModalWindow

Currently I'm trying to upgrade the application from wicket 1.4 to wicket 6 and I'm stuck with the following issue:
When I try to close ModalWindow, it is closed but I receive PageExpiredException on the page where I was opening this ModalWindow, so I'm redirected to
/myapp/wicket/bookmarkable/org.apache.wicket.markup.html.pages.PageExpiredErrorPage
I thought maybe the way I create ModalWindow is outdated, so I've tried an example from here
http://www.wicket-library.com/wicket-examples-6.0.x/ajax/modal-window?0
and it gives me the same exception.
Maybe I have to configure something in my WebApplication implementation, but I don't know what.
If anyone could help, it'll be really appreciated. Thanks.
Check your server logs for errors related to the serialization of the opener page. PageExpiredException means that the page cannot be found in the page storage. If there was an error with the serialization then it won't be stored and thus later won't be found too.

Apigee can't add TradeTracker Soap API

I'm very new to Apigee.
I'm adding an existing WSDL service as a API proxy.
When fetching the SOAP functions, all looks good. Every single one is imported and are setup correctly.
When i then hit the save button the proxy is created, but are never submitting the revision to the server.
When looking into the problem I see that i get a 502 error back from a file named https://enterprise.apigee.com/gw/upload/[NAME]/tradetracker-api/?validate=true
Also a TypeError: 'undefined' is not an object (evaluating 'b.then') are thrown from a file named 24efdbdd.proxy-editor.js
As i'm using Apigee's own website to add the proxy, so there's not much i can do about it.
This is happening in both Chrome 32, Safari 7 and Firefox 25 and the error has been there for at least a week.
I can't be the only one using Apigee's which keep's getting this error!?
There appears to be an issue with the WSDL file format -- not entirely sure what it is as one WSDL validator I used said it was okay, and another one choked on it saying it wasn't able to parse the file.
I've opened an issue with the Apigee product team to see if A) we can identify the issue with this WSDL and B) improve the product to throw a proper error rather than timing out.
This is fixed in the next release that is scheduled for release on 2/5/2014.

How to test an error page with Error 500 using Zend Framework

I am working on a project where client requires me to beautifully display error 500 with stacktrace etc.
So, I checked the Error Controller and made a nice fancy error page in corresponding views/script
The problem is, how do I test it?
Whilst working on the project, I cleared error on every page and there is no way I could generate it again. Also, I am using doctrine and I remember "echo-ing" the entitymanager array but, I cannot trace the location.
How would I custom generate error 500, "keeping it real"?
PS: I tried htaccess thing and trust me, it throws apache error and not zend 500.
It was pretty silly but, finally found it.
All I needed was to mis-spell a dql tablename on any page where I use querybuilder.

Zend Log: Unexplained Error On Page Request

I'm working on a very custom project using the Zend Framework, where the application uses database driven routes, default routes disabled by default, and a module setup.
I've just created a Zend_Log writer, that logs application errors in the Database.
The thing is, I've got two unexplained errors:
5 NOTICE M:\Zend_Framework\library\Zend\Controller\Action.php Line 516 Page not found
5 NOTICE M:\Zend_Framework\library\Zend\Controller\Action.php Line 516 Request Parameters
I've had a look at the line in question and it just has $this->$action();, which doesn't help me!
Can anyone tell me how I can debug this further?
These are not complete errors. Your logging is somehow broken. We did something like this for our project earlier - you can as well log get/post params, stacktrace, etc.
This looks like someone request nonexistent action - something like /index/does-not-exist