Page 1 of 1
Request for the permission of type 'System.Security.Permissions.EnvironmentPermission, mscorlib, Version=2.0.0.0, Cultur
Posted: Tue 09 Jan 2007 15:18
by farshore
Hiya we are getting the following error on a site we have deployed "
Request for the permission of type 'System.Security.Permissions.EnvironmentPermission, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed.
Can you pleeease tell me what is causing this
Thanks
Posted: Wed 10 Jan 2007 07:41
by Alexey
Please describe when exactly this error occurs.
As I remember, your vevida_net-2.0.config file differs a bit from default web_mediumtrust.config file (particularly in EnvironmentPermission section). So maybe this is the problem.
'System.Security.Permissions.EnvironmentPermission, mscorlib, Version=2.0.0.0, Cultur
Posted: Wed 10 Jan 2007 10:32
by farshore
It happens when processing a request to return data to the DB
this works but it generates the error message I posted.
I know that the hosting party are running their own config file but does this mean that corelab can only ever be deployed on a dedicated server and never in a shared hosting enviroment.
Is that point clear in the documention so other developers are aware that they should never try to run corelab on a normal hosted enviroment?
We are also trying to resolve a MySqlserver has gone away issue have you got any clues for me on that error too
Thanks
Posted: Wed 10 Jan 2007 11:43
by Alexey
Web sites written with MySQLDirect .NET can be deployed in a shared hosting enviroment as well, provided that trust level is at least medium.
As for "MySQL Server has gone away" problem, this error could happen if there was connection break or you were more then eight hours on one connection. For more information about this problem take a look
here
Request for the permission of type 'System.Security.Permissions.EnvironmentPermission, mscorlib, Version=2.0.0.0, Cultur
Posted: Wed 10 Jan 2007 14:53
by farshore
Hi Alexey
I saw this documentation but is it usual for a hosting party to leave an open DB connection for eight hours per session.
Thanks
Posted: Thu 11 Jan 2007 07:13
by Alexey
This is a hypothetical question. There are not only one reason why that error could happen.