Re: number of critical errors occurred on SBS 2003
- From: "Dave Nickason [SBS MVP]" <gwdibble@xxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 5 Sep 2008 12:42:04 -0400
Let me start by saying that I would not change the security settings for that database. I connected to mine, and it's set to Windows authentication mode - I don't think changing to mixed mode is the right way to fix this. It appears that this error started upon installation of WSS 3.0, which I unfortunately don't know much about. I would recommend that you start a new thread addressing that as a SharePoint 3 problem, and provide a complete description of any symptoms you're seeing in addition to the error code.
SharePoint 3 has been around for a while for SBS, and if it were installing with the database security defaulting to an incorrect setting, that would be well known by now. I would check all the installation docs (the SBS-specific ones) and the release notes, but I would assume the security is correct unless you find written documentation to the contrary.
The answer to how you would change the security is to use either SQL Management Studio (comes with Premium but probably needs to be installed), or Management Studio Express (free download from MS). Open the properties of the database and look on the Security tab. (There's a separate Security section under the database itself, that's not it. It's right in the properties of the actual database at the top of the left pane). But again, I don't think that's the real issue, and I wouldn't change it without looking into this further, or unless you're having actual symptoms as opposed to just getting a logged error.
"Associates" <Associates@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:F135AEE1-6B2A-40E6-8AD1-972378FC2923@xxxxxxxxxxxxxxxx
Thank you Larry and Dave for your replies.
I did look up the event IDs at the EventID.net website but to get the
answer, i think you need to pay or something.
Anyway, I tried to re-start the services from the Services. When i
right-clicked on the "DCOM Server Process Launcher" to re-start the service,
the buttons "Start", "Stop", "re-start" were disabled or greyed out. Hence,
could not re-start it. The same thing went for service "Application
Experience Lookup service".
By the way, i got a silly question here. How do i change the authentication
mode of the SQL Server in regards to event ID: 18452.
Thanks for your help in advance
"Dave Nickason [SBS MVP]" wrote:
I don't think you have any huge causes for concern here. Does the server
appear to be functioning normally other than the logged errors?
For the 10016, if you open the error message and click the "for more
information" link, you should get instructions on how to fix the dcom
permissions. If not, please post back.
For ID 4, you have an error from W32Time that references application
experience lookup? That seems odd. Anyway, if you look in Services, is
application experience lookup set to automatic and is it started? If not,
please try to manually start it. If it starts, you can ignore this until
your next reboot and see if it happens again. If it fails to start, it'll
log an event that should help with troubleshooting.
For ID 21, do you get this frequently or just occasionally? Please go to
Services and restart Windows Time, then look in the System Log to see what
gets logged when it restarts. If the time service usually succeeds when it
attempts to sync with the external source, you can ignore the occasional
failure as just a busy external time server or Internet connection. If it
fails often, you could configure it to a different source, and if it fails
always, it's probably not configured at all. Please post back if you need
more help with this, including that I can post a great script I stole from
Les Connor to do the config.
For 18452, is this a one-time thing with no other symptoms? If so, please
ignore. If not, any help in this KB? Please be careful making any changes,
and note the original settings in writing for undo purposes. That's
probably the database for SharePoint 3 (and maybe WSUS), so it's difficult
to see how the security would have been configured incorrectly in the
installer. I might be inclined to ignore this or research it further, in
the absence of other symptoms.
Login failed for user 'username'. The user is not associated with a trusted
SQL Server connection. (Microsoft SQL Server, Error: 18452)
http://support.microsoft.com/default.aspx?scid=kb;en-us;555332
"Associates" <Associates@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:A3738AB0-9F66-4C4F-907E-70F9819A086F@xxxxxxxxxxxxxxxx
> Hi,
>
> I was wondering if i could get some help with the following critical
> errors
> on SBS 2003
>
> ID: 10016
> Description:
> The application-specific permission settings do not grant Local > Activation
> permission for the Com Server application with CLSID {61738...} to the
> user
> NT Authority\Network Service SID. This security can be modified using > the
> component services administrative tool.
>
> I am afraid i am not sure which application it's referring to.
>
> W32Time with ID: 4
> Description: Application experience lookup service failed to start
>
> W32Time with ID: 21
> The time service is configured to use one or more input providers > however
> none of the input providers are available. The time service has no > source
> of
> accurate time.
>
> Windows SharePoint Services 3 Search with ID: 10036
> Description: A database error occurred. Source: Microsoft OLE DB > Provider
> for SQL Server code: 18452 occur 1 time...
>
> MSSQL$Microsoft##See with event ID: 18452
> Description: Small Business Server cannot display a description for > this
> event...
>
> I don't understand what is happening here. All i did was having > installed
> .NET Framework 3 SP1. as well as installing Windows SharePoint 3.0 to > the
> Server SBS 2003 standard edition. I have followed the procedure to > ensure
> that it's installed side by side with WSS 2.0.
>
> Hope someone might be kind to help me out here. These errors really
> concern
> me.
>
> Thank you in advance
>
.
- References:
- number of critical errors occurred on SBS 2003
- From: Associates
- Re: number of critical errors occurred on SBS 2003
- From: Dave Nickason [SBS MVP]
- Re: number of critical errors occurred on SBS 2003
- From: Associates
- number of critical errors occurred on SBS 2003
- Prev by Date: No option to choose domain (no "log on to" field) when RDP via VPN
- Next by Date: Re: Suggestions for a networked inkjet
- Previous by thread: Re: number of critical errors occurred on SBS 2003
- Next by thread: Re: SBS Backup fails
- Index(es):