nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Behavior of InsertAsset_UNC in version 4.5.3

System

Hello all.

We've just upgraded to version 4.5.3 (previously we had 4.01), and I noticed that it now seems to be impossible to use InsertAsset_UNC with UNC paths that refer to shares that are not on the MediaBin server.

Why is this? Is there a way of getting around it without using GetUploadUNC and copying the files to the MediaBin server?

Also, how long do the temporary directories created by GetUploadUNC stay on the server? Is there a way to set how long they stay there?

Thanks in advance

Folco

Find more posts tagged with

Comments

lyman

MediaBin doe snot know whether UNC paths are local or remote, however it does have to respect permissions. The two checks that get made with a UNC path are a) whether the pathname starts with "\\", and b) if the operating systems gives the account running the MediaBin service read permission.

Sometimes people install MediaBin service running under an account that does not have network permissions and that would explain the problem. The trick is to log in with the same permissions that the MediaBin service is running and try to access the desired share.

Note that using an upload not from a UNC while less efficient may work for you as it invokes a transfer which means that it relies on the visibility of the share to the client insead of the server. However you may want to resolve the permissions issue if performance outweighs security considerations.

Cheers,

Lyman Hurd

Migrateduser

MediaBin doe snot know whether UNC paths are local or remote, however it does have to respect permissions. The two checks that get made with a UNC path are a) whether the pathname starts with "\\", and b) if the operating systems gives the account running the MediaBin service read permission.

Sometimes people install MediaBin service running under an account that does not have network permissions and that would explain the problem. The trick is to log in with the same permissions that the MediaBin service is running and try to access the desired share.

This is not the case for us.
The account is the same that was being used with version 4.01, and InsertAsset_UNC worked then...
We've also tried accessing the share containing the files to be inserted in MediaBin from the MediaBin server and using said account, and the files are visible.
It's only when using InsertAsset_UNC that we get an exception saying that the file is not visible.

Is anyone using InsertAsset_UNC with 4.5.3? Are we the only ones experiencing this problem?

[/QUOTE]

lyman

Did you upgrade the underlying operating system? Microsoft shuffled around permissions with Windows 2003. Do you have evidence that the user account can see other network shares or do you have reaosn to believe it is having trouble with all network shares?

Thanks,

Lyman Hurd

msnider

The web service checks for the existence of the file before it even sends the request to the MediaBin server. Therefore, if you are getting the following exception "The file is not available at the specified path: ", then that is probably because the MediaBinWebService web application user context does not have access to the UNC path.

What type of authentication are you using....Basic, NTLM, Anonymous?

Migrateduser

The web service checks for the existence of the file before it even sends the request to the MediaBin server. Therefore, if you are getting the following exception "The file is not available at the specified path: ", then that is probably because the MediaBinWebService web application user context does not have access to the UNC path.

What type of authentication are you using....Basic, NTLM, Anonymous?

No, that's not it. The mediabinwebservice site is running as NTLM + Basic, which is exactly the way it was working in version 4.01...

BTW, in order to be able to use the TeamSite/MediaBin connector we had to enable Anonymous access to the "transfer" folder, but even removing that does not solve the issue.

The exception is:


An unhandled exception of type 'System.Web.Services.Protocols.SoapException' occurred in system.web.services.dll

Additional information: Server was unable to process request. --> The file is not available at the specified path:  \\pmichlauw05521\DATest\TestFiles\Batmobile.jpg

Now, the other possible option is that this behavior is linked to the fact that we HAD to change the location of the transfer folder because of local infrastructure policy. I had to move the folder to another disk and then add it in the mediabinwebservice as a virtual directory. It is still shared as \\servername\TransferFolderWS.

Still, it works fine for everything but the InsertAsset_UNC (and I suppose ReviseAsset_UNC) method.

I really am rather confused...

lyman

I apologize for not being clearer. Basically nothing has changed in the underlying server request and so the issue must have to do with the intervening web services layer. I will let Mark suggest further ways to diagnose as this is not my area of expertise!

Cheers,

Lyman

db.txt

msnider

What permissions are on
"\\pmichlauw05521\DATest\TestFiles"? In particular does the ASP.NET worker process have access to that folder?

Can you successfully insert an asset if the file is located on the WebService's share..i.e. \\servername\TransferFolderWS?

Migrateduser

What permissions are on
"\\pmichlauw05521\DATest\TestFiles"? In particular does the ASP.NET worker process have access to that folder?

Can you successfully insert an asset if the file is located on the WebService's share..i.e. \\servername\TransferFolderWS?

Yes, if I use the GetUploadUNC method to create a folder under TransferFolderWS, copy the files in it, then user InsertAsset_UNC it works.

Trouble is, because of internal policy, we cannot give users delete rights on that folder... So the images will end up accumulating there (how often does the web service delete these temporary folders?)

Anyway, why should the ASP.NET worker process have access to that folder? In version 4.0, it was the user running the MediaBin Server service that needed access. Here the ASP.NET worker process is a machine-local account, so there's no way that it has access to that folder...

Migrateduser

Yes, if I use the GetUploadUNC method to create a folder under TransferFolderWS, copy the files in it, then user InsertAsset_UNC it works.

Trouble is, because of internal policy, we cannot give users delete rights on that folder... So the images will end up accumulating there (how often does the web service delete these temporary folders?)

Anyway, why should the ASP.NET worker process have access to that folder? In version 4.0, it was the user running the MediaBin Server service that needed access. Here the ASP.NET worker process is a machine-local account, so there's no way that it has access to that folder...

So, does anyone have an idea about what we did wrong?