Unknown Host Unable to locate the server requested --- the server does not have a DNS entry. Perhaps there is a misspelling in the server name, or the server no

Hello,
Today i tried accessing transitbux.com with mozilla, but i'm getting this kind of a error as mentioned below:
Unknown Host
Description: Unable to locate the server requested --- the server does not have a DNS entry. Perhaps there is a misspelling in the server name, or the server no longer exists. Double-check the name and try again.
Can anyone help me please, and the same website is accessible with my phone.
Help me please. :(
Regards
-

Try http://www.transitbux.com/
Clear the cache and remove cookies only from websites that cause problems.
"Clear the Cache":
*Firefox/Tools > Options > Advanced > Network > Cached Web Content: "Clear Now"
"Remove Cookies" from sites causing problems:
*Firefox/Tools > Options > Privacy > "Use custom settings for history" > Cookies: "Show Cookies"

Similar Messages

I have a web site built by Yahoo Web Site Builder which does not have a Mac version, is there any compatability between Iweb and the old Yahoo program?

I have a web site built by Yahoo Web Site Builder which does not have a Mac version, is there any compatability between Iweb and the old Yahoo program? If not how do I clear off the old site so as to re publish with Iweb.

iWeb cannot import published files so you would need rebuild the site.
Yahoo hosting is notoriously poor and their tech support is awful. I would suggest you look for new hosting and start afresh. Some pointers for choosing hosting...
http://www.iwebformusicians.com/iWeb/Website-Hosting.html
If you do choose to go this route, transfer your domain name registration away from Yahoo to your new host.

My friend's iPod touch 5th gen is locked somehow for 41 years and she does not have a backup. Is there a way to unlock the iPod without restoring it or loosing the pictures and videos from the camera roll?

My friend's iPod touch 5th gen is locked somehow for 41 years and she does not have a backup. Is there a way to unlock the iPod without restoring it or loosing the pictures and videos from the camera roll, the applications can be redownloaded and she had no music. Is there any known bug about ipods locking on their own because no one seemed to have tried to bypass the 4 digit code and it is locked for 26 million minutes.So thank you if anyone has any information or help for us.

Your friend may have placed the ipod next to an object that repeatedly pressed the screen. Under certain circumstances this can lead to what appears to the iTouch to be failed attempts to access the system. After repeated failed attempts, the Touch increases the waiting time required for the password and may ultimately lock in the way you describe.
It's been a while since this was posted, but this might be informative to someone else who finds themself in a similar predicament.

A friend gifted me a copy of The Amazing Spider-man, I redeemed the code, now it tells me I can't download it onto my Ipad (1st Gen) because it does not have a gyroscope. Is there a way for my friend to get his money back, or a way for me to download it?

A friend gifted me a copy of The Amazing Spider-man, I redeemed the code, now it tells me I can't download it onto my Ipad (1st Gen) because it does not have a gyroscope. Is there a way for my friend to get his money back, or a way for me to download it?
As a second option I can play on my 1st gen Ipod Touch. Does that have a gyroscope?

Contact iTunes Store support staff through the report a problem links in your account history or,
iTunes Customer Service Contact - http://www.apple.com/support/itunes/contact.html > Get iTunes support via Express Lane > iTunes > iTunes Store - Apple states all sales are final, but you can always ask nicely. Your friend should have checked the specifications of your ipad before making the gift.

Can you locate a Iphone if that device does not have ICloud on?

Can I locate a lost iPhone if Icloud is turned off on that device?

Settings > iCloud > Find My iPhone must be turned on for the device to be located. The following has some other steps you may want to take such as changing passwords: If your iPhone, iPad, or iPod touch is lost or stolen - Apple Support

The document does not have a valid format. (is there a workaround?)

i searched this one out and saw that a few other people had the same problem with no resolution. i tried "dragging the file into Pages", though that didn't really make sense and nothing happened, that is, the document didn't open. i dragged the file to the Pages icon and got a warning that it couldn't even launch Pages. Opening from within Pages gives me the error in my subject heading. Any ideas on this???

Which are the infos returned in the infos window got thru cmd + I ?
Is the "Show package content item available if you 'ctrl - click' the doc's icon ?
Yvan KOENIG (VALLAURIS, France) samedi 19 septembre 2009 11:30:23

I need to use the "apple key" which is, I presume the command key, but I do not have an apple keyboard; is there a key on a logitech keyboard which will serve the purpose?

I need to use the "Apple key" which I presume is the command key; my computer does not have an apple keyboard; is there a key on a logitech keyboard which will serve the same purpose?

The "Windows flag" key on PC keyaboard in Commans, "Alt" is option.
Go to Logitech website to see if they have Mac compatibility software (Logictech Control Center) to make mappings a bit more complex).

My MacBook Air does not have an optical drive. I have a program (Megastar V) which is installed using a CD. Is there a way to use the optical drive on my PC laptop to install this program on my MacBook Air?

MacBook Air does not have an optical drive. There is a program I wish to install on my Air which is an astronomy application called Megastar V. Installation requires the use of a CD. Is there a way to use the optical drive on my PC (toshiba laptop using Windows 7) to install this program onto my Air?
With gratitude,
Otto

Thank you for explaining to me how to do this. I will try it tomorrow and let all of you know how it goes.
Otto

Messaging Server 4: WebMail login returns "unable to locate the server"

When I log into WebMail, the following error occurs: 

Netscape is unable to locate the server hostname.
Please check the server name and try again.

End User

First verify that you cannot reach the hostname
server by using the ping
utility (Windows NT or Unix). If
you cannot reach the host, report this problem to the appropriate system
administrator or help desk.

However, if you can reach the host with ping
, then the problem may be a minor
networking issue that you can resolve. There is also the possibility that
the network has been configured to allow users to ping
unreachable systems. You can use the
following actions to rule out possible sources of the problem: 

<OL>
<LI>Attempt to log in to WebMail again. If you can log in successfully, then
the problem with the WebMail server may have been temporary or is an
intermittent problem.

<LI>End the current browser session and then restart the browser and try to
connect to the WebMail server again. If you can log in successfully, then,
most likely, the browser had cached some old network information that was
reset when you exited the browser.

<LI>Verify the DNS configuration of your system and then restart the entire
system.
</OL>

If the above actions do not work, then you will need to contact the
system administrator or the help desk.

Mail Server Administrators

As the problem with connecting to the WebMail server is caused by configuration
or availability problems, make sure that users who report this problem have
HTTP network connectivity to the hostname. The following scenarios are
possible causes of connectivity problems: 

<UL>
<LI>Users have the wrong proxy.
<LI>Users are being blocked by firewalls.
<LI>Users are connecting from the wrong network.
<LI>Users specify the incorrect DNS servers.
</UL>

In addition, users may also report that the server is down. As the login page
for WebMail does not contain URL links that are FQDNs or absolute path names,
it is possible that users may still be able to see the login window if it was
cached or loaded before the server stopped working.

In some cases, it may be necessary to access the hostname that is used in the
WebMail links. This hostname setting is stored in the configdb
parameter
service.smtp.messagehostname.
This configuration setting is not mentioned in the Messaging Server
documentation.

The messagehostname is a
configuration value that affects many server functions. For this reason, do
not make changes to this value without first considering the effects of such a
change on other WebMail settings, such as the postmaster group and user
mailhost values. Also, please note that changing messagehostname
is not supported from Console.

For more information on messagehostname
, please see "What is messagehostname?"
at 
article 4250

You can also find documentation for configutil
in the Messaging Server Administrator's
Guide at the following URL: 

http://docs.iplanet.com/docs/manuals/messaging/nms41/ag/cmdline.htm#1003887

Note: You must stop and restart the HTTP service in order for changes to
the messagehostname to
take effect.

When I log into WebMail, the following error occurs: 

Netscape is unable to locate the server hostname.
Please check the server name and try again.

End User

First verify that you cannot reach the hostname
server by using the ping
utility (Windows NT or Unix). If
you cannot reach the host, report this problem to the appropriate system
administrator or help desk.

However, if you can reach the host with ping
, then the problem may be a minor
networking issue that you can resolve. There is also the possibility that
the network has been configured to allow users to ping
unreachable systems. You can use the
following actions to rule out possible sources of the problem: 

<OL>
<LI>Attempt to log in to WebMail again. If you can log in successfully, then
the problem with the WebMail server may have been temporary or is an
intermittent problem.

<LI>End the current browser session and then restart the browser and try to
connect to the WebMail server again. If you can log in successfully, then,
most likely, the browser had cached some old network information that was
reset when you exited the browser.

<LI>Verify the DNS configuration of your system and then restart the entire
system.
</OL>

If the above actions do not work, then you will need to contact the
system administrator or the help desk.

Mail Server Administrators

As the problem with connecting to the WebMail server is caused by configuration
or availability problems, make sure that users who report this problem have
HTTP network connectivity to the hostname. The following scenarios are
possible causes of connectivity problems: 

<UL>
<LI>Users have the wrong proxy.
<LI>Users are being blocked by firewalls.
<LI>Users are connecting from the wrong network.
<LI>Users specify the incorrect DNS servers.
</UL>

In addition, users may also report that the server is down. As the login page
for WebMail does not contain URL links that are FQDNs or absolute path names,
it is possible that users may still be able to see the login window if it was
cached or loaded before the server stopped working.

In some cases, it may be necessary to access the hostname that is used in the
WebMail links. This hostname setting is stored in the configdb
parameter
service.smtp.messagehostname.
This configuration setting is not mentioned in the Messaging Server
documentation.

The messagehostname is a
configuration value that affects many server functions. For this reason, do
not make changes to this value without first considering the effects of such a
change on other WebMail settings, such as the postmaster group and user
mailhost values. Also, please note that changing messagehostname
is not supported from Console.

For more information on messagehostname
, please see "What is messagehostname?"
at 
article 4250

You can also find documentation for configutil
in the Messaging Server Administrator's
Guide at the following URL: 

http://docs.iplanet.com/docs/manuals/messaging/nms41/ag/cmdline.htm#1003887

Note: You must stop and restart the HTTP service in order for changes to
the messagehostname to
take effect.

Soap:Server was unable to process request. --- Value does not fall within the expected range

Brand spanking new Sharepoint 2010 RTM and Designer 2010 RTM install. Unable to edit any page whatsoever even when checking out. Error in SP Designer: soap:Server was unable to process request. ---> Value does not fall within the expected range.
Like I said, this is a brand new RTM install with nothing altered yet. Why can't I edit any pages? I am using the highest credentials so there should be no permission issues. There isn't anything that is helping me on the Web for this.
Why would I encounter a problem like this out of the box? This is not the beta - it is RTM!

Go to :
Site Collection Administration
SharePoint Designer Settings
and Enable the following
Enable Detaching Pages from the Site Definition
Enable Customizing Master Pages and Page Layouts
Enable Managing of the Web Site URL Structure
This should resolve the SP Designer Edit Issues.

Patching WebLogic server - Unable to locate the specified product directory

We are trying to apply the October CPU patch to our WebLogic 10.3.6 installation on Windows Server 2003. However, when we run the below command:
bsu -install -patch_download_dir=E:\ofm11g\utils\bsu\cache_dir -patchlist=BYJ1 -prod_dir=E:\ofm11g\wlserver_10.3
We receive this error:
Unable to locate the specified product directory.[E:\ofm11g\wlserver_10.3]
That directory is valid. We are running two instances using this WLS installation - Oracle Reports 11.1.1.6 and Oracle Portal 11.1.1.6. We are trying to apply the patch with the same user that installed the software.
I was able to successfully run this command on a different server that runs Oracle Internet Directory 11.1.1.6.
Any ideas?

I was able to fix this by ensuring that E:\ofm11g\wlserver_10.3 contained two files: .home and .product.properties. After I copied these from a different server and edited to fit my environment, I was able to successfully install this patch.

Real time transaction response - unable to locate the root element

Hi There
Has anyone integrated webMethods with Data Services 3.2 for real time transactions?
We are trying to create a real time dataflow, initiated by webMethods. We are sending the request to the Access Server which runs our
real time dataflow and does process the request. However, our return response is null. No data in the response back to webMethods. We have
tested this in soapUI, and our transaction does work. We get the correct response back.
So my question is has any experienced this issue with webMethods? Any suggestions or ideas?
Here is the error
===========================================
Path name:
     PortType: Real-time_Services
     Operation: Realtime_address_cleanse
WSDL code: S-9043
[ISS.0092.9043] Schema Error: 1
     pathName: null
     errorCode: CONV-004
     errorMessage: [ISC.0082.9104] DataOut - unable to locate the root element
     identifier: null
===========================================
ps- xmlspy does not work as well
Please let me know
Thanks
Kurt

The problem was the generated test SOAP message from Netbeans. When built, the interface had more levels than described below. I've also had similar issues caused by bad namespaces - either not defined properly or not picking up the default namespace.

UNABLE TO LOCATE THE THE LABVIEW RUN-TIME ENGINE.LVBROKERAUX71

UNABLE TO LOCATE THE THE LABVIEW RUN-TIME ENGINE.LVBROKERAUX71 REQUIRES A VERSION 7.1 (OR COMPATIBLE) LABVIEW RUN-TIME ENGINE。PLEASE CONTACT THE VENDOR OF LVBROKERAUX71 TO CORRECT THIS PROBLEM
Uninstalled DAQ and reinstalled. MAX still throws an error.
Any Isead besides uninstalling 3/4 of my software?
Merry Christmas!
Matthew Fitzsimons
Certified LabVIEW Architect
LabVIEW 6.1 ... 2013, LVOOP, GOOP, TestStand, DAQ, and Vison

To clean up your system, you will need to uninstall the LabVIEW 7.1 run-time engine, and the "LVBroker," and the "LVBrokerAux71" components using the MSI Blast utility. To obtain this utility, please create a service request for phone or e-mail support, and contact one of our Applications Engineers about this issue. Thank you!

Javax.jbi.messaging.MessagingException: Unable to locate the operation

Hi,
I'm getting the following expection when try to test a built and deployed composite application:
javax.jbi.messaging.MessagingException: Unable to locate the operation that has the matching message signature in the requested endpoint {tmf854.v1.ws}ServiceProvisioning,ServiceProvisioningHttp,inbound as in the input SOAP body.
This doesn't make sense, as the Glassfish log shows:
Prepared inbound endpoint {tmf854.v1.ws}ServiceProvisioning,ServiceProvisioningHttp,inbound mapped to context /ServiceProvisioning/Common.
Below is the WSDL:
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions xmlns:tmf854WS="tmf854.v1.ws"
 xmlns:xsd="http://www.w3.org/2001/XMLSchema"
 xmlns:tmf854XSD="tmf854.v1"
 xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
 xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
 xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
 targetNamespace="tmf854.v1.ws"
 name="IhugProvisioningService"
 xmlns:ns1="tmf854.v1"
 xmlns:plnk="http://docs.oasis-open.org/wsbpel/2.0/plnktype"
 xmlns:vprop="http://docs.oasis-open.org/wsbpel/2.0/varprop">
 
 <wsdl:types>
 <xsd:schema targetNamespace="tmf854.v1.ws">
 <xsd:import namespace="tmf854.v1" schemaLocation="Header.xsd"/>
 <xsd:import namespace="tmf854.v1" schemaLocation="Exceptions.xsd"/>
 <xsd:import namespace="tmf854.v1" schemaLocation="IHugServiceProvisioning.xsd"/>
 </xsd:schema>
 </wsdl:types>
 
 <wsdl:message name="ProcessingFailureException">
 <wsdl:documentation>
 The generic exception message.
 </wsdl:documentation>
 <wsdl:part name="ProcessingFailureException" element="tmf854XSD:ProcessingFailureException"/>
 </wsdl:message>
 
 <wsdl:message name="getAvailableServicesByLWC">
 <wsdl:documentation>
 The getInventory request message.
 </wsdl:documentation>
 <wsdl:part name="mtosiHeader" element="tmf854XSD:header"/>
 <wsdl:part name="mtosiBody" element="tmf854XSD:getServicesByExchangeID"/>
 </wsdl:message>
 <wsdl:message name="getAvailableServicesByLWCResponse">
 <wsdl:documentation>
 The getInventory response message.
 </wsdl:documentation>
 <wsdl:part name="mtosiHeader" element="tmf854XSD:header"/>
 <wsdl:part name="mtosiBody" element="tmf854XSD:getServicesByExchangeIDResponse"/>
 </wsdl:message>
 
 <wsdl:message name="configureService">
 <wsdl:documentation>
 The configureService request message.
 </wsdl:documentation>
 <wsdl:part name="mtosiHeader" element="tmf854XSD:header"/>
 <wsdl:part name="mtosiBody" element="tmf854XSD:configureService"/>
 </wsdl:message>
 <wsdl:message name="configureServiceResponse">
 <wsdl:documentation>
 The configureService response message.
 </wsdl:documentation>
 <wsdl:part name="mtosiHeader" element="tmf854XSD:header"/>
 <wsdl:part name="mtosiBody" element="tmf854XSD:configureServiceResponse"/>
 </wsdl:message>
 
 <wsdl:message name="getServiceDetails">
 <wsdl:documentation>
 The getServiceDetails request message.
 </wsdl:documentation>
 <wsdl:part name="mtosiHeader" element="tmf854XSD:header"/>
 <wsdl:part name="mtosiBody" element="tmf854XSD:getServiceDetails"/>
 </wsdl:message>
 <wsdl:message name="getServiceDetailsResponse">
 <wsdl:documentation>
 The getServiceDetails response message.
 </wsdl:documentation>
 <wsdl:part name="mtosiHeader" element="tmf854XSD:header"/>
 <wsdl:part name="mtosiBody" element="tmf854XSD:getServiceDetailsResponse"/>
 </wsdl:message>
 
 <wsdl:message name="testService">
 <wsdl:documentation>
 The testService request message.
 </wsdl:documentation>
 <wsdl:part name="mtosiHeader" element="tmf854XSD:header"/>
 <wsdl:part name="mtosiBody" element="tmf854XSD:testService"/>
 </wsdl:message>
 <wsdl:message name="testServiceResponse">
 <wsdl:documentation>
 The testService response message.
 </wsdl:documentation>
 <wsdl:part name="mtosiHeader" element="tmf854XSD:header"/>
 <wsdl:part name="mtosiBody" element="tmf854XSD:testServiceResponse"/>
 </wsdl:message>
 
 <wsdl:message name="restartService">
 <wsdl:documentation>
 The restartService request message.
 </wsdl:documentation>
 <wsdl:part name="mtosiHeader" element="tmf854XSD:header"/>
 <wsdl:part name="mtosiBody" element="tmf854XSD:restartService"/>
 </wsdl:message>
 <wsdl:message name="restartServiceResponse">
 <wsdl:documentation>
 The restartService response message.
 </wsdl:documentation>
 <wsdl:part name="mtosiHeader" element="tmf854XSD:header"/>
 <wsdl:part name="mtosiBody" element="tmf854XSD:restartServiceResponse"/>
 </wsdl:message>
 <wsdl:message name="ServiceProvisioningOperationRequest">
 <wsdl:part name="part1" type="xsd:string"/>
 </wsdl:message>
 <wsdl:message name="ServiceProvisioningOperationReply">
 <wsdl:part name="part1" type="xsd:string"/>
 </wsdl:message>
 
 <wsdl:message name="portReservation">
 <wsdl:documentation>
 The portReservation request message.
 </wsdl:documentation>
 <wsdl:part name="mtosiHeader" element="tmf854XSD:header"/>
 <wsdl:part name="mtosiBody" element="tmf854XSD:portReservation"/>
 </wsdl:message>
 <wsdl:message name="portReservationResponse">
 <wsdl:documentation>
 The portReservation response message.
 </wsdl:documentation>
 <wsdl:part name="mtosiHeader" element="tmf854XSD:header"/>
 <wsdl:part name="mtosiBody" element="tmf854XSD:portReservationResponse"/>
 </wsdl:message>
 
 
 
 <wsdl:portType name="ServiceProvisioningPortType">
 <wsdl:documentation>
 The Available Services porttype
 </wsdl:documentation>
 <wsdl:operation name="GetAvailableServicesByLWCOperation">
 <wsdl:documentation>
 This is the getInventory request/response operation.
 </wsdl:documentation>
 <wsdl:input message="tmf854WS:getAvailableServicesByLWC"/>
 <wsdl:output message="tmf854WS:getAvailableServicesByLWCResponse"/>
 <wsdl:fault name="ProcessingFailureException" message="tmf854WS:ProcessingFailureException"/>
 </wsdl:operation>
 <wsdl:operation name="ConfigureServiceOperation">
 <wsdl:documentation>
 This is the configureService request/response operation.
 </wsdl:documentation>
 <wsdl:input message="tmf854WS:configureService"/>
 <wsdl:output message="tmf854WS:configureServiceResponse"/>
 <wsdl:fault name="ProcessingFailureException" message="tmf854WS:ProcessingFailureException"/>
 </wsdl:operation>
 <wsdl:operation name="GetServiceDetailsOperation">
 <wsdl:input message="tmf854WS:getServiceDetails"/>
 <wsdl:output message="tmf854WS:getServiceDetailsResponse"/>
 <wsdl:fault name="ProcessingFailureException" message="tmf854WS:ProcessingFailureException"/>
 </wsdl:operation>
 <wsdl:operation name="TestServiceOperation">
 <wsdl:input message="tmf854WS:testService"/>
 <wsdl:output message="tmf854WS:testServiceResponse"/>
 <wsdl:fault name="ProcessingFailureException" message="tmf854WS:ProcessingFailureException"/>
 </wsdl:operation>
 <wsdl:operation name="RestartServiceOperation">
 <wsdl:input message="tmf854WS:restartService"/>
 <wsdl:output message="tmf854WS:restartServiceResponse"/>
 <wsdl:fault name="ProcessingFailureException" message="tmf854WS:ProcessingFailureException"/>
 </wsdl:operation>
 <wsdl:operation name="PortReservationOperation">
 <wsdl:input message="tmf854WS:portReservation"/>
 <wsdl:output message="tmf854WS:portReservationResponse"/>
 <wsdl:fault name="ProcessingFailureException" message="tmf854WS:ProcessingFailureException"/>
 </wsdl:operation>
 </wsdl:portType>
 <wsdl:binding name="ServiceProvisioningSoapHTTPBinding" type="tmf854WS:ServiceProvisioningPortType">
 <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" />
 <wsdl:operation name="GetAvailableServicesByLWCOperation">
 <soap:operation soapAction="getAvailableServicesByLWC"/>
 <wsdl:input>
 <soap:header message="tmf854WS:getAvailableServicesByLWC" part="mtosiHeader" use="literal" />
 <soap:body parts="mtosiBody" use="literal" />
 </wsdl:input>
 <wsdl:output>
 <soap:header message="tmf854WS:getAvailableServicesByLWCResponse" part="mtosiHeader" use="literal" />
 <soap:body parts="mtosiBody" use="literal" />
 </wsdl:output>
 <wsdl:fault name="ProcessingFailureException">
 <soap:fault name="ProcessingFailureException" use="literal" />
 </wsdl:fault>
 </wsdl:operation>
 <wsdl:operation name="ConfigureServiceOperation">
 <soap:operation soapAction="ConfigureServiceOperation"/>
 <wsdl:input>
 <soap:header message="tmf854WS:configureService" part="mtosiHeader" use="literal" />
 <soap:body parts="mtosiBody" use="literal" />
 </wsdl:input>
 <wsdl:output>
 <soap:header message="tmf854WS:configureServiceResponse" part="mtosiHeader" use="literal" />
 <soap:body parts="mtosiBody" use="literal" />
 </wsdl:output>
 <wsdl:fault name="ProcessingFailureException">
 <soap:fault use="literal" name="ProcessingFailureException" />
 </wsdl:fault>
 </wsdl:operation>
 <wsdl:operation name="GetServiceDetailsOperation">
 <soap:operation soapAction="GetServiceDetailsOperation"/>
 <wsdl:input>
 <soap:header message="tmf854WS:getServiceDetails" part="mtosiHeader" use="literal" />
 <soap:body parts="mtosiBody" use="literal" />
 </wsdl:input>
 <wsdl:output>
 <soap:header message="tmf854WS:getServiceDetailsResponse" part="mtosiHeader" use="literal" />
 <soap:body parts="mtosiBody" use="literal" />
 </wsdl:output>
 <wsdl:fault name="ProcessingFailureException">
 <soap:fault use="literal" name="ProcessingFailureException" />
 </wsdl:fault>
 </wsdl:operation>
 <wsdl:operation name="TestServiceOperation">
 <soap:operation soapAction="TestServiceOperation"/>
 <wsdl:input>
 <soap:header message="tmf854WS:testService" part="mtosiHeader" use="literal" />
 <soap:body parts="mtosiBody" use="literal" />
 </wsdl:input>
 <wsdl:output>
 <soap:header message="tmf854WS:testServiceResponse" part="mtosiHeader" use="literal" />
 <soap:body parts="mtosiBody" use="literal" />
 </wsdl:output>
 <wsdl:fault name="ProcessingFailureException">
 <soap:fault use="literal" name="ProcessingFailureException" />
 </wsdl:fault>
 </wsdl:operation>
 <wsdl:operation name="RestartServiceOperation">
 <soap:operation soapAction="RestartServiceOperation"/>
 <wsdl:input>
 <soap:header message="tmf854WS:restartService" part="mtosiHeader" use="literal" />
 <soap:body parts="mtosiBody" use="literal" />
 </wsdl:input>
 <wsdl:output>
 <soap:header message="tmf854WS:restartServiceResponse" part="mtosiHeader" use="literal" />
 <soap:body parts="mtosiBody" use="literal" />
 </wsdl:output>
 <wsdl:fault name="ProcessingFailureException">
 <soap:fault use="literal" name="ProcessingFailureException" />
 </wsdl:fault>
 </wsdl:operation>
 <wsdl:operation name="PortReservationOperation">
 <soap:operation soapAction="PortReservationOperation"/>
 <wsdl:input>
 <soap:header message="tmf854WS:portReservation" part="mtosiHeader" use="literal" />
 <soap:body parts="mtosiBody" use="literal" />
 </wsdl:input>
 <wsdl:output>
 <soap:header message="tmf854WS:portReservationResponse" part="mtosiHeader" use="literal" />
 <soap:body parts="mtosiBody" use="literal" />
 </wsdl:output>
 <wsdl:fault name="ProcessingFailureException">
 <soap:fault use="literal" name="ProcessingFailureException" />
 </wsdl:fault>
 </wsdl:operation>
 </wsdl:binding>
 <wsdl:service name="ServiceProvisioning">
 <wsdl:port name="ServiceProvisioningHttp" binding="tmf854WS:ServiceProvisioningSoapHTTPBinding">
 <soap:address location="http://localhost:18181/ServiceProvisioning/Common"/>
 </wsdl:port>
 </wsdl:service>
 <vprop:property name="CorrelationToken" type="xsd:string"/>
 <vprop:propertyAlias propertyName="tmf854WS:CorrelationToken" messageType="tmf854WS:configureService" part="mtosiHeader"/>
 <plnk:partnerLinkType name="IhugServiceProvisioning">
 <plnk:role name="Requestor" portType="tmf854WS:ServiceProvisioningPortType"/>
 <plnk:role name="Service" portType="tmf854WS:ServiceProvisioningPortType"/>
 </plnk:partnerLinkType>
</wsdl:definitions>Any ideas how to resolve this?
Regards,

The problem was the generated test SOAP message from Netbeans. When built, the interface had more levels than described below. I've also had similar issues caused by bad namespaces - either not defined properly or not picking up the default namespace.

Unable to locate the LMS's API Implementation-Error in Content Player

Dear Guys,
when I am playing the content in content player of Authering environment we get the following error "Unable to locate the LMS's API Implementation" ,
Should any API be implemented explicitly?
How can we resolve this error?
Regards,
Shamila.

Hi Shamila!
As I mentioned, you need to consult your content developer to debug this issue. In the course content(i.e. flash file) there are references to the SCORM API. These when imported in to AE loose the reference. For instance, if you have something like this .. parent.api.<some scrom function> and the parent (window or frame) has the SCORM API. This reference might be getting broken when the course package is imported in to AE. The content developer need to make changes in the code to ensure the reference to the API is changed.
Please let me know if you require further guidance on this.
Regards,
Ravi Sekhar

Unknown Host Unable to locate the server requested --- the server does not have a DNS entry. Perhaps there is a misspelling in the server name, or the server no

Similar Messages

Maybe you are looking for