Contributor input gets lost

[WouterM]

Dear all,

I am being confronted with users claiming that their data gets lost when they enter and commit it via Contributor.

I have not been able to reproduce and I have no clue yet if we are talking about users doing something wrong. But awaiting an opportunity to do more tests, I took a look at the log file.

At numerous occasions during the day I find the following errors (see below) that I cannot explain. So my question to you is; do you have any clue what this means/can cause/etc. Google has not been my friend in finding out.

many thanks beforehand,

wouter

Error sample 1: (201 C - Sales.20101 Sales Plan Data INPUT is the cube.view name)

25976 ERROR 2010-10-22 12:38:13.212 TM1.Blob CommitDeferredFileCommand - Create failed: err=4 system_err_code=123
25976 ERROR 2010-10-22 12:38:13.212 TM1.Blob Commit - file operation failure for blob: 201 C - Sales.20101 Sales Plan Data INPUT_{dbf8c013-0a9f-484b-a232-f9e0a7456c44}_[C Entity].[FRAX].CAMID("Namespace:u:3e528f0cb949e64f95510b2d1e1e3458")

Error sample 2:

27016 ERROR 2010-10-22 12:57:48.321 TM1.Blob CommitDeferredFileCommand - Create failed: err=4 system_err_code=123
27016 ERROR 2010-10-22 12:57:48.321 TM1.Blob Commit - file operation failure for blob: 201 C - Sales.20101 Sales Plan Data INPUT_{dbf8c013-0a9f-484b-a232-f9e0a7456c44}_[C Entity].[FRAX].CAMID("Namespace:u:3e528f0cb949e64f95510b2d1e1e3458")
27016 ERROR 2010-10-22 12:57:48.430 TM1.Blob CommitDeferredFileCommand - Create failed: err=4 system_err_code=123
27016 ERROR 2010-10-22 12:57:48.430 TM1.Blob Commit - file operation failure for blob: 201 C - Sales.20102 Sales Plan TOTAL OVERVIEW_{dbf8c013-0a9f-484b-a232-f9e0a7456c44}_[C Entity].[FRAX].CAMID("Namespace:u:3e528f0cb949e64f95510b2d1e1e3458")

Error sample 3:

25800 ERROR 2010-10-22 13:19:00.634 TM1.Blob CommitDeferredFileCommand - Create failed: err=4 system_err_code=123
25800 ERROR 2010-10-22 13:19:00.634 TM1.Blob Commit - file operation failure for blob: 104 C - Other Costs.10406 Full P&L INPUT screen INCESA & CENTRAL only_{dbf8c013-0a9f-484b-a232-f9e0a7456c44}_[C Entity].[BGISCTOT].CAMID("Namespace:u=S-1-5-21-330163394-2794109790-232441381-1054")
25800 ERROR 2010-10-22 13:19:00.900 TM1.Blob CommitDeferredFileCommand - Create failed: err=4 system_err_code=123
25800 ERROR 2010-10-22 13:19:00.900 TM1.Blob Commit - file operation failure for blob: 104 C - Other Costs.10403 Inbound Freight ISC INPUT only_{dbf8c013-0a9f-484b-a232-f9e0a7456c44}_[C Entity].[BGISCTOT].CAMID("Namespace:u=S-1-5-21-330163394-2794109790-232441381-1054")

[comma]

I can't help you here, but I've experienced a similar problem on 9.5.0.
The user claimed that they have inputed their data via Contributor, it seemed to be true because it's logged in the transaction log.

But on next day, the numbers have disappeared with no trace. So I checked the transaction log, and I can only see lines saying old values were 0 and some number inputed as the new value. But no log recorded for the culprit who zeroed out the number after that!
Until today I still have no clue.

Btw, for your case, can you see whether the user did input the number or not?

[WouterM]

I did see in the logs that the user did login and did take ownership at the exact time he said he lost his data. But my log settings where as such that I did not collect the data of the entry actions of the user. In any case in the cube I did not find any data.