An unexpected error has occurred on this page.The system administrators have been notified.
I try to access de default.aspx but always get the following error. I changed my polls.config to fs as new with FileAccess.Read but same result. Any idea ?


The error occurred in:
http://localhost/ThePhileVB/Default.aspx

Error Message:
Unable to generate a temporary class (result=1).
error CS0009: Metadata file 'C:\WINDOWS\Microsoft.NET\Framework\v1.0.3705\Temp orary ASP.NET Files\thephilevb\bd099721\6bf86bc9\assembly\dl\332 a6843\178886c9_0806c401\Wrox.WebModules.Polls.Conf iguration.DLL' could not be opened -- 'Access denied. '

Navigate in Windows Explorer to C:\WINDOWS\Microsoft.NET\Framework\v1.0.3705\ and give the ASPNET user account Full Control to the 'Temporary ASP.NET Files' folder.

Refer to this posting on how to do it:

http://p2p.wrox.com/topic.asp?TOPIC_ID=10774

I read a lot on the subject before sending my problem. I don't have any answer for now. Still have this problem.

I gave permission for temp folder, ASP temporary folder. I work with WIN XP PRO and my DB is on a server name SBS. Any other idea.

System.InvalidOperationException: Unable to generate a temporary class (result=1).
error CS0009: Metadata file 'C:\WINDOWS\Microsoft.NET\Framework\v1.0.3705\Temp orary ASP.NET Files\thephilevb\bd099721\6bf86bc9\assembly\dl\332 a6843\f07a6309_0c06c401\Wrox.WebModules.Polls.Conf iguration.DLL' could not be opened -- 'Accès refusé. '

   at System.Xml.Serialization.Compiler.Compile()
   at System.Xml.Serialization.TempAssembly..ctor(XmlMap ping[] xmlMappings)
   at System.Xml.Serialization.XmlSerializer.GenerateTem pAssembly(XmlTypeMapping xmlTypeMapping)
   at System.Xml.Serialization.XmlSerializer..ctor(Type type)
   at Wrox.WebModules.Polls.Configuration.ModuleConfig.G etSettings() in C:\Wrox\ThePhileVB\WebModules\Polls\Polls.Configur ation\ModuleConfig.vb:line 28
   at Wrox.WebModules.Polls.Business.Question.GetCurrent Id() in C:\Wrox\ThePhileVB\WebModules\Polls\Polls.Business \Question.vb:line 224
   at Wrox.WebModules.Polls.Web.Controls.User.Poll.DataB ind() in C:\Wrox\ThePhileVB\WebModules\Polls\Poll.ascx.vb:l ine 260
   at Wrox.WebModules.Polls.Web.Controls.User.Poll.Page_ Load(Object sender, EventArgs e) in C:\Wrox\ThePhileVB\WebModules\Polls\Poll.ascx.vb:l ine 62
   at System.Web.UI.Control.OnLoad(EventArgs e)
   at System.Web.UI.Control.LoadRecursive()
   at System.Web.UI.Control.LoadRecursive()
   at System.Web.UI.Control.LoadRecursive()
   at System.Web.UI.Page.ProcessRequestMain()

Just install SQL-SERVER on my desktop and now, no problem with IIS and SQL-SERVER running in the same location. The app do very well. But if I try to change my connection string in every config file to my server where is the same ThePhile DB, I got the same error than before!!!!

How does your (initial) connection string look like?

Is your ASP.NET application running on a different machine than SQL Server?

Imar


---------------------------------------
Imar Spaanjaars
Everyone is unique, except for me.

 This is my 2 stringd
 1 - sqlConnectionString="data source=SBS;user Id=sa;password="

Sorry, and the other
sqlConnectionString="data source=(local);user Id=sa;password=" This is the good one. The other don't work. If I set identity impersonate to true than I receive an error, if false than I receive an not Trusted blablabla for (sa). I install one SQL-Server ( the one on my desktop ) with SQL and Windows and the other ( on the server) only with Windows authentification.

If SQL Server on your Server uses SQL Authentication, you have to make sure that you use a Trusted Connection, and you shouldn't pass a user name and a password in the connection string.

You'll also have to make sure that the SQL Server trusts the account that IIS is running under. Usually this is the MachineName\ASPNET account, or IWAM_MachineName.

In both cases, this is a local account, so you can't directly add these users to SQL Server.
What you could do is create a mirrored account; that is, set an explicit password for the ASPNET account, and created an identical account at the SQL Server with the same password.
Give this user sufficient access to your database and server.

Alternatively, switch to SQL Server authentication and pass a user id and password. IMO, this isn't recommended as it forces you to pass (unencrypted) passwords around.

Search this form for "trusted", "aspnet" and "sql server" for more posts about this subject. For example:
http://p2p.wrox.com/topic.asp?TOPIC_...,server,aspnet
http://p2p.wrox.com/topic.asp?TOPIC_...,server,aspnet



Imar


---------------------------------------
Imar Spaanjaars
Everyone is unique, except for me.