Greetings We have three cases of instances with problem trying start

leonardod over 10 years ago

Greetings

We have three cases of instances with problem trying start the smart service write database store.

When this smart service is called, the system generate this error:

20:13:00,621 INFO [stdout] (Appian Work Item - 435 - ProcessExec00 : UnattendedJavaActivityRequest) 2015-03-23 20:13:00,597 [Appian Work Item - 435 - ProcessExec00 : UnattendedJavaActivityRequest] ERROR com.appiancorp.process.runtime.activities.WriteToDataStoreSmartService - Error when trying to write to the data store.
20:13:00,621 INFO [stdout] (Appian Work Item - 435 - ProcessExec00 : UnattendedJavaActivityRequest) com.appiancorp.suiteapi.process.exceptions.SmartServiceException: userMsg[error.duringWrite.userMsg=An error occurred while trying to write to the entity ?vivoDadosContencioso? [id=3f68cca6-f689-469e-88ae-0e86e2525141@1203, type=VIVO_CONTENCIOSO_DadosProcesso (id=2230)] (data store: VIVO_CONTENCIOSO). Details: java.lang.RuntimeException: The supplied TypedVal...

Discussion posts and replies are publicly visible

Parents

0 Andrew P Gramann
Certified Lead Developer
over 10 years ago

I've seen something like this in the past where a user had pasted text into an input field that contained unprintable characters, which the system then tried to write to the database. Since those characters don't show up in a web interface, we had to paste the text into NotePad ++ to figure out what the problem was.

Once we figured out what the invalid characters were, we were able to substitute out the unprintable characters and the database write was successful.

Here's a good list of acii unprintable characters:
www.juniper.net/.../intrusion-detection-prevention-custom-attack-object-extended-ascii.html
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 Andrew P Gramann
Certified Lead Developer
over 10 years ago

I've seen something like this in the past where a user had pasted text into an input field that contained unprintable characters, which the system then tried to write to the database. Since those characters don't show up in a web interface, we had to paste the text into NotePad ++ to figure out what the problem was.

Once we figured out what the invalid characters were, we were able to substitute out the unprintable characters and the database write was successful.

Here's a good list of acii unprintable characters:
www.juniper.net/.../intrusion-detection-prevention-custom-attack-object-extended-ascii.html
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data