Different behavior of IIS with different application url

[mrudkhane]

I'm using Silverlight and RIA Service and Entity Framework. The problem is when users connect to the application and Application wants to connect to the database with a simple opening connection and close it to check connectivity, its service fails. The url that has this problem is:

http://192.168.1.1/main/index.aspx

I added an application to the IIS with 'test' name and the same directory as the 'main' application. The url is:

http://192.168.1.1/test/index.aspx

With this url, the application works good and does not any problem with the connection.
In fact, at this time, all users only connect to the first url(main) and all of their transaction load is on that.
What is the reason of this behavior?

[Frinavale]

It would be helpful if we could see any error messages in the Windows Event logs of your server regarding accessing the http://192.168.1.1/main/index.aspx URL.

-Frinny

[mrudkhane]

Event code: 4005
Event message: Forms authentication failed for the request. Reason: The ticket supplied has expired.
Event time: 7/16/2013 3:02:32 PM
Event time (UTC): 7/17/2013 3:02:32 AM
Event ID: 91301e4c8e0c483 5aeaef0305c0b2d d8
Event sequence: 47245
Event occurrence: 5077
Event detail code: 50202

Application information:
Application domain: /LM/W3SVC/1/ROOT/S4-4-130184963392159 384
Trust level: Full
Application Virtual Path: /S4
Application Path: E:\publish\S4\
Machine name: MTAHRA

Process information:
Process ID: 10920
Process name: w3wp.exe
Account name: IIS APPPOOL\Default AppPool

Request information:
Request URL: http://192.168.1.1/S4/Services/S4-Si.../binary/Search
Request path: /S4/Services/S4-SilWeb-Services-ReceptionServic e.svc/binary/Search
User host address: 192.168.1.1
User:
Is authenticated: False
Authentication Type:
Thread account name: IIS APPPOOL\Default AppPool



In fact, I want to know that what is the plan of IIS to handle processes on a url. Waiting of one of them will cause waiting of all of them or it handles processes in parallel. or any other information like this that may help me to know more.

[Frinavale]

Here is a link that covers what happens when IIS handles a request: IIS Request Processing.


Your error seems to have nothing to do with your database connection but rather to do with needing the user to re-login since the authentication ticket has expired....

-Frinny