TYPO3 Core

I have another Installation running, Typo3 Ver. 4.3.1 with the same DAM Version 1.1.5: In that combination the problem does not occur.

We now tried out if downgrading the installation in which the problems occurs solves the problem:
- Downgrading typo3 to 4.3.5 and dam to 1.1.1 does not solve the problem. Instead then there´s no more possiblity to index files in dam at all, the dam offers only the trial-mode.
- Downgrading typo3 back to 4.2.14 and dam to 1.1.1 worked in the end: The problem doesn´t occur anymore in that combination

I´ve got some further infos:

- One of my users who is only allowed to work in workspaces has somehow succesfully uploaded a file. She said, it didn´t work first, and she tried to upload it several times, and visited also the side in the frontend to check for the file. Eventually it worked, the file was shown in the backend and she could use it.
I don´t know how long she tried to realise this result, I couldn´t affirm it yet. With trying to uplod I get the error message "Meta record could not be inserted: Attempt to insert a record on page 'Media' (151) from table 'tx_dam' without permissions. Or non-existing page."

- Same user reported another problem in this context:
She can not create new content elements or copy existing content elements. If she tries all seems to work fine, but the new element doesn´s show up on the side (neither backend nor frontend) - but it can be found it in the tab "non-used elements" (got there a dozen entries meanwhile ;-)).
And for workspace users it seems impossible to make this elements appear in the page.

I now know how she managed to use the uploaded file: It was linked via "image links" in the media tab of the content element, and that seems to be a different way then inserting links in the rte. Looks like inserting image links does not use dam techniques.

Okay, finally it seems I´ve solved the problem: It was in the "Allowed excludefields" of the user group the users were asociated with. Some Mediafields and a content field were not marked.

Either the available fields have changed with the update, and the rights were not accurate adapted - or we have a problem with our database.

So, this problem ist solved, you may close the case!