SnapManager Exchange or SQL Service failed to start

or why .NET-Applications need long to start: "A common cause that I have seen often recently is Certificate Revocation List (CRL) checking when generating Publisher Evidence for Code Access Security (CAS)."[1]

In my case the Exchange Sever didn't had anymore direct access to the internet. The CRL checking during the SM Serverice Startup failed. This took longer than 30 seconds and causes the service start to time out. Adding some lines to the SnapMgrService.exe.config prevent the service to do the online CRL check. No further timeouts, services starts.

<?xml version="1.0" encoding="utf-8"?>
<configuration>
    <runtime>
        <generatePublisherEvidence enabled="false"/>
    </runtime>
    ...

Same issue some month's later with a SnapManager SQL installation. Good to have a cheat sheet for the most wired thing online.

[1] Best Practice - <GeneratePublisherEvidence> in ASPNET.CONFIG

The owner () of job does not have server access.

New week new troubles: SnapManager SQL created some backup jobs within the SQL Server 2005 - the job itself could not be run/executed.

The owner (...) of job <Job Name> does not have server access.

This strange behaviour i got only with SQL Server 2005. With SQL Server 2008 i could not reproduce it.  The user who created the job and was the owner of the job had SQL sysadmin role assigned. I found some hints to this behaviour: a restart of the SQL Server Agent should work. In my case i didn't work that easy. 

If i change the owner of the job to the builtin user sa the job is able to run...

It would be nice to understand the issue....

SnapManager SQL RPC error on initial configuration wizard setup

 If you get the following error during the initial configuration wizard you should verify if all required SQL Server services are running even if the databases are running fine. Some of the services are set to manual start by default.

[SQL-DMO API Error]: The RPC server is unavailable