Cant access web708 with new site

Hi all

I signed up for a new account today, this being my second active account with DASP. The first site I have running with DASP seems to be working fine on web705, but my site new is having troubles loading.

I'm trying to get a MVC3 site running, but at the moment I am just using the alterntive URL since I dont have a domain name yet. Any time I accesss the URL I get a "No data received" message in Chrome. No errors, no 404, just no response whatsoever. Thinking it's something to do with MVC I placed a file called index.html in the root folder with the text 'test' in it, but it's having the same problem. I placed an image in the root folder and I was able to access it with directory browsing turned on, so the server at least appears to be working in some way.

The server is web708 and I see a thread with people having troubles with web 703 and 103. Is 708 down as well?

Anyone know what might be going on?

Cheers.

- Boolean

 

The ticket system appears to be broken. I tried creating a new ticket and got the error:

--------

Ticket needs group

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Exception: Ticket needs group

Source Error:

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.

Stack Trace:


[Exception: Ticket needs group]
SmarterTrack.Business.Tickets.TicketAssignments.SaveAndAssignTicketToAvailableAgent(TicketEntity ticket, Int32 userIdDoingAction, InterfaceUsedTypes interfaceType) +141
SmarterTrack.MRS.Main.frmNewTicket.SubmitIcon_Click(Object sender, EventArgs e) +4528
SmarterTools.Web.Controls.SimpleButton.RaisePostBackEvent(String eventArgument) +61
System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) +13
System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) +176
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +5563

 

Ticketing system is working again.

 

I can't replicate that error - so I'm not sure what may have happened. Please try opening a ticket again.

 

I contacted support but were unable to help, so after playing around with settings for a few days, I found removing this line from my code allows the site to run:


Thread thread = new Thread(BackgroundWorkerThread);
thread.Start();

I have this in my global.asax file which calls BackgroundWorkerThread, which calls a static method every 15 seconds.

My only thought is that creating new threads in a .NET application is not allowed on DASP?

 

Threading works. Can you give us the URL to the page?

 

http://steelnemesi.web708.discountasp.net/

At the moment the bit of code which spawns a new thread is commented out. Should I turn it back on?

 

mmmm, I think it's working now. I didn't have any problems running it locally, but I noticed in some situations the new thread would throw an exception. I figured if there was a problem I would see the error on screen, but I guess because it's in a different thread the whole site is grinding to a stop and all the information of the exception is hidden in the extra thread?

I'm a bit new to the whole multithreading thing, so when it worked fine locally I just assumed it should be working remotely. I just didn't notice that it WAS having a problem, but it was being lost in the extra thread.

Cheers guys