Prev: Search Service will not start
Next: Desperate - WSS2.0 upgrade to WSS 3.0 trashed DB no either won
From: Wei Lu [MSFT] on 17 Sep 2007 03:58
Hello Henry,

The CLSID GUID {61738644-F196-11D0-9953-00C04FD919C1} is for IIS WAMREG
admin Service. Please go to the dcom configuration to grant the local
Actication permission for the Nerwork Service account.

1. In Start Menu, click RUN, type "dcomcnfg" (without quote) and click OK.

2. In the prompt dialogbox, click Component Servies -> Computers -> My
Computer -> DCOM config, find IIS WAMREG admin Service and right click the
Properties. In the Security Tab, check Customize and then click Edit in the
Launch and Activation Permissions section. Add Network Service and grant
the Local Launch and Local Activation permission. Click OK.

3. Restart IIS.

After that, please let me know whether you still get this error in the
event log and how about the memory usage of the OWSTIMER.EXE.

Sincerely,

Wei Lu
Microsoft Online Community Support

==================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
From: Henry99 on 17 Sep 2007 10:26
Hi Wei Lu,

OWSTIMER is stable running around 80 MB of mem usage.
COM Error disappeared, thanks to your last hint.

The problem with the SSO error in SP Backup I solved on my own (the brute
way) as following:
I created an empty Database in SQL Server with the name 'SSO'

I know, that is not the gentle way, but at least the SharePoint backup runs
now.

Thanks a lot, not even one error message in any event log.

Best Regards, Henry

From: callahan on 17 Sep 2007 14:58
That's actually pretty clever. Thanks for that tip Henry. I have a client
who just mentioned that problem.

-callahan
"Henry99" <Henry99(a)newsgroups.nospam> wrote in message
news:3DE06C2F-095A-4ED7-B5FC-0E246648F4F4(a)microsoft.com...
> Hi Wei Lu,
>
> OWSTIMER is stable running around 80 MB of mem usage.
> COM Error disappeared, thanks to your last hint.
>
> The problem with the SSO error in SP Backup I solved on my own (the brute
> way) as following:
> I created an empty Database in SQL Server with the name 'SSO'
>
> I know, that is not the gentle way, but at least the SharePoint backup
> runs
> now.
>
> Thanks a lot, not even one error message in any event log.
>
> Best Regards, Henry
>


From: Wei Lu [MSFT] on 18 Sep 2007 01:49
Hello Henry,

My pleasure. If you have any question, please feel free to let me know.

Sincerely,

Wei Lu
Microsoft Online Community Support

==================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
First  |  Prev  | 
Pages: 1 2 3
Prev: Search Service will not start
Next: Desperate - WSS2.0 upgrade to WSS 3.0 trashed DB no either won