Which Log to check

On my qa server I have teamsite pages that are throwing web page not found errors.

Is there a logfile I can check to gather more information on this error? Its an IIS http 400 Bad Request Error or something of that nature.

Find more posts tagged with

Comments

curiousmaverick

try iwproxy -d

Venus00

can also look into "servletd.log" and "access.log" resides at iw-home/local/logs/iwui

Migrateduser

When you say "TeamSite pages", do you mean pages from the TeamSite GUI (like you click the admin link and get the error) [these would be served up by iwservletd, frontended by iw-webd], or do you mean content pages within TeamSite [these would be served up by your customer web server, front ended by iwproxy]. I'm assuming you mean the latter, but I've seen cases of the former where iw-webd wasn't able to start and people were hitting CCPro via iwservletd directly (i.e., specifying the port for connecting in the url).

shougom

I mean from the content center. Check out the attached screen.

nipper

Could be a bunch of things. You may want to run iwproxy in debug mode.

Does this happen for everything (.html, etc) or for a certain type of file

Is the webserver running ? try http://yourserver:81/

shougom

I tried a test html page and it loaded fine.

Its whenever I try and aspx page. One thought was maybe the IIS scriptmaps needed to be rebuilt with aspnet_regiis.exe but...thats a wild guess.

shougom

Another thought I had was port 81 was being blocked. But the system admin said it wasnt.

shougom

http://rochsvr42:81/

See attached. Its not down.

nipper

How have you configured IIS to render ASPX files in TeamSite

Had you posted that HTML worked but ASPX doesn't you would not have wasted nearly as much time as you have lost.

Talk to A/I support, there is a KB with instructions to render ASPX inside a workarea. There are a few changes you need to make.

Adam Stoller

I tried a test html page and it loaded fine.

Its whenever I try and aspx page. One thought was maybe the IIS scriptmaps needed to be rebuilt with aspnet_regiis.exe but...thats a wild guess.

Yes, you need to make sure all the ASP/ASPX extensions are loaded in the local IIS server running (presumably) on port 81.

shougom

Uh nipper first of all how about responding with some class...I appreciate the help and that your smarter than me but i came here for help not to be disrespected. Im new to these concepts ok i have 0 experience working with any CMS at all. Were all in this together.

shougom

Thanks ghoti I will check that out.

Adam Stoller

Uh nipper first of all how about responding with some class...I appreciate the help and that your smarter than me but i came here for help not to be disrespected. Im new to these concepts ok i have 0 experience working with any CMS at all. Were all in this together.

His response had nothing to do with smartness - his response was pretty basic: The more detailed your initial post is, the more detailed and focused your responses will tend to be - and the fact that you left out key information in the original post(s) means that you wasted some time (ours and yours) trying to arrive at the information you finally got -- fortunately, it was only about 1 day's worth of time, but sometimes every minute counts and the more diligent you are the better (generally) the results.

shougom

Ran aspnet_regiis - but no luck. aspx pages till saying page not found.

shougom

Sorry I call em like I see them...ive seen some of your posts too. Sorry to waste your time. Ive been a developer 16 years and am mcsd so Id appreciate a little respect. You dont like the post...dont respond. It doesnt matter what a person leaves out if they dont know what the problem is. Im a developer not a server admin so naturally Im not 100% up on what to do in IIS or Windows server. So I think your being way out of line here. Have it your way but dont respond to any more of my posts I dont want your brand of help ghoti. If someone leaves something out you can tell them politely not drag them through the mud to boost your own ego.

Migrateduser

Are you sure your web server is setup to allow ASP pages? By default in Windows 2003 ASP is disabled. Go in to IIS and go under Web Service Extensions. Check if Active Server Pages is set to Allowed.

shougom

I did check the extensions in IIS and both asp and aspx are allowed.

Thanks taalgaard

Migrateduser

Can you repeat this on other desktop machines?
What is the full url in the error screen?
Can you attach the source code for the asp page so that we can see if there is an error there?
Can you put the asp page on another server and see it work there, if not, then maybe there is an error in the asp code.

shougom

All the server pages throw IIS 400 or 404 errors. I dont believe its a code error or it would redirect to our 404.aspx page we have custom errors turned on in web.config.

See attached screenshots for asp errors and aspx errors.
asp error url
http://localhost:81/iw-mount/default/main/Internet/rochestermn.gov/WORKAREA/TS_Admin/sitemap.asp

aspx error url
http://localhost:81/iw-mount/default/main/Internet/rochestermn.gov/WORKAREA/TS_Admin/Default.aspx

Migrateduser

Search support for "tsimp asp". You should find things ranging from making sure your tsimp user account is active to what local permissions it needs as well as adding .NET account to your TeamSite Web Preview group.

I am also assuming you replaced your server name with localhost in both your urls and the screen shots when you posted here. If not, and you're using localhost, then you must be on the server using it's browser, correct?

Have you tried a basic asp page with just hello world in it?

shougom

I did a search for tsimp there is alot of info. thanks for the tip.

I also created a new hello world in vs.net and copied it to the teamsite server and ran it and got the same error.

This could be alot of things it sounds like including permissions. It looks like on the website security we have tsimp_servername as the user and anonymous checked. Still digging.

k1DBLITZ

One little tip that can help when using IE, make sure and uncheck 'display friendly HTTP error messages" under Tools > Internet Options > Advanced.

This will allow you to see a more meaningful error message.