Re: Event 1000 Windows SharePoint Services 2.0 Error
- From: thejamie <thejamie@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sat, 13 Sep 2008 16:03:01 -0700
I wonder how hard it would be for Microsoft to post the fix. I see that
there are issues with both security as well as with the setup. MSDE, sp3a
added a patch to place a strong sa password into the SQL Authentication
(SECURITYMODE=SQL). For my part, upon installing SBS 2003, my assumption was
the the SP1 version of SQL had gone into the four or five instances of MSDE
that run on SBS and performed this update. One of the things that happens in
the update is that the SP4 version of MSDE is written to the disk and some
updates run.
I have made several attempts to perform the SAPWD=<strongSApwd> required on
the UDDI, the SBSMONITORING, the MSFW, the SHAREPOINT, the MICROSOFT##SSEE
using techniques I found worked on the MSDE databases in the past (that is
for an upgradesp switch on the setup of SQL using the sp4 setup program).
If would appear the security is complicated and I suspect this is why I am
unsucessful at patching the entire gamut of instances. I have attempted to
get Microsoft to post the fix with no result.
To my knowledge, the sp4 setup file needs to contain several items in the
setup.ini (you need to alter it for each instance and run the setup from the
commandline in the folder where the sp4 msde update resides)
Example setup.ini
[OPTIONS]
DISABLENETWORKPROTOCOLS=1
SAPWD=<strongSAPwdofchoice>
UID=sa
SECURITYMODE=SQL
DISABLEAGENTSTARTUP=1
DISABLETHROTTLE=1
INSTANCENAME=SBSMONITORING
REINSTALL=ALL
REINSTALLMODE=VEMUS
[see the link: http://msdn.microsoft.com/en-us/library/aa214935.aspx]
To launch the command, you would run a command similar to this:
setup /upgradesp sqlrun instancename=MSFW /l*v c:\msde2Ksp4.log
however, since you include the SBSMONITORING instancename in the setup.ini,
you can eliminate the instancename portion of the commandline and it would
boil down to:
setup /upgradesp sqlrun
and the VEMUS would simply populate verbosely the sql log in its default
location (somewhere in the SQL Server "INSTANCENAME" folder.
I cannot determine from the command line given in the support article for
948110 whether the password for the WSUS instance (which I have not
installed) and the Sharepoint instance use blank passwords:
http://support.microsoft.com/kb/948110
It would appear that they do, but I find this part difficult to fathom and
would welcome an explanation on this from Microsoft before I disable the
password on my Sharepoint instance. (which is not running at the moment).
SQLWMSDE-KB948110-x86-ENU /quiet /upgradesp sqlrun DISABLENETWORKPROTOCOLS=1
DISABLEAGENTSTARTUP=1 DISABLETHROTTLE=1 BLANKSAPWD=1 INSTANCENAME=Sharepoint
REINSTALL=ALL REINSTALLMODE=VEMUS /l*v %windir%WMSDE.log
At the moment, the most difficult part of this issue seems to be that the
MSDE installation hangs just as it is about to finish and I cannot find the
WMSDE.log in the Windows directory to determine where it fails.
On the other hand, I am able to get an error... "network error occured while
attempting to read from the file sqlrun.dat.
Hopefully, some of the information I have provided above will help others to
find the solution. I am tired of telling my server to NOT INSTALL 948110.
I would rather not have Microsoft mucking around in my system. Some of
their support is great while in some areas it has been lacking and I am of
the opinion that finding the correct solution is better than spending hours
on the phone and being tied down from doing other things more relevant.
If you can add to the above - specifically about the networking permissions
and whether the SAPWD should actually be blank (null) for SHAREPOINT to work.
Perhaps this is the case, and if so, then this would be nice to know also.
It seems they are asking that we call in because somehow it is construed that
we cannot fix this one ourselves and perhaps they are right, but I stubbornly
hold to believe in myself and that it is something that will be fixed
eventually.
--
Regards,
Jamie
"Aplima" wrote:
I have my server a total mess for a week....
Due to this update...
I realized what caused it 3 days after...
I tried to fix it on my own and now I think I got a bigger problem...
First I read about WUS could cause the problem... So I uninstalled it.
After that, I had all SQL server instances to a complete stop.
They don't start and I get an error: "The system could not find the
specified file"
WHAT FILE?????
And it gets worst!
Exchange pop3 connector fails with the same error.
I need help... I don't want to try any other solution unless someone
garantees it will work for sure.
I will call MS again, because in my country on the day after the update the
answer was: "It's hardly an update issue, but you can fill a form for a paid
support". I paid a lot for this software. The last thing I wanted to hear was
something like that.
I'll call them again tomorrow. I'm willing to pay, anyone that solves me
this issue... :(
"Pete at Glassblade" wrote:
It IS widespread - SBS is used by small companies who often don't have
dedicated IT staff - they are obliged to trust Microsoft's expertise. So when
an update is pushed out that kills something as inherently flakey as SQL it
is MS who should stand up and be counted. The 'I'm not bothered, it is only
the small guys who are suffering' approach will prove very expensive for our
MS oriented community if we aren't careful.
I don't see symantec as an admirable model to copy in that respect.
Pete
"Susan Bradley" wrote:
You have a backup of the entire server, yes?
You control patching, yes? I'm not trying to be mean here but patching
SQL should be planned.
And these patches don't barf on everyone, so this isn't widespread.
Ed Podowski wrote:
I think I found my answer and it doesn't look good. Our drives are mirrored,
but Volume Shadow Copy for C Drive is disabled. Volume Shadow Copy for D
Drive is enabled. [Naturally, the information is on C Drive.] If anyone has
any suggestions, i would greatly appreciate it.
Thank you,
Ed Podowski
P.S. I'll take responsibility for not having a backup and / or volume shadow
copy enabled, but Microsoft should take responsibility for publishing a patch
that is causing millions of dollars in loss productivity.
Microsoft should be responsible for doing a back up before applying any
update. What is the first rule before you update - Backup?
If you are from Microsoft, please do not respond to my P.S. I just need
this fixed.
"Ed Podowski" wrote:
Thanks for posting this.
I am experiencing the same problem and do not have a backup. How do use
shadow copy to restore the file?
Thank you!
"wrytat" wrote:
Hi
I'm using Small Business Server 2003. At 3 am this morning, my
MSSQL$Sharepoint service stopped running and the server restarts by itself,
most probably due to an update. And this morning when I came to work, I
discovered that when I try to access http://companyweb/, I receive the
"Cannot connect to the configuration database." error message. I followed
KB823287 and KB833183, but still couldn't access the website. I managed to
ping, nslookup, and even login to the SQL server successfully.
I checked my Events Log, and discovered that the Event 1000 Windows
SharePoint Services 2.0 Error appeared almost every 5 seconds. The error
description reads, "#50070: Unable to connect to the database STS_Config on
servername\MICROSOFT##SSEE. Check the database connection information and
make sure that the database server is running."
Besides, it sometimes accompanied with a 18456 Failure Audit, which reads,
"The description for Event ID ( 18456 ) in Source ( MSSQL$MICROSOFT##SSEE )
cannot be found. The local computer may not have the necessary registry
information or message DLL files to display messages from a remote computer.
You may be able to use the /AUXSOURCE= flag to retrieve this description; see
Help and Support for details. The following information is part of the event:
NT AUTHORITY\NETWORK SERVICE, [CLIENT: <named pipe>]."
What can I do? Please advise, thank you.
- Prev by Date: Re: Remote Client Connection Problem - KB897651
- Next by Date: Re: Remote Client Connection Problem - KB897651
- Previous by thread: Issues with FTP on SBS
- Next by thread: Re: Outlook signature..
- Index(es):
Relevant Pages
|
Loading
