Automatic State transition "Access denied" for non admin users

You say it fails for none admin users. This means that it is not the code that fails. It is a matter of permissions. So you need to look at the permission settings on the transition and possibly on the state, and on the object itself as well.

User has rights to change workflow so it is not that easy.

Typically the issue in these cases is that M-Files checks the state "before" (Valmis) and after (Lainassa), then checks that the user who modified the object has permission to make that transition.  With transitions made via code (e.g. setting property 39) it's often the case that you wish to stop a user making the transition but allow the code to, and that doesn't work.

Often this is only seen when testing with non-administrative users, as administrators have the permission to move from any state to any other state.

Is there any way to solve this without opening transitions for users?

You have a couple of options, but they boil down to making it so that it's the server that moves from state B to C.  From recollection there is a way to do this without code that involves a transitional state between the two; maybe I can ask one of the sales engineers to comment.

Going down the code route the simple way is to allow the object to move into state B naturally, then use some asynchronous process (e.g. task queue) to load the object and move it to state C (this operation is then done by the server, so is allowed to do any state transition).

I'll put a link to this on an internal Teams channel to see whether I can get someone to respond on the non-code way.

You have a couple of options, but they boil down to making it so that it's the server that moves from state B to C.  From recollection there is a way to do this without code that involves a transitional state between the two; maybe I can ask one of the sales engineers to comment.

Going down the code route the simple way is to allow the object to move into state B naturally, then use some asynchronous process (e.g. task queue) to load the object and move it to state C (this operation is then done by the server, so is allowed to do any state transition).

I'll put a link to this on an internal Teams channel to see whether I can get someone to respond on the non-code way.

Automatic without code works fine but then I loose information who did that while that puts "M-Files Server" as last modified

I think these are two separate things.  But any automatic transition is, by definition, undertaken by the server.

If this is the actual thing you want to resolve then you probably need some code on the Valmis state which loads the object history, finds who moved it to the Lainassa state, and calls "SetLastModificationInfoAdmin" to override what's saved: M-Files API