I tried to access the C.A. Site with different configuration's security
leves in IE 7 and I got the same error.
Any idea about how can I solve it? I need to create 2 more colletion sites
in the farm.
Is it any way to enable diagnostic logging modifing the registry?
Thanks in advance
Adrian Garcia
Intertron
Hope this helps!
"Adrian Garcia" <Adrian Gar...@discussions.microsoft.com> wrote in message
news:E6E19BD7-A287-424E...@microsoft.com...
Here is the answer and also some actions that I made.
> Have you ever been able to access Central Administration?
Yes, I had created a couple of applications and site collections without any
problems.
When did it stop working and is there something in particular that was
installed or changed?
I dont know exactly. Last time I used the Central Administration was las
week. We didnt made any update y this last week.
> On what port is it?
Port number: 4844
> Do you have the most recent Service Pack(s) installed?
Yes, SP1
> Is this WSS 3.0 or MOSS 2007?
MOSS 2007. The farm have 2 server: One for SQL Server 2005 and other for the
rest of the services.
> Next, open IIS Manager and make sure the Central Administration site is
> started.
yes, the web site and the application pool are started
> At the command prompt, type iisreset /noforce and try again.
I made it yesterday without result. Today I made a system restart and also
no result.
Also I made the following:
a) I runned the Sharepoint wizard again, delete the C.A. site from the
server, went to IIS Admin a delete the C.A. site manually (the wizard didnt
delete), and runned the wizard again in order to recreate the C.A. site but
in a differente port, now in 8488, without result
b) I 've installed the SPTraceWiew.exe to get some diagnostic data but I
could not catch any exception, warnning, error, related to the HTTP error.
This are the message trace that I could catch:
ISIDORO 18:34:42.45254 Medium Windows SharePoint Services General Exiting
MRU trim routine.
ISIDORO 18:34:42.45254 Medium Windows SharePoint Services General Final
table size: 13879913 in 131 entries
ISIDORO 18:34:42.45254 Medium Windows SharePoint Services General Initial
table size: 13879913 in 131 entries
ISIDORO 18:34:42.45254 Medium Windows SharePoint Services General Entering
MRU trim routine.
No other trace message was generated.
c) I created a SQL Trace with the SQL Profiler and thess are the activities
the the Sharepoint server are sending prior the error:
exec sp_oledb_ro_usrname
select collationname(0x0904100000)
declare @p20 tinyint
set @p20=NULL
exec proc_FetchDocForHttpGet
'647B0531-BA05-4E66-BFBA-048CEDDBDC68',N'',N'',0,'Dec 30 1899
12:00:00:000AM',0,0,NULL,NULL,NULL,0,0x010500000000000515000000C6BB507AF89FB474BE043E3283100000,NULL,1,5242880,2,1,0,NULL,@p20 output
select @p20
exec sp_reset_connection
declare @p20 tinyint
set @p20=NULL
exec proc_FetchDocForHttpGet
'647B0531-BA05-4E66-BFBA-048CEDDBDC68',N'',N'default.aspx',0,'Dec 30 1899
12:00:00:000AM',0,0,NULL,NULL,1,1,0x010500000000000515000000C6BB507AF89FB474BE043E3283100000,NULL,1,5242880,2,1,0,N'',@p20 output
select @p20
The application that sended this command was "Internet Information Server"
using the Sharepoint services 's NTDomain Account.
Any help wil be appreciated.
Thanks in advance
Adrian Garcia
INTERTRON
STSADM has two operations listlogginglevels and setlogginglevel which may help you get more info
--
BR
Per Jakobsen
Blog: http://www.theblackknightsings.com
STSADM is a wonderful tool full of litle jewels like you point me.
Yesterday I used the SPTraceView Tool to setup and view the diagnostic
traces of my MOSS 2007 instalation.
The is that no error is reported when I got the HTTP 500 error.
Perhaps it is a IIS problem rather that a MOSS 2007 problem? How could I
check this? The C.A web site and the App Pool are up and running.
Thanks and hope this helps!
"Adrian Garcia" <Adrian...@discussions.microsoft.com> wrote in message
news:393E62A1-8A5A-4CA5...@microsoft.com...
Try 1. Looking for events in he Application log and System log: I cant find
any error/warning/message related to the time a open the site from
Sharepoint, IIS or any other source.
Try 2. Dettach/Attach: Works fine, no error log in SQL Server, no error
while I was doing the dettach/attach process. Same result, error 500. I can
access de database from the farm server without any problem. The Sharepoint
service 's domain user is setup as a user of the database.
I 'm thinking that could be an IIS related problem than a Sharepoint problem.
If that doesn't help, then I am officially out of troubleshooting ideas :(
Time maybe for drastic measures? Use stsadm to backup the default sharepoint
site and any other sites you have, re-install MOSS, making sure you specify
a NEW/Unique configuration database name.
Mike
"Adrian Garcia" <Adrian...@discussions.microsoft.com> wrote in message
news:972CA34E-5635-451B...@microsoft.com...
The user in the database is configured as dbo role. It has full access and
control ober the database.
Some other things I had tried was stsadm -o forceupdate, but still got error
500.
Strange... I can access the C.A. site with the Oficce Sharepoint Designer. I
can add and modify any page or content, see the design pane and so on. So I m
thinking that it is an IIS problem instead of a Sharepoint error.
I will try to add a server to the farm and host the C.A. in this new server.
crossing fingers....
Adrian