Can not start application from mapped unc rive, suspecting caspol

We have some trouble starting some custom applications from a mapped UNC drive at some terminal servers, others not. The terminal servers are Windows 2003 servers. One such application was possible to start after executing the following command:

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727>caspol.exe -m -addgroup 1.2 -url "file:///\\server\applicationshare\folder\*" FullTrust -n test

However, several other applications in the folder structure under the same path do not start. There is no error message, nothing logged in eventviewer, and nothing appears when running the exe file. Tried an process monitor trace, wich shows that the exe file executes, digs around in C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\CONFIG, then searches in several registry keys such as HKCU\Software\Microsoft\Windows\CurrentVersion, goes through a bunch of dll's, reads through what looks to be the GAC and then issues a Process Exit with the following information:

Exit Status:      -532459699
User Time:      0.0156250 seconds
Kernel Time:      0.1406250 seconds
Private Bytes:      8 126 464
Peak Private Bytes:      8 318 976
Working Set:      8 863 744
Peak Working Set:      9 043 968

I have verified that C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\CONFIG\security.config contains the settings I have  been trying to add, both with mapped UNC drive letter in the path and full clean UNC path.

I am unsure on how to troubleshoot further, any ideas?
LVL 2
itniflAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

itniflAuthor Commented:
.Net 3.0 and .Net 3.5 were missing on the terminal servers where this problem occured. Installing this fixed  the problem.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.