Re: Outlook for MAPI on SBS
- From: "kj" <kj@xxxxxxxxxxx>
- Date: Thu, 13 Jul 2006 08:11:15 -0700
Thanks for posting this follow up information Jamie.
Undoubtedly a future Google will be fruitful for other with this or similar
issues.
--
/kj
"thejamie" <thejamie@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:4830E8D3-2449-4AF4-8087-7FA9143F35D8@xxxxxxxxxxxxxxxx
I doubt I will find time to get to the beta site to file a bug - here is
what
I've noticed and presumably it is fixed in the R2 release Steve spoke of.
kj points out that we can also use the LAUNCHWIZARDENTRY API to run this
action and generally if there is a programmable option to access as with
PROGMAN and PROGMAN2, I'm happy. On the other hand, in asking this
question
I wound up looking at another thread here on installing SQL 2005 which I
tried to follow-up on in the middle of all this.
SQL Server 2005 installation changes the name of services that are
required
(Pre R2 - I will test R2 shortly - I'm still download) For example,
SQLServerDTSUser$ServerName after installation of 2005 SQLExpress
(Instance
not default) indicates this has changed to
SQLServer2005DTSUser$Servername.)
I had to manually add the user group. There is also a bug in the
documentation - double clicking the Log on as Service does not allow edit
of
this property. You must right click and select properties.
Additionally, the Volume Shadow Service is also unable to run which causes
an error during backup. ESENT fails and a dll
(http://support.microsoft.com/kb/830575/en-us) needs to be re-registered.
I
am not sure how many of them were actually changed in the process. I am
going to cross my fingers and hope it auto-resolves when I upgrade to R2.
If
not, I may never know because it is highly likely I will just re-install
the
OS out of frustration.
--
Regards,
Jamie
"kj" wrote:
Afraid you're hitting below the belt on me Jamie. SQL isn't my strong
suit
particularly 2005 on SBS.
Perhaps start a new post with the new topic and someone more profecient
in
SQL can help?
--
/kj
"thejamie" <thejamie@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:AE9A5470-84AE-45BE-9616-8615EDBEE4F8@xxxxxxxxxxxxxxxx
KJ,
Thanks for that... I have noticed something interesting here in SBS
which
doesn't exactly tie into the question I have asked you. Loading SQL
Server
2005 as an instance on SBS (I noticed because someone else is talking
about
doing this in another thread) causes the Local Security Policy to
change
the
agent from the SBS Monitoring Agent to the 2005 agent instance. I
suspect
that this is one of the incompatibility issues associated with placing
SQL
2005 on SBS. Is this something you are familiar with? My local
security
policy is mapped as not enabled, thus changing the agent back in the
local
security policy is NOT an option. If this is so, in my case, there is
nothing critical running here and I can simply reinstall SBS after
uninstalling 2005. It looks to me like this is a serious issue.
--
Regards,
Jamie
"kj" wrote:
Use the LAUNCHWIZARDENTRY function !
;-)
--
/kj
"thejamie" <thejamie@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:165B1317-7F4D-4E02-AF6E-BCC0DBDC650B@xxxxxxxxxxxxxxxx
Looks like that'll work. SBS already has reporting. Is this the
only
way
to
tap into that subsystem for MAPI? I know it sounds lazy, but "WHERE
IS
THE
WIZARD?"
Thanks, I saw this in my searches. I was hoping to avoid it but see
now
that it is unavoidable.
--
Regards,
Jamie
"kj" wrote:
Have a look at the article found here;
http://support.microsoft.com/kb/306962/
--
/kj
"thejamie" <thejamie@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:B0F452CE-7A82-4892-932E-DB7AE0D2214E@xxxxxxxxxxxxxxxx
Wow! Glad I asked first. Any idea how to enable the agent
on
SQL
over SBS Prem or is that a question for the SQL forum?
--
Regards,
Jamie
"Cris Hanna (SBS-MVP)" wrote:
NO...do not install Outlook on Your SBS you will hose Exchange
--
Cris Hanna [SBS-MVP]
--------------------------------------
Please do not respond directly to me, but only post in the
newsgroup
so
all can take advantage
"thejamie" <thejamie@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:48425397-2151-4DDB-A7F4-FDBA67EB5E33@xxxxxxxxxxxxxxxx
Is there an easy way to set up notifications from SQL Server
Agent
on
SBS?
It appears to be that setting up Outlook on the server is one
way
to
get MAPI
to be available. Is this wise? I don't know that it will
work
either.
Will
installing Outlook place MAPI on the server so that I can
configure
SBS
Premium to send mail on a SQL Server Agent job? Is there an
easier
way
to do
this?
--
Regards,
Jamie
.
- References:
- Re: Outlook for MAPI on SBS
- From: Cris Hanna \(SBS-MVP\)
- Re: Outlook for MAPI on SBS
- From: kj
- Re: Outlook for MAPI on SBS
- From: kj
- Re: Outlook for MAPI on SBS
- From: thejamie
- Re: Outlook for MAPI on SBS
- From: kj
- Re: Outlook for MAPI on SBS
- From: thejamie
- Re: Outlook for MAPI on SBS
- Prev by Date: Re: Chief Exec wants to monitorand view email
- Next by Date: Re: Reverse Lookup Zone record problem
- Previous by thread: Re: Outlook for MAPI on SBS
- Next by thread: Re: Outlook for MAPI on SBS
- Index(es):
Relevant Pages
|
