ICC Error 1072896749 - filenet-p8

I am getting this error (in taskroute log) while trying to ingest documents from ICC (IBM Content Collector v2.1.x) with xml as metadata file. Can anyone shed more light on "Whitespace is not allowed at this location." error?
2011-09-12T18:39:37Z Error An error occurred while evaluating the task route 'M1 TR Docs': Task Method 'ibm.ctms.filesystem.metadata' failed for entity with id 'd:\icc_migration\conventional_pm\test.xml': Status=error; Message='Error -1072896749 at 22:22 - "Whitespace is not allowed at this location." - D:\ICC_Migration\Conventional_PM\test.xml'Reason: Task Method 'ibm.ctms.filesystem.metadata' failed for entity with id 'd:\icc_migration\conventional_pm\test.xml': Status=error; Message='Error -1072896749 at 22:22 - "Whitespace is not allowed at this location." - D:\ICC_Migration\Conventional_PM\test.xml' ibm::ctms::taskrouting::TaskRouteEvaluator::SubmitRoute (taskrouteevaluator.cpp:427) 0x820 Stack Trace: (class ibm::ctms::taskrouting::TaskStatusException) at ibm::ctms::taskrouting::TaskRoutingException::TaskRoutingException (taskrouting.cpp:11), at ibm::ctms::taskrouting::TaskStatusException::TaskStatusException (taskrouting.cpp:88), at ibm::ctms::taskrouting::TaskMethodManager::checkTaskStatus (taskmethodmanager.cpp:610), at ibm::ctms::taskrouting::TaskMethodManager::InvokeTaskMethod (taskmethodmanager.cpp:730), at ibm::ctms::taskrouting::TaskRouteEvaluator::invokeTaskMethod (taskrouteevaluator.cpp:255), at ibm::ctms::taskrouting::TaskRouteEvaluator::SubmitRoute (taskrouteevaluator.cpp:375), at ibm::ctms::taskrouting::TaskRouteEngine::SubmitEntity (taskrouteengine.cpp:475), at ibm::ctms::taskrouting::SubmissionTask::Execute (submissiontask.cpp:44), at ibm::ctms::core::threads::ThreadPoolImplementation::TaskThread::Execute (threadpool.cpp:214), at ATL::CThreadPool<ibm::ctms::core::threads::ThreadPoolImplementation::TaskThread,ATL::CRTThreadTraits,ATL::Win32WaitTraits>::ThreadProc (atlutil.h:1386), at ATL::CThreadPool<ibm::ctms::core::threads::ThreadPoolImplementation::TaskThread,ATL::CRTThreadTraits,ATL::Win32WaitTraits>::WorkerThreadProc (atlutil.h:1404), at MSVCR80.dll:0x29ba, at MSVCR80.dll:0x2a46,

I figured it. The XML that I was trying to use had a tag like this.
<Company name>Test & Company</Company Name>
And of course, it did not like the "&" symbol there. I enclosed it in CDATA tag and it was fixed. What was mysterious though was the disconnect between the type of error and error message ICC was throwing.

Related

Feature type rename failed after 9

I'm trying to upload shape file for geoserver and I'm getting this error when I upload the same feature type 10 times in to different datastores.
I'm getting this warning,
WARN [rest.catalog] - Feature type surface_zone_line-line already exists in namespace MyWorkSpace, attempting to rename
And In the next line this error is showing,
ERROR java.lang.RuntimeException: java.lang.IllegalArgumentException: Resource named 'surface_zone_line-line9' already exists in namespace: 'MyWorkSpace'
That renaming worked well up to 9 feature types but It didn't work for 10th.
Please help!
GeoServer Version 2.14.1

Error: command "bash" failed with no error message?

I am using terraform on my Mac system, and terraform apply results with below error
Error: command "bash" failed with no error message
on ssm.tf line 7, in data "external" "ssm-dynamic-general":
7: data "external" "ssm-dynamic-general" {
However there is nothing wrong in ssm.tf file, same runs perfectly fine in my another system.
Can some one please let me know what i am missing here?
You might have done what I accidentally did: not follow the external program protocol:
https://www.terraform.io/docs/providers/external/data_source.html#external-program-protocol
In my particular case, I failed to send the errors that were coming from my program to standard error. Instead, those errors were going to standard out.
That's why Terraform wasn't able to report on those errors.
So if you send any and all errors from your program to standard error using > &2, you should be able to see those errors when you run terraform plan.

tensorflow_datasets.load() downloads but cannot extract certain datasets

Calling tensorflow_datasets.load('cycle_gan/apple2orange') works fine
but tensorflow_datasets.load('cycle_gan/vangogh2photo') gives me an error.
I've tried this on my desktop and laptop and both gave the same error message.
Here's the code I ran and the error message I got:
import tensorflow_datasets as tfds
dataset = tfds.load('cycle_gan/vangogh2photo',
data_dir='data', batch_size=1, download=True, in_memory=False)
InvalidArgumentError: Failed to create a NewWriteableFile: data\downloads\extracted\ZIP.peop.eecs.berk.edu_taes_park_Cycl_data_vanNiw0c-cL4JRL2gjUnWYOr9woVN9V1peDW4GG0decqv8.zip.incomplete_bf327518b23f41ee9a3a469cc0b541ba\vangogh2photo\testB\2014-12-10 12:08:40.jpg : The filename, directory name, or volume label syntax is incorrect.
; Unknown error
then it says
During handling of the above exception, another exception occurred:
(traceback)
ExtractError: Error while extracting data\downloads\peop.eecs.berk.edu_taes_park_Cycl_data_vanNiw0c-cL4JRL2gjUnWYOr9woVN9V1peDW4GG0decqv8.zip to data\downloads\extracted\ZIP.peop.eecs.berk.edu_taes_park_Cycl_data_vanNiw0c-cL4JRL2gjUnWYOr9woVN9V1peDW4GG0decqv8.zip : Failed to create a NewWriteableFile: data\downloads\extracted\ZIP.peop.eecs.berk.edu_taes_park_Cycl_data_vanNiw0c-cL4JRL2gjUnWYOr9woVN9V1peDW4GG0decqv8.zip.incomplete_bf327518b23f41ee9a3a469cc0b541ba\vangogh2photo\testB\2014-12-10 12:08:40.jpg : The filename, directory name, or volume label syntax is incorrect.
; Unknown error
How do I fix this?
Which OS are you using?
There is an issue with some datasets on Windows when composing the URLs to fetch the files or the URLs where to save them locally.
For the Oxford Pets III dataset, the link below provides the fix:
https://github.com/tensorflow/tensorflow/issues/31171#issuecomment-529169445
Perhaps something similar may apply here?

Where is the laravel error file located? or Is there a default error log in Laravel?

I'm working on a medium project -with laravel- for quite a long time now and of course I use the debugger of the framework -laravel-, but now from time to time I see the page of error but there is just "whoops something went wrong without" without any specifications for the error, and I see it a lot in ajax requests, but I just actualize the page and its gone!;
Finally the error show up again and I could see it in my terminal with the command tail down here
this is what I got
[2016-12-28 14:54:04] production.ERROR: exception 'RuntimeException' with message 'No supported encrypter found. The cipher and / or key length are invalid.' in D:\shop\tess\vendor\laravel\framework\src\Illuminate\Encryption\EncryptionServiceProvider.php:45
Stack trace:
#0 D:\shop\tess\vendor\laravel\framework\src\Illuminate\Encryption\EncryptionServiceProvider.php(25): Illuminate\Encryption\EncryptionServiceProvider->getEncrypterForKeyAndCipher(NULL, 'AES-256-CBC')
#1 D:\shop\tess\vendor\laravel\framework\src\Illuminate\Container\Container.php(731): Illuminate\Encryption\EncryptionServiceProvider->Illuminate\Encryption\{closure}(Object(Illuminate\Foundation\Application), Array)
I've found this on github it helped https://github.com/orchestral/testbench/issues/93
Make sure APP_DEBUG is set to true in your .env file
You can check the errors with the following command tail -f storage/logs/laravel.log Could be different errors

Chef - ArgumentError: too short control escape

I will glad to get an any help in the next issue:
when I run a numerous recipes (when I run an each in a separate way it doesn't fails), I sometimes get a next error:
"ArgumentError: too short control escape"
log:
[2016-03-15T15:41:55+01:00] INFO: Running queued delayed notifications before re-raising exception
[2016-03-15T15:41:55+01:00] ERROR: Running exception handlers
[2016-03-15T15:41:55+01:00] ERROR: Exception handlers complete
[2016-03-15T15:41:55+01:00] FATAL: Stacktrace dumped to c:/chef/chef-stacktrace.out
[2016-03-15T15:41:55+01:00] FATAL: ArgumentError: too short control escape
chef-stacktrace.out:
Generated at 2016-03-14 15:56:29 +0100
ArgumentError: too short control escape
C:/opscode/chef/embedded/apps/chef/lib/chef/formatters/error_inspectors/resource_failure_inspector.rb:66:in 'recipe_snippet'
C:/opscode/chef/embedded/apps/chef/lib/chef/formatters/error_inspectors/resource_failure_inspector.rb:43:in 'add_explanation'
It happens randomly and I can't to find an explanation,
Thanks
I'm guessing something is going wonky with the regexp compile. It supposed to use Regexp.escape(source) but something might be slipping through? Please include the full error output though.
After a deep investigations, we have found the root cause of the issue. The name of the Github repository was interpreted by Chef as an escape character (the name of repository was starting with capital letter "C") which caused the configuration to fail alternately.
It regards to Chef 12.0.3 version (I hope, they fixed it in a newer next version)
We changed the name of repository and it solved the problem.

Resources