i developed a website already and it was hosted in live too. My Problem is , site take a very long time to load , it take nearly 30-60 seconds to open , once it opened then it is some what better, MY Url Ishttp:\shoesrus.msinternational.bizplease verify and give me a solution , is their is any setting changes has to be taken in iis or server side etc..
I have developed an application in asp.net with crystal report. It has more than 30 pages in the project. Now I want to improve the performance of the application.1. What I need is , I want to know each and every page loading time and where actually it take long time to load while requesting the page.There are so many tools available. But am not able to follow as where actually the problem is and how to solve.
When I Publish my website it takes around an hour and a half. This is publishing to a directory on my local machine, it is not FTP'ing to a remote server. The build seems to take about an hour (when I build without publishing it is noticeably slow, but 5 minutes slow, not an hour), then the publish seems to take a further half an hour.
what could be causing this and how I can improve this? This obviously causes issues when I make a change (I'm constantly updating the site) as I need to wait for an hour an a half. I'm considering not precompiling the site now and simply uploading the .aspx and .cs files direct to the server as this is unmanageable for me.
After this message is displayed , no pages is able to access ....
The error message is :
Validation of viewstate MAC failed. If this application is hosted by a Web Farm or cluster, ensure that <machineKey> configuration specifies the same validationKey and validation algorithm. AutoGenerate cannot be used in a cluster
i have a web aplication in asp.net 2.0. i have configured it using IIS when i am trying to access the webpage even thr' the IIS , the page is not getting displayed.there is no error msg nor any msg , but nothing appears even for a very long timethe webapplication was wrking fine 2 days back
after nearly 5 mts i get a msg Thread was being aborted. Description: An unhandled exception occurred during the execution of the current web request. review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Threading.ThreadAbortException: Thread was being aborted.
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
My ASP.NET website while trying to connect to the database for first time after a period of inactivity throws an time out exception.
I understand the connections in the connection pool get terminated after some idle time for some reason (Firewall or Oracle settings) and the pool or app doesn't have a clue about it.
Is there any way to validate the connection beforehand so that the first try doesn't throw an exception? I don't have much control over the DB or Firewall settings. So I have to deal with this is my application.(would prefer if there is any web.config settings)
I am using: ASP.NET 2.0. Oracle server 11g, Microsoft Enterprise Library DAAB to do all my DB operations.
I have an IIS 6.0-based C#/ASP.NET web site with a SQL server backend.I want to generate some computationally expensive reports (summaries, search engine indexes, etc...) in idle CPU time. I need the reports to be generated from WITHIN the IIS App Pool so it knows the proper configuration settings and (harder to fix) avoids the nightmarish security restrictions I've been placed under.
Can I start threads inside the AppPool's process that won't tie up the CPU, so it can continue serving requests unfettered? If so, how? What code and libraries?
I imagine it involves ThreadPool and thread priorities, but I couldn't find good coverage of low-pri threads and their interaction with the IIS web server and App pool.
[EDIT] [URL] discusses using a Timer for this but doesn't directly state that the .NET framework will insure that the Timer thread is low-priority. This might be a solution, but is that assured?
[EDIT] Interestingly, Stack Overflow itself seems to use IIS background threads for my purpose:
[URL] in the comments, everyone says their (no longer used) technique sucks, but this one in the comments makes sense to me...
i made an web application for my client, he is from usa, I deployed application to [URL], at my local system, the project function proper. But what is happening that at main server the session is destroying automatically, before the idle time. I have been figuring out this problem for long but could not solved it. what may be the reason behind this session out. I am using in process session.
in my page i dessigned Updatepanel within that i placed some input controls(textbox, dropdownlist etc) within that updatepanel i placed one button. now the problem is on production if i idle some time after enter some data and press the button then the button click event not fired, then i refresh the page enter the input then press button then its fired, what is the problem? and how to resolve it? (i didnt included any triggers)
I am working on a web application in C#. I am using FormsAuthenticationTicket to authenticate the user. The user's information is check against a sqlserver database, if the correct credential is entered, (combine the username and password, encrypt them using the FormsAuthentication, and assign the random number generated to a session.), the users is redirected to a welcome pages.
However, I notice that there are times when I run the application, and it takes over five minutes to display the login screen, or I have to stop and start the application in order to display the login screen . Does anyone have an idea what may cause this issue?
We developed an application in ASP.NET 3.5 on Windows Server 2003. (IIS 6.0)They are trying to deploy it on Windows Server 2008 IIS 7.5.But we are getting the old yellow screen message: Runtime ErrorDescription:
Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.
An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed.Details: To enable the details of this specific error message to be viewable on the local server machine, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "RemoteOnly". To enable the details to be viewable on remote machines, please set "mode" to "Off".We have turned off custom errors everywhere we can find in ASP.Net Error Pages and set it to Detailed Errors at all folder levels for IIS Error Pages.Still the yellow screen with custom errors and no detailed errors.If we switch the application pool to run in 32 bit = true, we get a detailed error. But we don't get very far with that because of Oracle issues and wouldn't really want to force it to run in 32 bit when it should really run in 64 bit anyway.So how do we get detailed messages from IIS while running in 64 bit?