Welcome to HostingForumz.com!
FAQFAQ      ProfileProfile    Private MessagesPrivate Messages   Log inLog in

IISstate log analysis

  
   Web Hosting Problem Solving Community! (Home) -> IIS RSS
Next:  IIS serves empty page  
Author Message
user944

External


Since: Oct 10, 2003
Posts: 22



(Msg. 1) Posted: Tue Aug 10, 2004 8:42 pm
Post subject: IISstate log analysis
Archived from groups: microsoft>public>inetserver>iis (more info?)
Hi

Could anyone point me in the direction of where to start with the problem
below. IIS stops serving ASP pages, just eventually times out, but html
pages are fine, have to restart www service to fix.

Thanks in Advance

Stephen

____________________________________________________________________

Thread ID: 19
System Thread ID: 8c
Kernel Time: 0:0:2.546
User Time: 0:0:4.906
Other information: Thread is waiting for a lock to be released. Looking for
lock owner.
Owning thread System ID: 1e4
Thread Type: Jet DB Query. Possible ASP Page
Executing Page: D:\INTRANET\INDEX.ASP

# ChildEBP RetAddr
00 029dcd04 77f43741 SharedUserData!SystemCallStub+0x4
01 029dcd08 77f5d64e ntdll!ZwWaitForSingleObject+0xc
02 029dcd44 77f42044 ntdll!RtlpWaitForCriticalSection+0x126
03 029dcd4c 1b0058cc ntdll!RtlEnterCriticalSection+0x46
04 029dd244 02fa75ec msjet40!WZLocalTransporterID+0x24
05 029de3a8 02fa8da4 odbcjt32!SQLConnectCover+0x395
06 029de3dc 00fb1c0f odbcjt32!SQLDriverConnectW+0x3d
07 029de420 00fb18cb ODBC32!SQLInternalDriverConnectW+0x142
08 029deb64 02e82049 ODBC32!SQLDriverConnectW+0x6ba
09 029debcc 02e821d0 msdasql!CODBCHandle::OHDriverConnect+0x80
0a 029debec 02e82313 msdasql!CHdbcNode::DriverConnect+0x20
0b 029dec30 02de4602 msdasql!CImpIDBInitialize::Initialize+0x161
0c 029dec5c 02de46a3 oledb32!CDBInitialize::DoInitialize+0x32
0d 029dec8c 02de2d75 oledb32!CDBInitialize::Initialize+0x58
0e 029ded38 75610dfe oledb32!CDCMPool::CreateResource+0x1fa
0f 029ded74 75612301
comsvcs!CHolder::SafeDispenserDriver::CreateResource+0x25
10 029dedd0 02de3319 comsvcs!CHolder::AllocResource+0x325
11 029dee20 02de4748 oledb32!CDCMPool::DrawResource+0x9d
12 029dee78 02de320e oledb32!CDCMPoolManager::DrawResource+0x185
13 029deed8 02ab6a9b oledb32!CDPO::Initialize+0x136
14 029defd8 02ab6c37 msado15!_ConnectAsync+0x1da
15 029defe8 02ab694e msado15!ConnectAsync+0x1f
16 029df158 02ad0d8d msado15!CConnection::Open+0xa26
17 029df3dc 7348b427 msado15!CConnection::Invoke+0xb63
18 029df430 7347f39c vbscript!CatchIDispatchInvoke+0x46
19 029df47c 7346368c vbscript!IDispatchInvoke+0x95
1a 029df590 73462f95 vbscript!InvokeDispatch+0x138
1b 029df5b4 734635ef vbscript!InvokeByName+0x40
1c 029df890 73463c33 vbscript!CScriptRuntime::Run+0x2625
1d 029df994 73463d42 vbscript!CScriptEntryPoint::Call+0x65
1e 029df9f8 73464081 vbscript!CSession::Execute+0xb6
1f 029dfa48 734640ee vbscript!COleScript::ExecutePendingScripts+0x14a
20 029dfa64 709e5e87 vbscript!COleScript::SetScriptState+0x14e
21 029dfa90 709e5ee1 asp!CActiveScriptEngine::TryCall+0x17
22 029dfacc 709e5f21 asp!CActiveScriptEngine::Call+0x31
23 029dfae0 709e6227 asp!CallScriptFunctionOfEngine+0x21
24 029dfb18 709e6393 asp!ExecuteRequest+0x138
25 029dfb60 709e5573 asp!Execute+0x16a
26 029dfbb0 709e5726 asp!CHitObj::ViperAsyncCallback+0x3ec
27 029dfbd0 75633107 asp!CViperAsyncRequest::OnCall+0x8c
28 029dfbec 77204c67 comsvcs!CSTAActivityWork::STAActivityWorkHelper+0x30
29 029dfc38 7720539a ole32!EnterForCallback+0xc0
2a 029dfd98 771e03a4 ole32!SwitchForCallback+0x194
2b 029dfdc4 771c7e10 ole32!PerformCallback+0x52
2c 029dfe48 77207984 ole32!CObjectContext::InternalContextCallback+0x140
2d 029dfe68 756332b3 ole32!CObjectContext::DoCallback+0x1a
2e 029dfed4 756337ad comsvcs!CSTAActivityWork::DoWork+0x137
2f 029dfee8 75633f71 comsvcs!CSTAThread::DoWork+0x14
30 029dff04 7563423b comsvcs!CSTAThread::ProcessQueueWork+0x30
31 029dff84 77bc91ed comsvcs!CSTAThread::WorkerLoop+0x17a

 >> Stay informed about: IISstate log analysis 
Back to top
Login to vote
patfilot

External


Since: Aug 24, 2003
Posts: 1478



(Msg. 2) Posted: Tue Aug 10, 2004 8:42 pm
Post subject: Re: IISstate log analysis [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
Is this IIS6? This looks like the Jet bug. You'll need to contact support
to obtain it (ask for fix from KB Q838306).


Pat

"sdm" <stephen.moss.DeleteThis@bradford.gov.uk> wrote in message
news:_7ucncOjXpt-Z4XcSa8jmw@karoo.co.uk...
 > Hi
 >
 > Could anyone point me in the direction of where to start with the problem
 > below. IIS stops serving ASP pages, just eventually times out, but html
 > pages are fine, have to restart www service to fix.
 >
 > Thanks in Advance
 >
 > Stephen
 >
 > ____________________________________________________________________
 >
 > Thread ID: 19
 > System Thread ID: 8c
 > Kernel Time: 0:0:2.546
 > User Time: 0:0:4.906
 > Other information: Thread is waiting for a lock to be released. Looking
 > for
 > lock owner.
 > Owning thread System ID: 1e4
 > Thread Type: Jet DB Query. Possible ASP Page
 > Executing Page: D:\INTRANET\INDEX.ASP
 >
 > # ChildEBP RetAddr
 > 00 029dcd04 77f43741 SharedUserData!SystemCallStub+0x4
 > 01 029dcd08 77f5d64e ntdll!ZwWaitForSingleObject+0xc
 > 02 029dcd44 77f42044 ntdll!RtlpWaitForCriticalSection+0x126
 > 03 029dcd4c 1b0058cc ntdll!RtlEnterCriticalSection+0x46
 > 04 029dd244 02fa75ec msjet40!WZLocalTransporterID+0x24
 > 05 029de3a8 02fa8da4 odbcjt32!SQLConnectCover+0x395
 > 06 029de3dc 00fb1c0f odbcjt32!SQLDriverConnectW+0x3d
 > 07 029de420 00fb18cb ODBC32!SQLInternalDriverConnectW+0x142
 > 08 029deb64 02e82049 ODBC32!SQLDriverConnectW+0x6ba
 > 09 029debcc 02e821d0 msdasql!CODBCHandle::OHDriverConnect+0x80
 > 0a 029debec 02e82313 msdasql!CHdbcNode::DriverConnect+0x20
 > 0b 029dec30 02de4602 msdasql!CImpIDBInitialize::Initialize+0x161
 > 0c 029dec5c 02de46a3 oledb32!CDBInitialize::DoInitialize+0x32
 > 0d 029dec8c 02de2d75 oledb32!CDBInitialize::Initialize+0x58
 > 0e 029ded38 75610dfe oledb32!CDCMPool::CreateResource+0x1fa
 > 0f 029ded74 75612301
 > comsvcs!CHolder::SafeDispenserDriver::CreateResource+0x25
 > 10 029dedd0 02de3319 comsvcs!CHolder::AllocResource+0x325
 > 11 029dee20 02de4748 oledb32!CDCMPool::DrawResource+0x9d
 > 12 029dee78 02de320e oledb32!CDCMPoolManager::DrawResource+0x185
 > 13 029deed8 02ab6a9b oledb32!CDPO::Initialize+0x136
 > 14 029defd8 02ab6c37 msado15!_ConnectAsync+0x1da
 > 15 029defe8 02ab694e msado15!ConnectAsync+0x1f
 > 16 029df158 02ad0d8d msado15!CConnection::Open+0xa26
 > 17 029df3dc 7348b427 msado15!CConnection::Invoke+0xb63
 > 18 029df430 7347f39c vbscript!CatchIDispatchInvoke+0x46
 > 19 029df47c 7346368c vbscript!IDispatchInvoke+0x95
 > 1a 029df590 73462f95 vbscript!InvokeDispatch+0x138
 > 1b 029df5b4 734635ef vbscript!InvokeByName+0x40
 > 1c 029df890 73463c33 vbscript!CScriptRuntime::Run+0x2625
 > 1d 029df994 73463d42 vbscript!CScriptEntryPoint::Call+0x65
 > 1e 029df9f8 73464081 vbscript!CSession::Execute+0xb6
 > 1f 029dfa48 734640ee vbscript!COleScript::ExecutePendingScripts+0x14a
 > 20 029dfa64 709e5e87 vbscript!COleScript::SetScriptState+0x14e
 > 21 029dfa90 709e5ee1 asp!CActiveScriptEngine::TryCall+0x17
 > 22 029dfacc 709e5f21 asp!CActiveScriptEngine::Call+0x31
 > 23 029dfae0 709e6227 asp!CallScriptFunctionOfEngine+0x21
 > 24 029dfb18 709e6393 asp!ExecuteRequest+0x138
 > 25 029dfb60 709e5573 asp!Execute+0x16a
 > 26 029dfbb0 709e5726 asp!CHitObj::ViperAsyncCallback+0x3ec
 > 27 029dfbd0 75633107 asp!CViperAsyncRequest::OnCall+0x8c
 > 28 029dfbec 77204c67 comsvcs!CSTAActivityWork::STAActivityWorkHelper+0x30
 > 29 029dfc38 7720539a ole32!EnterForCallback+0xc0
 > 2a 029dfd98 771e03a4 ole32!SwitchForCallback+0x194
 > 2b 029dfdc4 771c7e10 ole32!PerformCallback+0x52
 > 2c 029dfe48 77207984 ole32!CObjectContext::InternalContextCallback+0x140
 > 2d 029dfe68 756332b3 ole32!CObjectContext::DoCallback+0x1a
 > 2e 029dfed4 756337ad comsvcs!CSTAActivityWork::DoWork+0x137
 > 2f 029dfee8 75633f71 comsvcs!CSTAThread::DoWork+0x14
 > 30 029dff04 7563423b comsvcs!CSTAThread::ProcessQueueWork+0x30
 > 31 029dff84 77bc91ed comsvcs!CSTAThread::WorkerLoop+0x17a
 >
 ><!-- ~MESSAGE_AFTER~ -->

 >> Stay informed about: IISstate log analysis 
Back to top
Login to vote
user944

External


Since: Oct 10, 2003
Posts: 22



(Msg. 3) Posted: Wed Aug 11, 2004 4:35 pm
Post subject: Re: IISstate log analysis [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
Hi Pat

Yes it is IIS6, thanks for that,

Regards

Stephen

"Pat [MSFT]" <patfilot.RemoveThis@online.microsoft.com> wrote in message
news:O2ydiPwfEHA.2544@TK2MSFTNGP10.phx.gbl...
 > Is this IIS6? This looks like the Jet bug. You'll need to contact
support
 > to obtain it (ask for fix from KB Q838306).
 >
 >
 > Pat
 >
 > "sdm" <stephen.moss.RemoveThis@bradford.gov.uk> wrote in message
 > news:_7ucncOjXpt-Z4XcSa8jmw@karoo.co.uk...
  > > Hi
  > >
  > > Could anyone point me in the direction of where to start with the
problem
  > > below. IIS stops serving ASP pages, just eventually times out, but html
  > > pages are fine, have to restart www service to fix.
  > >
  > > Thanks in Advance
  > >
  > > Stephen
  > >
  > > ____________________________________________________________________
  > >
  > > Thread ID: 19
  > > System Thread ID: 8c
  > > Kernel Time: 0:0:2.546
  > > User Time: 0:0:4.906
  > > Other information: Thread is waiting for a lock to be released. Looking
  > > for
  > > lock owner.
  > > Owning thread System ID: 1e4
  > > Thread Type: Jet DB Query. Possible ASP Page
  > > Executing Page: D:\INTRANET\INDEX.ASP
  > >
  > > # ChildEBP RetAddr
  > > 00 029dcd04 77f43741 SharedUserData!SystemCallStub+0x4
  > > 01 029dcd08 77f5d64e ntdll!ZwWaitForSingleObject+0xc
  > > 02 029dcd44 77f42044 ntdll!RtlpWaitForCriticalSection+0x126
  > > 03 029dcd4c 1b0058cc ntdll!RtlEnterCriticalSection+0x46
  > > 04 029dd244 02fa75ec msjet40!WZLocalTransporterID+0x24
  > > 05 029de3a8 02fa8da4 odbcjt32!SQLConnectCover+0x395
  > > 06 029de3dc 00fb1c0f odbcjt32!SQLDriverConnectW+0x3d
  > > 07 029de420 00fb18cb ODBC32!SQLInternalDriverConnectW+0x142
  > > 08 029deb64 02e82049 ODBC32!SQLDriverConnectW+0x6ba
  > > 09 029debcc 02e821d0 msdasql!CODBCHandle::OHDriverConnect+0x80
  > > 0a 029debec 02e82313 msdasql!CHdbcNode::DriverConnect+0x20
  > > 0b 029dec30 02de4602 msdasql!CImpIDBInitialize::Initialize+0x161
  > > 0c 029dec5c 02de46a3 oledb32!CDBInitialize::DoInitialize+0x32
  > > 0d 029dec8c 02de2d75 oledb32!CDBInitialize::Initialize+0x58
  > > 0e 029ded38 75610dfe oledb32!CDCMPool::CreateResource+0x1fa
  > > 0f 029ded74 75612301
  > > comsvcs!CHolder::SafeDispenserDriver::CreateResource+0x25
  > > 10 029dedd0 02de3319 comsvcs!CHolder::AllocResource+0x325
  > > 11 029dee20 02de4748 oledb32!CDCMPool::DrawResource+0x9d
  > > 12 029dee78 02de320e oledb32!CDCMPoolManager::DrawResource+0x185
  > > 13 029deed8 02ab6a9b oledb32!CDPO::Initialize+0x136
  > > 14 029defd8 02ab6c37 msado15!_ConnectAsync+0x1da
  > > 15 029defe8 02ab694e msado15!ConnectAsync+0x1f
  > > 16 029df158 02ad0d8d msado15!CConnection::Open+0xa26
  > > 17 029df3dc 7348b427 msado15!CConnection::Invoke+0xb63
  > > 18 029df430 7347f39c vbscript!CatchIDispatchInvoke+0x46
  > > 19 029df47c 7346368c vbscript!IDispatchInvoke+0x95
  > > 1a 029df590 73462f95 vbscript!InvokeDispatch+0x138
  > > 1b 029df5b4 734635ef vbscript!InvokeByName+0x40
  > > 1c 029df890 73463c33 vbscript!CScriptRuntime::Run+0x2625
  > > 1d 029df994 73463d42 vbscript!CScriptEntryPoint::Call+0x65
  > > 1e 029df9f8 73464081 vbscript!CSession::Execute+0xb6
  > > 1f 029dfa48 734640ee vbscript!COleScript::ExecutePendingScripts+0x14a
  > > 20 029dfa64 709e5e87 vbscript!COleScript::SetScriptState+0x14e
  > > 21 029dfa90 709e5ee1 asp!CActiveScriptEngine::TryCall+0x17
  > > 22 029dfacc 709e5f21 asp!CActiveScriptEngine::Call+0x31
  > > 23 029dfae0 709e6227 asp!CallScriptFunctionOfEngine+0x21
  > > 24 029dfb18 709e6393 asp!ExecuteRequest+0x138
  > > 25 029dfb60 709e5573 asp!Execute+0x16a
  > > 26 029dfbb0 709e5726 asp!CHitObj::ViperAsyncCallback+0x3ec
  > > 27 029dfbd0 75633107 asp!CViperAsyncRequest::OnCall+0x8c
  > > 28 029dfbec 77204c67
comsvcs!CSTAActivityWork::STAActivityWorkHelper+0x30
  > > 29 029dfc38 7720539a ole32!EnterForCallback+0xc0
  > > 2a 029dfd98 771e03a4 ole32!SwitchForCallback+0x194
  > > 2b 029dfdc4 771c7e10 ole32!PerformCallback+0x52
  > > 2c 029dfe48 77207984 ole32!CObjectContext::InternalContextCallback+0x140
  > > 2d 029dfe68 756332b3 ole32!CObjectContext::DoCallback+0x1a
  > > 2e 029dfed4 756337ad comsvcs!CSTAActivityWork::DoWork+0x137
  > > 2f 029dfee8 75633f71 comsvcs!CSTAThread::DoWork+0x14
  > > 30 029dff04 7563423b comsvcs!CSTAThread::ProcessQueueWork+0x30
  > > 31 029dff84 77bc91ed comsvcs!CSTAThread::WorkerLoop+0x17a
  > >
  > >
 >
 ><!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: IISstate log analysis 
Back to top
Login to vote
user944

External


Since: Oct 10, 2003
Posts: 22



(Msg. 4) Posted: Wed Aug 11, 2004 6:41 pm
Post subject: Re: IISstate log analysis [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
Hi Pat

Yes it is IIS6, I've obtained the patch from support and I'll see how it
goes. Thanks very much for your help.

Regards

Stephen

"Pat [MSFT]" <patfilot.DeleteThis@online.microsoft.com> wrote in message
news:O2ydiPwfEHA.2544@TK2MSFTNGP10.phx.gbl...
 > Is this IIS6? This looks like the Jet bug. You'll need to contact
support
 > to obtain it (ask for fix from KB Q838306).
 >
 >
 > Pat
 >
 > "sdm" <stephen.moss.DeleteThis@bradford.gov.uk> wrote in message
 > news:_7ucncOjXpt-Z4XcSa8jmw@karoo.co.uk...
  > > Hi
  > >
  > > Could anyone point me in the direction of where to start with the
problem
  > > below. IIS stops serving ASP pages, just eventually times out, but html
  > > pages are fine, have to restart www service to fix.
  > >
  > > Thanks in Advance
  > >
  > > Stephen
  > >
  > > ____________________________________________________________________
  > >
  > > Thread ID: 19
  > > System Thread ID: 8c
  > > Kernel Time: 0:0:2.546
  > > User Time: 0:0:4.906
  > > Other information: Thread is waiting for a lock to be released. Looking
  > > for
  > > lock owner.
  > > Owning thread System ID: 1e4
  > > Thread Type: Jet DB Query. Possible ASP Page
  > > Executing Page: D:\INTRANET\INDEX.ASP
  > >
  > > # ChildEBP RetAddr
  > > 00 029dcd04 77f43741 SharedUserData!SystemCallStub+0x4
  > > 01 029dcd08 77f5d64e ntdll!ZwWaitForSingleObject+0xc
  > > 02 029dcd44 77f42044 ntdll!RtlpWaitForCriticalSection+0x126
  > > 03 029dcd4c 1b0058cc ntdll!RtlEnterCriticalSection+0x46
  > > 04 029dd244 02fa75ec msjet40!WZLocalTransporterID+0x24
  > > 05 029de3a8 02fa8da4 odbcjt32!SQLConnectCover+0x395
  > > 06 029de3dc 00fb1c0f odbcjt32!SQLDriverConnectW+0x3d
  > > 07 029de420 00fb18cb ODBC32!SQLInternalDriverConnectW+0x142
  > > 08 029deb64 02e82049 ODBC32!SQLDriverConnectW+0x6ba
  > > 09 029debcc 02e821d0 msdasql!CODBCHandle::OHDriverConnect+0x80
  > > 0a 029debec 02e82313 msdasql!CHdbcNode::DriverConnect+0x20
  > > 0b 029dec30 02de4602 msdasql!CImpIDBInitialize::Initialize+0x161
  > > 0c 029dec5c 02de46a3 oledb32!CDBInitialize::DoInitialize+0x32
  > > 0d 029dec8c 02de2d75 oledb32!CDBInitialize::Initialize+0x58
  > > 0e 029ded38 75610dfe oledb32!CDCMPool::CreateResource+0x1fa
  > > 0f 029ded74 75612301
  > > comsvcs!CHolder::SafeDispenserDriver::CreateResource+0x25
  > > 10 029dedd0 02de3319 comsvcs!CHolder::AllocResource+0x325
  > > 11 029dee20 02de4748 oledb32!CDCMPool::DrawResource+0x9d
  > > 12 029dee78 02de320e oledb32!CDCMPoolManager::DrawResource+0x185
  > > 13 029deed8 02ab6a9b oledb32!CDPO::Initialize+0x136
  > > 14 029defd8 02ab6c37 msado15!_ConnectAsync+0x1da
  > > 15 029defe8 02ab694e msado15!ConnectAsync+0x1f
  > > 16 029df158 02ad0d8d msado15!CConnection::Open+0xa26
  > > 17 029df3dc 7348b427 msado15!CConnection::Invoke+0xb63
  > > 18 029df430 7347f39c vbscript!CatchIDispatchInvoke+0x46
  > > 19 029df47c 7346368c vbscript!IDispatchInvoke+0x95
  > > 1a 029df590 73462f95 vbscript!InvokeDispatch+0x138
  > > 1b 029df5b4 734635ef vbscript!InvokeByName+0x40
  > > 1c 029df890 73463c33 vbscript!CScriptRuntime::Run+0x2625
  > > 1d 029df994 73463d42 vbscript!CScriptEntryPoint::Call+0x65
  > > 1e 029df9f8 73464081 vbscript!CSession::Execute+0xb6
  > > 1f 029dfa48 734640ee vbscript!COleScript::ExecutePendingScripts+0x14a
  > > 20 029dfa64 709e5e87 vbscript!COleScript::SetScriptState+0x14e
  > > 21 029dfa90 709e5ee1 asp!CActiveScriptEngine::TryCall+0x17
  > > 22 029dfacc 709e5f21 asp!CActiveScriptEngine::Call+0x31
  > > 23 029dfae0 709e6227 asp!CallScriptFunctionOfEngine+0x21
  > > 24 029dfb18 709e6393 asp!ExecuteRequest+0x138
  > > 25 029dfb60 709e5573 asp!Execute+0x16a
  > > 26 029dfbb0 709e5726 asp!CHitObj::ViperAsyncCallback+0x3ec
  > > 27 029dfbd0 75633107 asp!CViperAsyncRequest::OnCall+0x8c
  > > 28 029dfbec 77204c67
comsvcs!CSTAActivityWork::STAActivityWorkHelper+0x30
  > > 29 029dfc38 7720539a ole32!EnterForCallback+0xc0
  > > 2a 029dfd98 771e03a4 ole32!SwitchForCallback+0x194
  > > 2b 029dfdc4 771c7e10 ole32!PerformCallback+0x52
  > > 2c 029dfe48 77207984 ole32!CObjectContext::InternalContextCallback+0x140
  > > 2d 029dfe68 756332b3 ole32!CObjectContext::DoCallback+0x1a
  > > 2e 029dfed4 756337ad comsvcs!CSTAActivityWork::DoWork+0x137
  > > 2f 029dfee8 75633f71 comsvcs!CSTAThread::DoWork+0x14
  > > 30 029dff04 7563423b comsvcs!CSTAThread::ProcessQueueWork+0x30
  > > 31 029dff84 77bc91ed comsvcs!CSTAThread::WorkerLoop+0x17a
  > >
  > >
 >
 ><!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: IISstate log analysis 
Back to top
Login to vote
Display posts from previous:   
   Web Hosting Problem Solving Community! (Home) -> IIS All times are: Pacific Time (US & Canada) (change)
Page 1 of 1

 
 You can post new topics in this forum
You can reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum



[ Contact us | Terms of Service/Privacy Policy ]