Hello Everybody,

we've setted up an extranet on our external webserver located at the
providers datacenter. This server is not an member of any domain only in a
workgroup.

We've installed Sharepoint Services incl. SP2 (english) - local installation
without SQL Server, only WMSDE and the german languagepack.

My problem is that Alerts are not sended out, only the email "An alert has
successfully been added on ...".

I've already googled and found that the "Timer Service" must be running. I
can't get this service work. Each time I start it, an message come up that
the services couldn't be started. Out of the event-log I can see that the
error seems to be that the time service depends on netlogon service. I can't
start netlogon because the server ins't a domain member.

Furthermore I found that the Timer Service was running under NetworkService
first, I should change it to localSystem but the service also does not start.

Can anybody help me?

Could it be, that alerts only work with SQL Server not with the WMSDE, like
the search?

RE: Alerts form non domain SP-Server not working (Timer Service/Netlog by RobinMeur

RobinMeur
Tue Apr 11 06:33:01 CDT 2006

Thomas,

alerts also work fine on MSDE so there is not wrong with that.

What you could do is instead of using the local service of network service,
is creating a (service) user account that is local admin of on the machine.
This account must also be known in MSDE as a database admin.

You can probably re-use the application pool's account for this job (if you
are using a (service) user account). So reconfigure the owstimer service with
this service account. (please read the following article :
http://blogs.msdn.com/modonovan/archive/2005/06/14/428862.aspx)

Also check if there is no antivirus tool blocking the emails (McAfee
considers it as spam for example)

"Thomas" wrote:

> Hello Everybody,
>
> we've setted up an extranet on our external webserver located at the
> providers datacenter. This server is not an member of any domain only in a
> workgroup.
>
> We've installed Sharepoint Services incl. SP2 (english) - local installation
> without SQL Server, only WMSDE and the german languagepack.
>
> My problem is that Alerts are not sended out, only the email "An alert has
> successfully been added on ...".
>
> I've already googled and found that the "Timer Service" must be running. I
> can't get this service work. Each time I start it, an message come up that
> the services couldn't be started. Out of the event-log I can see that the
> error seems to be that the time service depends on netlogon service. I can't
> start netlogon because the server ins't a domain member.
>
> Furthermore I found that the Timer Service was running under NetworkService
> first, I should change it to localSystem but the service also does not start.
>
> Can anybody help me?
>
> Could it be, that alerts only work with SQL Server not with the WMSDE, like
> the search?
>
>
>

RE: Alerts form non domain SP-Server not working (Timer Service/Ne by Thomas

Thomas
Thu Apr 13 09:52:03 CDT 2006

Thanks Robin for the info that alerts also work fine on MSDE. I thougt i need
an sql server, but now I'm glad I didn't :-)

Today I've deinstalled the whole Sharepoint Services incl. the MSDE and
anstalled it again. During the installation i created a new applicationpool
insted of using the one from the standard website, furthermore I've choosed a
user account (has admin rights on the machine) for the pool.

Unfortunately it's the same as yesterday :-(

Always I want to start the timer service I got the message "the service
sharepoint timer service on the local machine could not be started. error
1068: the dependencyservice or the dependencygroup couln't be started"

As mentioned above the event log shows 2 events:

EventID 3095

"This computer is configured as member of an workgroup, not as a member of a
domain. the netlogon service must not be started at this configuration.

EventID 7001

"The service sharepoint timer service depends on service netlogon, which
couldn't be started because of the following error: the process was
successfully stopped.

The same happens if the service is started with the user which was created
for the application pool, the administrator, the local system account or
nt-authority\networkservice.

I'm going crazy **aaarggg*

RE: Alerts form non domain SP-Server not working (Timer Service/Ne by Thomas

Thomas
Thu Apr 13 10:06:02 CDT 2006

I forgot something...

You wrote: "This account must also be known in MSDE as a database admin."

How can I see the Database Tables and edit users, I don't have an enterprise
manager console as on our sql server.

Is there any freeware tool giving me this options?

RE: Alerts form non domain SP-Server not working (Timer Service/Ne by Thomas

Thomas
Thu Apr 13 10:08:02 CDT 2006

I forgot something...

You wrote: "This account must also be known in MSDE as a database admin."

How can I see the database tables and edit users, I don't have an enterprise
manager console as on our sql server.

Is there any freeware tool giving me this options?

RE: Alerts form non domain SP-Server not working (Timer Service/Ne by Sebastian

Sebastian
Sun Apr 23 09:42:01 CDT 2006

Hi Thomas,

I have exact the same problem that sptimer is not statring because it
depends on net logon... Could you solve the problem in the meantime??

To manage SQL Servers/MSDEs you can use the free SQL Management Studio
Express: http://go.microsoft.com/fwlink/?LinkId=65110

But setting permissions didn't help in my case :-(

Kind regards,
Sebastian



"Thomas" wrote:

> I forgot something...
>
> You wrote: "This account must also be known in MSDE as a database admin."
>
> How can I see the database tables and edit users, I don't have an enterprise
> manager console as on our sql server.
>
> Is there any freeware tool giving me this options?

RE: Alerts form non domain SP-Server not working (Timer Service/Ne by Thomas

Thomas
Thu Apr 27 07:57:02 CDT 2006

Hi Sebastian!

I got it working. Set the "Sharepoint Timer Service" to "local system"
instead of "NT AUTHORITY\NetworkService"and restart the whole Server. That
solved the Problem in my case.