I did send ISP the doc for the permissions (I will though send them the doc you sent me because it is different from what I sent them).
It does keep freezing and they did recycle the app (been like this for like 2 weeks now, I am interested in getting it to work with them once and for all because they offer good stuff).
- Kill the app pool without restarting it (e.g. touch the web.config, but make no further requests)
- Go to the /data/_systemUmbracoIndexDontDelete folder and delete its contents (not the folder, just the innards)
- Now try making a request again. Monitor the folder contents to see if within minutes you get new files
The current implementation of Lucene indexing is pretty broken and can sometimes crash the worker process if the index is corrupt. Deleting the index like this (which is what you've done by deleting the files) causes a fresh one to be made on app startup. Obviously it's an edge case and might not apply in your scenario - Let me know how you get on
I'm afraid I can't think of any edge-case gotchas remaining now after the other posts in this thread, due to the lack of specific details.
I recommend you go through the handlers commenting them out of the web.config file one-by-one until you at least get a more informant .NET error and let us know the details of your results. This should help isolate the problem.
Another avenue is to write a blank page that tries the same database connection string, makes a simple read, and closes the connection; check that works. You'll have to exclude the file from Umbraco's handling of course, by editing Umbraco's excluded paths config, but you want it to run in the same application so that you can test the existing web.config.
static public string GetSqlAsString(string sqlText, SqlParameter[] sqlParameters, string databaseConnectionString) { string result = ""; SqlDataReader reader; SqlConnection connection = new SqlConnection(databaseConnectionString); using (connection) { SqlCommand sqlcommand = connection.CreateCommand(); sqlcommand.CommandText = sqlText; if (sqlParameters != null) { sqlcommand.Parameters.AddRange(sqlParameters); } connection.Open(); reader = sqlcommand.ExecuteReader(); if (reader != null) if (reader.Read()) { result = reader.GetString(0); } } return result; }
</script> <html> <head> <title> ASP .NET Testpage </title> </head> <body> <p><% Response.Write("Welcome to the ASP .NET test page<br>"); Response.Write("Local Time: " + System.DateTime.Now.ToLocalTime() + "<br>"); %> <% // Response.Write (GetSqlAsString("select * from cmsMacro", null, umbraco.GlobalSettings.DbDSN)); %> </p> </body> </html>
And then the test.aspx crashed!
So now I will try to exchange the umbraco.GlobalSettings.DbDSN with the connection string and see if it works, but first I will have to get the site up running again. So back to scratch :P
Oh first I will go to backend and publish and see if files are rebuild of course.
No new files on publish, but they shouldn't be rebuild when published anyways.
So I will try rename the umbraco.config and see if that gets rebuild. And it does!
Well now on to the hit the frontend show again :D - and it ..... ..... .... worked..... well that is odd! Maybe they did something with the permissions? I asked them to give network service the correct permissions.
Hmmm does it seem to be solved now?
Conclusion: If umbraco crash - then give network service the correct permissions?!
Umbraco dying at the requestModule in web.config, why?
Umbraco dying at the requestModule in web.config, why?
Sorry for the double post on this but I really need it fixed, does anyone has the sligthest idea what this could be?
The settings for the website is just about the same on another server running more than 20 solutions.
I have added a <trust level="Full" /> to the web.config to see if that helped, but no luck.
Thank you all
1. Check that all the .dll's are in the bin folder.
2. Make sure your web.config is not malformatted xml.
3. Post the error presented / trace.
All .dlls are newly uploaded and I hit the backend and it worked.
Then I hit the frontend and it died...
No errors, no trace, no nothing :( it is really annoying.
Web.config is the one I always use, no modifications, no nothing as well.
YSOD?
ysod eh? :P
yellow screen of death, the error message.
Or is the page just plain blank? In that case, have you assigned a template to the page?
well nothing really. right now it comes with an error in the browser, seems like it times out for some reason.
and no ysod either. just a regular browser error message (usually point to an internal 500 error).
Do you have a url where I can see? You're not giving me much to go on here :)
sorry Stephan, of course (try the backend first, have patience):
http://www.soctt-hugh.com/umbraco/umbraco.aspx which does work (if you do not try to enter the frontend as well)
http://www.soctt-hugh.com/ which does not work
I have just touched the web.config so the app should have been restarted.
Sorry, no go. No response in over 3 minutes, what are you running the site off, a modem? ;)
Have you added any httpModules yourself, or is everything standard?
Running IIS7 with integrated pipeline mode? - Have you added the system.webServer config section?
everything is standard no packages installed at all.
I got a internet explorer cannot show the page etc...
running windows 2003, iis 6, and site is running off a 100/1000 :D enom.con connection.
I left it for 5 minutes and came with the above from the browser.
hey scott, here are some suggestions.
1) Maybe it's time to try and get it running on fresh install and work backwards.
2) Here are some docs on how to install on IIS6. Take note on the files you need give permissions too.
http://umbraco.org/documentation/books/install-umbraco-4-on-windows-vista/configure-iis-website
3) if you website freeze like it's doing at the mo. Send a request to isp asking them to recycle the app pool
good luck, sounds painful :)
It is totally fresh :S
I did send ISP the doc for the permissions (I will though send them the doc you sent me because it is different from what I sent them).
It does keep freezing and they did recycle the app (been like this for like 2 weeks now, I am interested in getting it to work with them once and for all because they offer good stuff).
Thank Anthony.
Hi Scott,
Try the following:
- Kill the app pool without restarting it (e.g. touch the web.config, but make no further requests)
- Go to the /data/_systemUmbracoIndexDontDelete folder and delete its contents (not the folder, just the innards)
- Now try making a request again. Monitor the folder contents to see if within minutes you get new files
The current implementation of Lucene indexing is pretty broken and can sometimes crash the worker process if the index is corrupt. Deleting the index like this (which is what you've done by deleting the files) causes a fresh one to be made on app startup. Obviously it's an edge case and might not apply in your scenario - Let me know how you get on
Cheers,
--
Alex Norcliffe
Umbraco Core Dev, Consultant Architect
- www.boxBinary.com
- [email protected]
International Tech Lead, Condé Nast Digital
- Vogue.com / Wired.co.uk / GQ.com
Hmm not working either - permissions should be in order - Umbraco said that the settings were perfect.
I can't even get a trace on it because it just seems to time out for some reason.
Did that folder get new files after you tried to warm-up the app again? This will help in knowing where to look next
--
Alex Norcliffe
Umbraco Core Dev, Consultant Architect
- www.boxBinary.com
- [email protected]
International Tech Lead, Condé Nast Digital
- Vogue.com / Wired.co.uk / GQ.com
No new files... buhuu...
I'm afraid I can't think of any edge-case gotchas remaining now after the other posts in this thread, due to the lack of specific details.
I recommend you go through the handlers commenting them out of the web.config file one-by-one until you at least get a more informant .NET error and let us know the details of your results. This should help isolate the problem.
Another avenue is to write a blank page that tries the same database connection string, makes a simple read, and closes the connection; check that works. You'll have to exclude the file from Umbraco's handling of course, by editing Umbraco's excluded paths config, but you want it to run in the same application so that you can test the existing web.config.
--
Alex Norcliffe
Umbraco Core Dev, Consultant Architect
- www.boxBinary.com
- [email protected]
International Tech Lead, Condé Nast Digital
- Vogue.com / Wired.co.uk / GQ.com
I will put in another web.config and give it over night and do the above - hopefully it will have reset the app pool and everything..
Thanks Alex, I will be back if not tomorrow then Monday.
Okay, I got the backend up running and checked that everything was okay.
Then I created a test.aspx and added it to web.config under reservedPaths and that worked as well.
Then I modified the page to contain the following:
And then the test.aspx crashed!
So now I will try to exchange the umbraco.GlobalSettings.DbDSN with the connection string and see if it works, but first I will have to get the site up running again. So back to scratch :P
Be back soon (hopefully)
Okay I got the retrieve from database working in the test.aspx directly with the umbraco.GlobalSettings.DbDSN.
So database is working.
Now I will try to hit the frontend and see what happens.
Oh first I will go to backend and publish and see if files are rebuild of course.
No new files on publish, but they shouldn't be rebuild when published anyways.
So I will try rename the umbraco.config and see if that gets rebuild. And it does!
Well now on to the hit the frontend show again :D - and it ..... ..... .... worked..... well that is odd! Maybe they did something with the permissions? I asked them to give network service the correct permissions.
Hmmm does it seem to be solved now?
Conclusion: If umbraco crash - then give network service the correct permissions?!
Permission problems, it was because some of the files for some reason had read-only.
Thanks to everybody who participated in finding a solution for me!
Scott
Special thanks to Alex!
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.