I'm getting an error message while trying to add Pi Web Parts which says:
A Configuration setting is missing from either machine.config or one of the web.config files. Setting 'RtWebPartsVDIR'
How do I fix it?
Related
I am using plesk'shared hosting server to host my website. Constantly getting ViewState MAC failed error
Plesk won't be able to provide any Machine Key. As it is shared hosting.
I have also attached the screenshot. please help.
Earlier This issue was coming in one page only. I have resolve it by converting it to JavaScript and ajax call in order to Stop AutoPostBack.
But now this is coming in many pagaes.
Add following link in your web.config file.
Above line should be included within section.
OR
if you don't want this solution to implemented on project level then you can add these attribute to the page(Top most line of HTML view) directive of the page which is creating issue.
That means you have to add enableEventValidation="false" viewStateEncryptionMode="Never" in page directive.
I already search all the web but can't find any problem similar.
Note: The following problem only occurs on production.
In my mvc website if i reload any page multiple times, css, javascript files and images begin to give "500 - Internal Server Error".
It doesn't happen with all the files. Some of the files that are giving the error are: fontawesome.min.css and chartnew.js.
If i call the files directly they work, but if i reload they begin to give the asp default error page "500 - Internal Server Error" without any other details (Already tried without custom errors and using detailed error view).
Any ideas?
Thanks.
Resolved removing this at the webconfig:
<urlCompression doDynamicCompression="true" doStaticCompressions="True" dynamicCompressionBeforeCache="true" />
In my case, I removed WebDav by clicking, Handler Mapping->WebDav module*->Request Restrictions->Verbs-> All verbs.
This will add an entry to your web.config. But then later I decided to remove WebDav from IIS (Remove Features). However, in the web.config, WebDav was still referenced.
Removed all references to WebDav in Web.config, and it worked.
Conclusion: When removing WebDav from IIS, make sure there is no reference to it in web.config.
I'm pretty new to SharePoint and IIS, but I haven't been able to find an answer to this one. I'm deploying a custom ASPX with code-behind to my SharePoint server and need a detailed stack trace to see where my problems are.
This involves modifying the web.config file and setting three attributes of certain tags: <SafeMode CallStack="true" AllowPageLevelTrace="true" /> and <CustomErrors mode="Off" />. There are lots of different web.config files, but my error messages change when I modify a certain one, indicating that I chose the right file to edit.
Error message
The problem, however, is that when I do change these tags, I only get an error message telling me the stack trace cannot be displayed remotely, even if I try to display the page on the server itself. The error message basically tells me that in order to get the complete stack trace, I have to do what I just did: Set CustomErrors mode="Off".
I have had this happen before, but only with certain types of errors (HttpModules).
Try checking the windows event log for a more detailed message. It should be there.
Also try restarting IIS/server to make sure its clean/all services are started.
I want to manage two web.config file in a application one for the front-end user and second for the back-end(admin) user.for admin section I have created a folder with name admin in the same website.following settiongs are in the admin/web.config
when I am trying to run the application I am getting following error message:
It is an error to use a section registered as allowDefinition='MachineToApplication' beyond application level. This error can be caused by a virtual directory not being configured as an application in IIS
Same problem have discussed on below
ASP.NET What causes: It is an error to use a section registered as allowDefinition='MachineToApplication' beyond application...?
It is an error to use a section registered as allowDefinition='MachineToApplication' beyond application level
Please give me some suggestion to solve this problem.
Thanks in advance
I faced same issue when I had a web application inside another web application resulting in two Web.config files.I deleted one and issue was solved.
As configuration settings in the child level can override the ones in parent level,this error can occur when you have 2 web.config files one redefining configuration settings that you cannot override such as authentication or session state. Issue happens when you may have authentication / session state set on the lower level web.config and also in higher level web.config
There are an enormous amount of
information on getting this error in
IIS. I have spent hours on issues
like this, because, there has never
been a CLEAR ANSWER.
You will hear things like
It means that if you have an application, you should not configure
the MachineToApplication settings in
web.config's in the subdirectories.
All you have to do is set the
MachineToApplication settings in your
Application's root, and they will be
inherited in the subdirectories.
Solution :
Configure all MachineToApplication
settings in your application's root,
and remove all MachineToApplication
settings from your application's
subdirectories.
What all of the answers FAIL TO
MENTION is that there are a myriad of
file permissions, security, etc..
going on with any file in IIS.
It used to be easier, but with the
increase in the proliferation, it is
getting much, much more complicated.
I have one solution which I have used
which got my IIS to work-
1st. Test a simple HTML page in a new
Web App. If you can get that to work,
then you should be good for the next
steps.
2nd. When you are thinking about the
issue that started this, you have a
Machine.config file in the
E:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\CONFIG
directory for your Framework.
This is the file that sets the Type
of AllowedDefinitions. ( look for
that in the config file)either
allowDefinition="MachineToApplication"
or allowDefinition="Machine"
When someone says you have to put
your web.config in your applications
"Root" Folder, depending on how your
application is setup, will dictate
where to put your web.config.
To get mine to work, I put it in the
E:\Inetpub\wwwroot folder.
3rd. You will have to test which
sections to include in the config
root folder, and which ones you can
put in your various web "Application"
folders.
4th. This is a work in progress, but
I wanted to get this out there while
I was working on it and it was fresh
in my mind...
I'll post more later when I iron out
more of the issues.
I plan to post an extremely detailed
explanation later on when I decipher
all of the cryptic, purposefully
undocumented, sometimes misleading,
information on the matter of configs,
etc. to get IIS running properly.
ie. I'm tired of hacking around
trying to get it to behave properly,
but I want to thoroughly test the
system out and document, EXACTLY what
needs to be done, and why, to get
applications up and running
quickly...
Thanks for reading this.
You need to set it as as an application in IIS.
I had the same issue when using a Kentico installation. Admittedly this is no silver bullet, but in this case it was because one of the base templates CorporateSiteAspx had its own webconfig file containing configuration settings that used requirePermission="false" allowDefinition="MachineToApplication"
On excluding this file (which wasn't used anyway) the application built successfully.
I am doing a Web Deployment of my website and I have the merge assemblies property set to true.
For some reason I get the following error.
aspnet_merge : error occurred:
An error occurred when merging assemblies: The relative virtual path 'Global.asax' is not allowed here.
It seems to have something to do with the Global.asax, but I'm not really sure why its getting truncated. My code compiles locally fine, but its only the merge that is messing up.
Any ideas?
As a shot in the dark:
Is it a slash issue? I vaguely remember MSBuild forcibly requiring a trailing slash on some of its properties.