Click here to Skip to main content
15,908,015 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
See more:
Well this is a fun one. One of the web apps on our server has suddenly started throwing an error
IndexOutOfRangeException: Index was outside the bounds of the array.]
   WebServiceDeskPortalAdmin.MainPage.Page_Load(Object sender, EventArgs e) in C:\projects\WebServiceDeskPortalAdmin\WebServiceDeskPortalAdmin\MainPage.aspx.cs:0

Running the code locally displays no such error and runs as designed.

My thought is something amiss in the IIS setup but being a mere developer my IIs skills are sorely lacking and Our web/network admin training education consists of stackoverflow lurking.

the only other thing that might be at issues is that we are using CA Siteminder for user auth. but again there is no one here with any real training in that package.

The other app on this server works just the way it is supposed to.

The other odd thing is the file it is pointing to is the one on my local machine where the app is built and published before being copied to the server.

What I have tried:

I have tried starting and stopping the server. I have also compared the web config to the web config on another box running the same app and found no differences
Posted
Updated 11-Oct-18 9:15am
Comments
#realJSOP 11-Oct-18 14:08pm    
Did you recently edit a javascript file?
RmcbainTheThird 11-Oct-18 14:11pm    
There is no javascript in the app.

Because it's published to the server as a compiled file, and that applies optimizations and so forth which removes line numbers?

Because you probably can't debug "live code", you need to add logging to you app to try and narrow down exactly which arry and which index is involved. Given that it's probably also related to your data, we really can't do that for you!
 
Share this answer
 
Well being a lazy guy I never looked at my log files because the error was said to happen on line 0 and we all know there is no line 0 in source code. However I went and looked just be able to tell OldGriff his advice was bogus. Turns out the crash was several lines into the app and caused by me breaking on of my own rules and reusing a variable and then attempting to manipulate that variable with the assumption it still had the value from the first assignment (doing string split) I am a bad boy
 
Share this answer
 

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900