Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post Nov 08, 2012 09:48 PM by awihere
Nov 07, 2012 03:48 PM|LINK
An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.
Parser Error Message: Could not load type 'GasSta.SiteMaster'.
Line 1: <%@ Master Language="VB" AutoEventWireup="true" CodeBehind="Site.master.vb" Inherits="GasSta.SiteMaster" %> Line 2:
Line 3: <!DOCTYPE html>
/Site.Master Line: 1
Nov 07, 2012 07:38 PM|LINK
Just change Inherits="GasSta.SiteMaster" to Inherits="SiteMaster"
It will solve your problem
Nov 07, 2012 09:20 PM|LINK
I tried your suggestion but it did not work for me.
I tested this in two ways. First I changed it in Visual Studio and ran it on the local host and it failed with the error message found on the website.
I then ignored that and built the site which it did successfully and then published that to the remote server.
I got the same error except the new error on the remote server correctly reflected the drop the GasSta.
Maybe there is something else you can suggest?
Nov 08, 2012 02:10 AM|LINK
What net version running your app_pool in iis?
Nov 08, 2012 11:46 AM|LINK
The server is set to run either net 2.0 or 4.0. My program is written to 4.0.
If the 4.0 is not being used would the error message not tell me that? The configuration file spells out 4.0 for the code.
I am using Visual Studio Express 2012 Web. I am using FileZilla to upload the files.
Is there a dll that could be missing or a particular file that is missing?
Your assistance is very much appreciated.
Nov 08, 2012 07:21 PM|LINK
write page name in Inherits. Suppose your page name is pankil.master the write
Nov 08, 2012 09:17 PM|LINK
I tried what you suggested but it failed both on the remote server and the local host.
There must be some file that I am missing on the remote server that is on the local host.
I appreciate your help. If you have additional thoughts, please let me know.
Nov 08, 2012 09:48 PM|LINK
Thank you all for your assistance. I decided to reload the entire site to see if that would find a file that was missing.
That solved the problem and the problem is now fixed.
So the cause must have been a missing or damaged file.