Unable to locate the xml-definition for FieldName with FieldId

On a site collection of SP2013 on-premise farm, I found there are many similar log occur every minute. The logs are like:
Unable to locate the xml-definition for FieldName with FieldId '56747800-d36e-4625-abe3-b1bc74a7d5f8', exception: Microsoft.SharePoint.SPException: Catastrophic failure (Exception from HRESULT: 0x8000FFFF (E_UNEXPECTED)) ---> System.Runtime.InteropServices.COMException:
Catastrophic failure (Exception from HRESULT: 0x8000FFFF (E_UNEXPECTED)) at Microsoft.SharePoint.Library.SPRequestInternalClass.GetGlobalContentTypeXml(String bstrUrl, Int32 type, UInt32 lcid, Object varIdBytes)
at Microsoft.SharePoint.Library.SPRequest.GetGlobalContentTypeXml(String bstrUrl, Int32 type, UInt32 lcid, Object varIdBytes)
The log level is medium. The same set of log occur every minute with same set of 60 different GUIDs. All related function on the site is working as expected. By using PowerShell to loop thru the site collections I confirmed there is no field using these
GUID. Also I have checked the content database and configuration database, also no luck to finding these GUIDs.
These logs should be related with the search service since the Authentication Authorization log mentioned it is the "Crawler" account in action. However I have no idea why the crawler keep looking for these GUID. I have reset the farm service multiple
times already.
The farm was upgraded from SP2010 and it seems no such logs before upgrade.
Any advice? Thank you.

Hi Mark,
From your description, this issue ocurred after you upgraded SharePoint 2010 to SharePoint 2013. Is it right?
Whether you have some solutions in SharePoint 2010.
If yes, please make sure you deploy the solution in SharePoint 2013 well after you upgraded to SharePoint 2013.
There are some similar posts, please check if they are useful for you:
https://social.msdn.microsoft.com/Forums/sharepoint/en-US/5fa900f0-8a1d-4ce8-9ef8-d6e599106834/unable-to-locate-the-xmldefinition-for-fieldname-with-fieldid?forum=sharepointdevelopmentprevious
http://shipoint.com/2013/03/22/fixing-unable-to-locate-xml-definition-for-ctype-with-spcontenttypeid-in-sharepoint-2010/
Best Regards,
Wendy
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Similar Messages

Unable to locate the xml-definition for FieldName with FieldId '1f8a351c-965d-4927-9c22-8772b7089f55' when trying to activate feature with references a custom field type

I´ve a solution which contains a custom field type (found somewhere on the net, the custom field type maps a choice field to managed metadata). There is a second solution which contains site column and site content type definitions using the custom field
type definition from field type solution.
On my developement environment, there is no problem with this two solutions. When field type solution is deployed, i can deploy the content type solution and activate the feature and everything is fine.
However if i give the two solutions to our adminstrator to deploy them into our staging environment, content type feature activation fails. Deploying the field type solution makes no problems. The field type is then available and i can manually creates
columns with this new field type. However activating the content type solution fails with the error shown in the title of this message. The FieldID from the message is not part of my content type project. Searching the net doens´t show any results for that
id. So i think it´s not some of the standard field id´s from sharepoint.
Can anyone help?

Stack Trace
Unable to locate the xml-definition for FieldName with FieldId '1f8a351c-965d-4927-9c22-8772b7089f55', exception: Microsoft.SharePoint.SPException: Catastrophic failure (Exception from HRESULT: 0x8000FFFF (E_UNEXPECTED)) ---> System.Runtime.InteropServices.COMException (0x8000FFFF): Catastrophic failure (Exception from HRESULT: 0x8000FFFF (E_UNEXPECTED))
at Microsoft.SharePoint.Library.SPRequestInternalClass.GetGlobalContentTypeXml(String bstrUrl, Int32 type, UInt32 lcid, Object varIdBytes)
at Microsoft.SharePoint.Library.SPRequest.GetGlobalContentTypeXml(String bstrUrl, Int32 type, UInt32 lcid, Object varIdBytes) -
-- End of inner exception stack trace ---
at Microsoft.SharePoint.SPGlobal.HandleComException(COMException comEx)
at Microsoft.SharePoint.Library.SPRequest.GetGlobalContentTypeXml(String bstrUrl, Int32 type, UInt32 lcid, Object varIdBytes)
at Microsoft.SharePoint.SPFieldCollection.FetchFieldsFromWeb()

Unable to locate the Printer Code for Desktjet 3070A, please help?

Unable to locate the Printer Code for Desktjet 3070A, please help?

You can follow this link for steps on getting started with ePrint on the Deskjet 3070A: http://h10025.www1.hp.com/ewfrf/wc/document?docname=c02728147&cc=us&dlc=en&lc=en&product=5068754&too...=
I am an HP employee

Unable to find corresponding attribute definition for taxonomy

Hi,
I am facing this issue while the endecaScript Service runs.
In the ConfigurationGeneratorForge.log I am seeing this message . Can anybody will help me on this
Thanks in Advance
Jan 24, 2013 12:18:14 PM com.endeca.itl.fcm.integration.cadk.ifdi.TaxonomyGenerator execute
WARNING: Associated attribute (dimension) configuration with spec 'product.price_range' was not found for dval with spec 'under_100'. An associated full configuration is necessary to completely define node, an attempt will be made but some defaults will have to be used (e.g. range dimension bound type)
Jan 24, 2013 12:18:14 PM com.endeca.itl.fcm.integration.cadk.ifdi.TaxonomyGenerator execute
WARNING: Associated attribute (dimension) configuration with spec 'product.price_range' was not found for dval with spec '100_to_500'. An associated full configuration is necessary to completely define node, an attempt will be made but some defaults will have to be used (e.g. range dimension bound type)
Jan 24, 2013 12:18:14 PM com.endeca.itl.fcm.integration.cadk.ifdi.TaxonomyGenerator execute
WARNING: Associated attribute (dimension) configuration with spec 'product.price_range' was not found for dval with spec '100_to_150'. An associated full configuration is necessary to completely define node, an attempt will be made but some defaults will have to be used (e.g. range dimension bound type)
Jan 24, 2013 12:18:14 PM com.endeca.itl.fcm.integration.cadk.ifdi.TaxonomyGenerator execute
WARNING: Associated attribute (dimension) configuration with spec 'product.price_range' was not found for dval with spec '150_to_200'. An associated full configuration is necessary to completely define node, an attempt will be made but some defaults will have to be used (e.g. range dimension bound type)
Jan 24, 2013 12:18:14 PM com.endeca.itl.fcm.integration.cadk.ifdi.TaxonomyGenerator execute
WARNING: Associated attribute (dimension) configuration with spec 'product.price_range' was not found for dval with spec '200_to_300'. An associated full configuration is necessary to completely define node, an attempt will be made but some defaults will have to be used (e.g. range dimension bound type)
Jan 24, 2013 12:18:14 PM com.endeca.itl.fcm.integration.cadk.ifdi.TaxonomyGenerator execute
WARNING: Associated attribute (dimension) configuration with spec 'product.price_range' was not found for dval with spec '300_to_400'. An associated full configuration is necessary to completely define node, an attempt will be made but some defaults will have to be used (e.g. range dimension bound type)
Jan 24, 2013 12:18:14 PM com.endeca.itl.fcm.integration.cadk.ifdi.TaxonomyGenerator execute
WARNING: Associated attribute (dimension) configuration with spec 'product.price_range' was not found for dval with spec '400_to_500'. An associated full configuration is necessary to completely define node, an attempt will be made but some defaults will have to be used (e.g. range dimension bound type)
Jan 24, 2013 12:18:14 PM com.endeca.itl.fcm.integration.cadk.ifdi.TaxonomyGenerator execute
WARNING: Associated attribute (dimension) configuration with spec 'product.price_range' was not found for dval with spec '500_to_1000'. An associated full configuration is necessary to completely define node, an attempt will be made but some defaults will have to be used (e.g. range dimension bound type)
Jan 24, 2013 12:18:14 PM com.endeca.itl.fcm.integration.cadk.ifdi.TaxonomyGenerator execute
WARNING: Associated attribute (dimension) configuration with spec 'product.price_range' was not found for dval with spec 'over_1000'. An associated full configuration is necessary to completely define node, an attempt will be made but some defaults will have to be used (e.g. range dimension bound type)
Jan 24, 2013 12:18:14 PM com.endeca.edf.adapter.AdapterRunner run
SEVERE: Unable to find corresponding attribute definition for taxonomy with root node spec 'product.price_range', you must define a dimension in the schema feed
com.endeca.edf.adapter.AdapterException: Unable to find corresponding attribute definition for taxonomy with root node spec 'product.price_range', you must define a dimension in the schema feed
+     at com.endeca.itl.fcm.integration.cadk.ifdi.TaxonomyGenerator.execute(TaxonomyGenerator.java:249)+
+     at com.endeca.itl.fcm.integration.cadk.ConfigurationAdapter.execute(ConfigurationAdapter.java:118)+
+     at com.endeca.esource.springadapter.SpringDelegateAdapter.execute(SpringDelegateAdapter.java:60)+
+     at com.endeca.edf.adapter.AdapterRunner.run(AdapterRunner.java:168)+
+     at com.endeca.edf.adapter.AdapterRunner.main(AdapterRunner.java:43)+

Hi,
I was also getting same error, which is solved now.
For reference following is what we need to check.
- Proper mapping of source data to endeca dimension is made.
- You have made entries in "dimension_values.csv" but dimension is not specified in "schema.csv"
HTH
MS

Unable to locate unrestricted policy files for the Sun JCE for download

My platform:
java version "1.6.0_26"
Java(TM) SE Runtime Environment (build 1.6.0_26-b03)
Oracle JRockit(R) (build R28.1.4-7-144370-1.6.0_26-20110617-2130-windows-x86_64, compiled mode)
I am unable to locate the Unlimited Strength Jurisdiction JCE files.
According to BouncyCastle for Java 1.6:
..."you must download the unrestricted policy files for the Sun JCE if you want the provider to work properly. The policy files can be found at the same place as the JDK download. Further information on this can be found in the Sun documentation on the JCE."

The version at the very bottom of http://www.oracle.com/technetwork/java/javase/downloads/index.html should work.

I use a macbook pro. Several months ago I signed up for the Photoshop/lightroom offer and the payments are taken from my bank but I am unable to locate the product. I just get a message saying that my trial is expired. I am really desperate.

I use a macbook pro. Several months ago I signed up for the Photoshop/lightroom offer and the payments are taken from my bank but I am unable to locate the product. I just get a message saying that my trial is expired. I am really desperate.

Sign in, activation, or connection errors | CS5.5 and later
Mylenium

Unable to load the XML Report

Hi,
I am using TestStand 3.1. Someone before me has developped a lot of things in our application : specific steps, specific process model, ... . Now this person is not here anymore and I have a test report display problem.
After an execution, the execution window cannot display the test report and displays the following message :
"Unable to load the XML Report.
At line 285 End tag 'NOBR' does not match the start tag 'BR'."
Also with Internet Explorer, the test report cannot be displayed (and he locates the error at lign 287) .
Needless to say that I am a poor guy in XML code that's why I am asking you some help.
But, I opened the .xml with a text editor and that is the part of the code which causes the problem :
284 </Prop>
285 <BLOCKQUOTE>
286 <H5><NOBR>Begin Sequence: MainSequence
287 <BR>(X:\DATA_Utilisateur\Florian DENEVE\04_GENERIC\GenericTestMainSeq\GenericTestMainSeq.seq)<BR></BR></H5>
288 <table BORDERCOLOR=#000000 FRAME=BOX RULES=ALL WIDTH=70%><TBODY>
(please, be careful with the lines numbers, because i don't think that IE and TestStand have the same numbering)
I don't know if it's a problem of basic TestStand or if it's due to the new process model and modifications realized by my previous colleague.
Any ideas ?
Thanks in advance for your help.

Ok, here they are.
There is a file called Addons.cfg.sources but I had to rename it to get it to attach
Attachments:
Addons.cfg.sources.txt ‏1 KB
Addons.cfg ‏53 KB
ResultProcessing.cfg ‏189 KB

Getting error "Unable to find the published output for this request"

1. Created a Data Template
2. Created a Data Definition using the above Data Template
3. Created a RTF template and registered the same in XML Publisher Administrator
4. Created Concurrent program for the data template using 'XDODTEXE' as executable
5. Ran the above concurrent program and it completed successfully.
6. When I click the 'View Output' button in Oracle applications it says "Unable to find the published output for this request".
7. I can see the XML output in the $APPLCSF/out directory.
8. Also the short name for concurrent program and data definition code and template code are same.
I assume the Concurrent Manager’s Output Post Processor is not able to setup the layout template to the generated XML.
Am I missing something here. Can anyone come across this issue.
I have the XML publisher 5.6.1 patch on the DB. Do I need to take 5.6.2 Patch to fix this issue.
Thanks

I tried again after applying XDO 5.6.2. I am still not able to see the output.
Here is the logfile info. There is no mention of OPP or PUBLISH section:
XDO Data Engine ver 1.0
Resp: 21540
Org ID : 101
Request ID: 348042
All Parameters: p_batch_id=7169
Data Template Code: AUDRPT
Data Template Application Short Name: XXCUST
Debug Flag: Y
{p_batch_id=7169}
Calling XDO Data Engine...
Start of log messages from FND_FILE
End of log messages from FND_FILE
Executing request completion options...
------------- 1) PRINT -------------
Printing output file.
Request ID : 348042
Number of copies : 0
Printer : noprint
Finished executing request completion options.

Opatch error 'Unable to parse the xml file'

Hi there,
I am new to installing patches on Oarcle and I need to install patch 12375678 on my windows system, Oracle 11.2.0.2.
I have followed the instructions in the readme.txt file, but got this error and I have not come across anywhere on the web that explain how I could fix it.
Could you please advise?
Thanks
C:\>set oracle_home=C:\oracle\product\11.2.0\dbhome_1
C:\>echo %oracle_home%
C:\oracle\product\11.2.0\dbhome_1
C:\>cd C:\oracle\product\11.2.0\dbhome_1\inventory\oneoffs\12375678
C:\oracle\product\11.2.0\dbhome_1\inventory\oneoffs\12375678>opatch apply
Invoking OPatch 11.2.0.1.1
Oracle Interim Patch Installer version 11.2.0.1.1
Copyright (c) 2009, Oracle Corporation. All rights reserved.
Oracle Home : C:\oracle\product\11.2.0\dbhome_1
Central Inventory : C:\Program Files\Oracle\Inventory
from : n/a
OPatch version : 11.2.0.1.1
OUI version : 11.2.0.2.0
OUI location : C:\oracle\product\11.2.0\dbhome_1\oui
Log file location : C:\oracle\product\11.2.0\dbhome_1\cfgtoollogs\opatch\opatch2
012-05-21_15-28-52PM.log
Patch history file: C:\oracle\product\11.2.0\dbhome_1\cfgtoollogs\opatch\opatch_
history.txt
ApplySession applying interim patch '12375678' to OH 'C:\oracle\product\11.2.0\d
bhome_1'
Running prerequisite checks...
OPatch detected non-cluster Oracle Home from the inventory and will patch the lo
cal system only.
Backing up files and inventory (not for auto-rollback) for the Oracle Home
Backing up files affected by the patch '12375678' for restore. This might take a
while...
Backing up files affected by the patch '12375678' for rollback. This might take
a while...
Patching component oracle.rdbms, 11.2.0.2.0...
Copying file to "C:\oracle\product\11.2.0\dbhome_1\rdbms\xml\xsl\kuexttbl.xsl"
Patching component oracle.rdbms.dbscripts, 11.2.0.2.0...
Copying file to "C:\oracle\product\11.2.0\dbhome_1\rdbms\admin\prvtbpd.plb"
Copying file to "C:\oracle\product\11.2.0\dbhome_1\rdbms\admin\prvtbpw.plb"
ApplySession adding interim patch '12375678' to inventory
Interim Patch metadata parsing failure... 'Unable to parse the xml file.'
ApplySession failed: ApplySession failed in system modification phase... 'Unable
to create patchObject'
OPatch will attempt to restore the system...
Restoring the Oracle Home...
OPatch was able to restore your system. Look at log file and timestamp of each f
ile to make sure your system is in the state prior to applying the patch.
OPatch failed with error code = 73

your actions.xml must not be able to be read.
open it in notepad yourself to see does it open, if so its not corrupt, if doesnt open download patch again.
More then likely will be fine so try locate the patch in a shorter home path, like c:\patches\12375678 and see does it install from there.
Only other thing I can think of is the main inventory.xml, usually c:\program files\oracle\inventory\inventory.xml
try notepad with that too.

Oralce B2B 10g unable to delete the xml from ftp folder

Hi,
Oracle B2B is polling in to a ftp folder which is located on different IP.
After picking-up the xml from this folder, b2b should delete the xml but, it is unable to delete the xml.
and as a result same xml is picked-up multiple times. could you please help us here?
Regards

Manually I am able to delete the xml from thr FTP folder
Also below is the text of b2b-idc log generated
2012.06.06 at 13:46:00:296: B2BStarter thread: (DEBUG) TransportProperties.TransportProperties():markerbasedpoll=false;file.receiver.wallet_location=/etc/ORACLE/WALLETS/ows/ewallet.p12;file.receiver.polling_interval=5;file.receiver.path=/wls_domains/gsb2b/gsb2bdA/ART/oraclePickupPath/outbound;file.receiver.marker=false;marker=false;ccc=false;filename_separator=-;file.receiver.channel_mask=None;port=21;file.receiver.minimum_age=0;filename_format=%TO_PARTY%-%SERVICE%-%ACTIONNAME%-%INREPLYTO_MSG_ID%.xml;file.receiver.van=false;keep_connections=false;file.sender.channel_mask=None;file.receiver.user=gsb2bdA;file.receiver.archive_dir=null;file.receiver.markerbasedpoll=false;file.receiver.password=******;file.receiver.preserve_filename=false;transport_callout_waittime=30;preserve_filename=false;file.receiver.keep_connections=false;file.receiver.ccc=false;van=false;polling_interval=5;
2012.06.06 at 13:46:00:336: B2BStarter thread: (DEBUG) initialize TransportReceiver: [PG_Transport_Server_new < ftp > < CIT >]
2012.06.06 at 13:46:00:338: B2BStarter thread: (DEBUG) FileReceiver.init() started ....
2012.06.06 at 13:46:00:375: B2BStarter thread: (DEBUG) FTPAgent.login(): Enter
2012.06.06 at 13:46:00:377: B2BStarter thread: (DEBUG) Host name is 'hwspxv006'.
2012.06.06 at 13:46:00:484: B2BStarter thread: (DEBUG) Host hwspxv006 FTP command: USER gsb2bdA
2012.06.06 at 13:46:00:486: B2BStarter thread: (DEBUG) FTP Command: USER, reply:
331 Password required for gsb2bdA.
2012.06.06 at 13:46:00:488: B2BStarter thread: (DEBUG) Host hwspxv006 FTP command: PASS
2012.06.06 at 13:46:00:903: B2BStarter thread: (DEBUG) FTP Command: PASS, reply:
230-Please read the file README-btwlutils.txt230- it was last modified on Wed Jul 1 17:09:58 2009 - 1071 days ago230 User gsb2bdA logged in.
2012.06.06 at 13:46:00:908: B2BStarter thread: (DEBUG) FTPAgent.login(): Exit
2012.06.06 at 13:46:00:910: B2BStarter thread: (DEBUG) Disconnecting from hwspxv006
2012.06.06 at 13:46:00:979: B2BStarter thread: (DEBUG) Host hwspxv006 disconnected.
2012.06.06 at 13:46:01:003: B2BStarter thread: (DEBUG) FileReceiver.init() completed.
2012.06.06 at 13:46:01:004: Thread-13: (DEBUG) FTPAgent.login(): Enter
2012.06.06 at 13:46:01:006: Thread-13: (DEBUG) Host name is 'hwspxv006'.
2012.06.06 at 13:46:01:077: Thread-13: (DEBUG) Host hwspxv006 FTP command: USER gsb2bdA
2012.06.06 at 13:46:01:079: Thread-13: (DEBUG) FTP Command: USER, reply:
331 Password required for gsb2bdA.
2012.06.06 at 13:46:01:080: Thread-13: (DEBUG) Host hwspxv006 FTP command: PASS
2012.06.06 at 13:46:01:356: Thread-13: (DEBUG) FTP Command: PASS, reply:
230-Please read the file README-btwlutils.txt230- it was last modified on Wed Jul 1 17:09:58 2009 - 1071 days ago230 User gsb2bdA logged in.
2012.06.06 at 13:46:01:357: Thread-13: (DEBUG) FTPAgent.login(): Exit
2012.06.06 at 13:46:01:359: Thread-13: (DEBUG) Host hwspxv006 FTP command: PASV
2012.06.06 at 13:46:01:361: Thread-13: (DEBUG) FTP Command: PASV, reply:
227 Entering Passive Mode (147,149,200,111,175,184)
2012.06.06 at 13:46:01:362: Thread-13: (DEBUG) Passive: ip = 147.149.200.111, port = 44984
2012.06.06 at 13:46:01:364: Thread-13: (STATUS) Connecting to hwspxv006:44984
2012.06.06 at 13:46:01:366: Thread-13: (DEBUG) Host hwspxv006 FTP command: NLST //wls_domains/gsb2b/gsb2bdA/ART/oraclePickupPath/outbound
2012.06.06 at 13:46:01:368: Thread-13: (DEBUG) FTP Command: NLST, reply:
150 Opening ASCII mode data connection for file list.
2012.06.06 at 13:46:01:375: Thread-13: (DEBUG) Disconnecting from hwspxv006
2012.06.06 at 13:46:01:377: Thread-13: (DEBUG) Host hwspxv006 disconnected.
2012.06.06 at 13:46:01:380: Thread-13: (DEBUG) [IPT_FileRecMonitorProcessFile] Processing file BTGS-bcRequestIncidentReportv1-rsConfirmIncidentReport-2008Dec15_12_12_12_122-Conversation-Id-READY-2009Jun23_16_37_43_625-1295541858750.xml in transport layer.
2012.06.06 at 13:46:01:381: Thread-13: (DEBUG) FTPAgent.login(): Enter
2012.06.06 at 13:46:01:383: Thread-13: (DEBUG) Host name is 'hwspxv006'.
2012.06.06 at 13:46:01:447: Thread-13: (DEBUG) Host hwspxv006 FTP command: USER gsb2bdA
2012.06.06 at 13:46:01:448: Thread-13: (DEBUG) FTP Command: USER, reply:
331 Password required for gsb2bdA.
2012.06.06 at 13:46:01:450: Thread-13: (DEBUG) Host hwspxv006 FTP command: PASS
2012.06.06 at 13:46:01:726: Thread-13: (DEBUG) FTP Command: PASS, reply:
230-Please read the file README-btwlutils.txt230- it was last modified on Wed Jul 1 17:09:58 2009 - 1071 days ago230 User gsb2bdA logged in.
2012.06.06 at 13:46:01:731: Thread-13: (DEBUG) FTPAgent.login(): Exit
2012.06.06 at 13:46:01:732: Thread-13: (DEBUG) Host hwspxv006 FTP command: CWD //wls_domains/gsb2b/gsb2bdA/ART/oraclePickupPath/outbound
2012.06.06 at 13:46:01:771: Thread-13: (DEBUG) FTP Command: CWD, reply:
250 CWD command successful.
2012.06.06 at 13:46:01:773: Thread-13: (DEBUG) Host hwspxv006 FTP command: PASV
2012.06.06 at 13:46:01:775: Thread-13: (DEBUG) FTP Command: PASV, reply:
227 Entering Passive Mode (147,149,200,111,72,215)
2012.06.06 at 13:46:01:776: Thread-13: (DEBUG) Passive: ip = 147.149.200.111, port = 18647
2012.06.06 at 13:46:01:778: Thread-13: (STATUS) Connecting to hwspxv006:18647
2012.06.06 at 13:46:01:787: Thread-13: (DEBUG) Host hwspxv006 FTP command: TYPE I
2012.06.06 at 13:46:01:789: Thread-13: (DEBUG) FTP Command: TYPE, reply:
200 Type set to I.
2012.06.06 at 13:46:01:790: Thread-13: (DEBUG) Host hwspxv006 FTP command: RETR BTGS-bcRequestIncidentReportv1-rsConfirmIncidentReport-2008Dec15_12_12_12_122-Conversation-Id-READY-2009Jun23_16_37_43_625-1295541858750.xml
2012.06.06 at 13:46:01:793: Thread-13: (DEBUG) FTP Command: RETR, reply:
150 Opening BINARY mode data connection for BTGS-bcRequestIncidentReportv1-rsConfirmIncidentReport-2008Dec15_12_12_12_122-Conversation-Id-READY-2009Jun23_16_37_43_625-1295541858750.xml (2257 bytes).
2012.06.06 at 13:46:01:796: Thread-13: (DEBUG) Disconnecting from hwspxv006
2012.06.06 at 13:46:01:798: Thread-13: (DEBUG) Host hwspxv006 disconnected.
2012.06.06 at 13:46:01:834: Thread-13: (DEBUG) Conversion of file BTGS-bcRequestIncidentReportv1-rsConfirmIncidentReport-2008Dec15_12_12_12_122-Conversation-Id-READY-2009Jun23_16_37_43_625-1295541858750.xml to TransportMessage is completed.
2012.06.06 at 13:46:17:355: Thread-13: (DEBUG) Move file to archive null
2012.06.06 at 13:46:17:356: Thread-13: (DEBUG) FileSourceMonitor.moveFile(MessageOrigin): begin to move BTGS-bcRequestIncidentReportv1-rsConfirmIncidentReport-2008Dec15_12_12_12_122-Conversation-Id-READY-2009Jun23_16_37_43_625-1295541858750.xml in //wls_domains/gsb2b/gsb2bdA/ART/oraclePickupPath/outbound to null
2012.06.06 at 13:46:17:359: Thread-13: (DEBUG) Host name is 'hwspxv006'.
2012.06.06 at 13:46:17:462: Thread-13: (DEBUG) Host hwspxv006 FTP command: USER gsb2bdA
2012.06.06 at 13:46:17:464: Thread-13: (DEBUG) FTP Command: USER, reply:
331 Password required for gsb2bdA.
2012.06.06 at 13:46:17:466: Thread-13: (DEBUG) Host hwspxv006 FTP command: PASS
2012.06.06 at 13:46:18:051: Thread-13: (DEBUG) FTP Command: PASS, reply:
230-Please read the file README-btwlutils.txt230- it was last modified on Wed Jul 1 17:09:58 2009 - 1071 days ago230 User gsb2bdA logged in.
2012.06.06 at 13:46:18:055: Thread-13: (DEBUG) Host hwspxv006 FTP command: CWD //wls_domains/gsb2b/gsb2bdA/ART/oraclePickupPath/outbound
2012.06.06 at 13:46:18:081: Thread-13: (DEBUG) FTP Command: CWD, reply:
250 CWD command successful.
2012.06.06 at 13:46:18:083: Thread-13: (DEBUG) Host hwspxv006 FTP command: RNFR //wls_domains/gsb2b/gsb2bdA/ART/oraclePickupPath/outbound/BTGS-bcRequestIncidentReportv1-rsConfirmIncidentReport-2008Dec15_12_12_12_122-Conversation-Id-READY-2009Jun23_16_37_43_625-1295541858750.xml
2012.06.06 at 13:46:18:084: Thread-13: (DEBUG) FTP Command: RNFR, reply:
350 File exists, ready for destination name
2012.06.06 at 13:46:18:086: Thread-13: (DEBUG) FTPClient.renameFrom(): 350 File exists, ready for destination name
2012.06.06 at 13:46:18:087: Thread-13: (DEBUG) Host hwspxv006 FTP command: RNTO null/BTGS-bcRequestIncidentReportv1-rsConfirmIncidentReport-2008Dec15_12_12_12_122-Conversation-Id-READY-2009Jun23_16_37_43_625-1295541858750.xml
2012.06.06 at 13:46:18:090: Thread-13: (DEBUG) FTP Command: RNTO, reply:
550 rename: No such file or directory.
2012.06.06 at 13:46:18:091: Thread-13: (DEBUG) FTPClient.renameTo(): 550 rename: No such file or directory.
2012.06.06 at 13:46:18:092: Thread-13: (ERROR) FTPClient.renameTo(): Unable to RNTO file null/BTGS-bcRequestIncidentReportv1-rsConfirmIncidentReport-2008Dec15_12_12_12_122-Conversation-Id-READY-2009Jun23_16_37_43_625-1295541858750.xml', reply code = 550
2012.06.06 at 13:46:18:093: Thread-13: (DEBUG) File has been already archived BTGS-bcRequestIncidentReportv1-rsConfirmIncidentReport-2008Dec15_12_12_12_122-Conversation-Id-READY-2009Jun23_16_37_43_625-1295541858750.xml in //wls_domains/gsb2b/gsb2bdA/ART/oraclePickupPath/outbound to null
2012.06.06 at 13:46:18:094: Thread-13: (DEBUG) Moved file BTGS-bcRequestIncidentReportv1-rsConfirmIncidentReport-2008Dec15_12_12_12_122-Conversation-Id-READY-2009Jun23_16_37_43_625-1295541858750.xml in //wls_domains/gsb2b/gsb2bdA/ART/oraclePickupPath/outbound to null
2012.06.06 at 13:46:18:109: Thread-13: (DEBUG) Host name is 'hwspxv006'.
2012.06.06 at 13:46:18:190: Thread-13: (DEBUG) Host hwspxv006 FTP command: USER gsb2bdA
2012.06.06 at 13:46:18:193: Thread-13: (DEBUG) FTP Command: USER, reply:
331 Password required for gsb2bdA.
2012.06.06 at 13:46:18:194: Thread-13: (DEBUG) Host hwspxv006 FTP command: PASS
2012.06.06 at 13:46:18:471: Thread-13: (DEBUG) FTP Command: PASS, reply:
230-Please read the file README-btwlutils.txt230- it was last modified on Wed Jul 1 17:09:58 2009 - 1071 days ago230 User gsb2bdA logged in.
2012.06.06 at 13:46:18:474: Thread-13: (DEBUG) Host hwspxv006 FTP command: PASV
2012.06.06 at 13:46:18:475: Thread-13: (DEBUG) FTP Command: PASV, reply:
227 Entering Passive Mode (147,149,200,111,171,164)
2012.06.06 at 13:46:18:477: Thread-13: (DEBUG) Passive: ip = 147.149.200.111, port = 43940
2012.06.06 at 13:46:18:478: Thread-13: (STATUS) Connecting to hwspxv006:43940
2012.06.06 at 13:46:18:480: Thread-13: (DEBUG) Host hwspxv006 FTP command: NLST //wls_domains/gsb2b/gsb2bdA/ART/oraclePickupPath/outbound
2012.06.06 at 13:46:18:482: Thread-13: (DEBUG) FTP Command: NLST, reply:
150 Opening ASCII mode data connection for file list.
2012.06.06 at 13:46:18:483: Thread-13: (DEBUG) Disconnecting from hwspxv006
2012.06.06 at 13:46:18:485: Thread-13: (DEBUG) Host hwspxv006 disconnected.
2012.06.06 at 13:46:18:489: Thread-13: (DEBUG) [IPT_FileRecMonitorProcessFile] Processing file BTGS-bcRequestIncidentReportv1-rsConfirmIncidentReport-2008Dec15_12_12_12_122-Conversation-Id-READY-2009Jun23_16_37_43_625-1295541858750.xml in transport layer.
2012.06.06 at 13:46:18:492: Thread-13: (DEBUG) Host name is 'hwspxv006'.
2012.06.06 at 13:46:18:557: Thread-13: (DEBUG) Host hwspxv006 FTP command: USER gsb2bdA
2012.06.06 at 13:46:18:559: Thread-13: (DEBUG) FTP Command: USER, reply:
331 Password required for gsb2bdA.
2012.06.06 at 13:46:18:561: Thread-13: (DEBUG) Host hwspxv006 FTP command: PASS
2012.06.06 at 13:46:18:833: Thread-13: (DEBUG) FTP Command: PASS, reply:
230-Please read the file README-btwlutils.txt230- it was last modified on Wed Jul 1 17:09:58 2009 - 1071 days ago230 User gsb2bdA logged in.
2012.06.06 at 13:46:18:836: Thread-13: (DEBUG) Host hwspxv006 FTP command: CWD //wls_domains/gsb2b/gsb2bdA/ART/oraclePickupPath/outbound
2012.06.06 at 13:46:18:840: Thread-13: (DEBUG) FTP Command: CWD, reply:
250 CWD command successful.
Thanks

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 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!

Unable to find the published output for this request - problem

Hi ,
In the invoice Payables module i modified a report to be open in xml and not text as it was. The program name of this report iis Print Invoice Notice. I did same thing we normally do to register a xml report in ebs.
The problem is that when i run the report from the invoice form and from the button wich call this raport i get this error:
Unable to find the published output for this request.
No output file exist for the request
and if i see the log file i get this message :
Arguments
P_INVOICE_ID='10243'
APPLLCSP Environment Variable set to :
XML_REPORTS_XENVIRONMENT is :
+/oracle/prodora/8.0.6/guicommon6/tk60/admin/Tk2Motif_UTF8.rgb+
XENVIRONMENT is set to /oracle/prodora/8.0.6/guicommon6/tk60/admin/Tk2Motif_UTF8.rgb
Current NLS_LANG and NLS_NUMERIC_CHARACTERS Environment Variables are :
AMERICAN_ALBANIA.UTF8
+' '+
REP-3000: Internal error starting Oracle Toolkit.
Report Builder: Release 6.0.8.27.0 - Production on Fri Mar 27 02:30:46 2009
+(c) Copyright 1999 Oracle Corporation. All rights reserved.+
The thing is that if i run this report from Other ->Request -> Run of the same module this raport runs correctly
And if i change the output of my report (From concurrent manager) to text its open correctly even from there where i want to open it.
Can anyone give me any sugestion why i get this error while i try to open this xml publisher report from a button in a form in application?
PS: i am using ebs 11.5 version
Thanks in advance,
Best regards

Hi,
REP-3000: Internal error starting Oracle ToolkitThis errors was discussed many times before in this thread, so please search for REP-3000 and fix this error first ( [REP-3000|http://forums.oracle.com/forums/search.jspa?threadID=&q=REP-3000&objID=c84&dateRange=all&userID=&numResults=15] )
Regards,
Hussein

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

Error when opening: "DiscoBrick 1.60. Unable to locate the plugin. Repair permissions and retry."

Error when opening: "DiscoBrick 1.60. Unable to locate the <> plugin. Repair permissions and retry."

I also got this error this morning. DiscoBrick is just a visual plug-in for itunes that i don't even use, so i just uninstalled it and that solved my problem.
Go to MacHD/Library/iTunes/iTunes Plug Ins/ then delete DiscoBrick.
If you still want it you could try re-installing it again
Glen.

Unable to locate the xml-definition for FieldName with FieldId

Similar Messages

Maybe you are looking for