|
Home > Archive > BizTalk Server > May 2007 > Log on Event Viewer Shutdown Component Services
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Log on Event Viewer Shutdown Component Services
|
|
|
| Hi.
I would like to know if exists a way to log in the Event Viewer when any
Biztalk Server component services shutdown or startup.
Thx for your help.
mbrenes26@hotmail.com
MCSE:Security
| |
| Saravana Kumar 2007-04-23, 7:18 pm |
| What do you mean by BizTalk Server Component services. If you are referring
to the BTSNTSVC windows NT service, then it logs the successful start and
shut down as "information" in the event viewer automatically. You don't need
to do anything.
If you are referring to any other component like custom pipeline,
orchestration etc then you can write .NET code to write information into
eventviewer based on your logic.
Regards,
Saravana Kumar
http://www.biztalk247.com/v1/
http://www.digitaldeposit.net/blog
"Mario" <Mario@discussions.microsoft.com> wrote in message
news:056A4FF9-140E-4D0B-A74C-96899272F91A@microsoft.com...
> Hi.
> I would like to know if exists a way to log in the Event Viewer when any
> Biztalk Server component services shutdown or startup.
> Thx for your help.
>
> mbrenes26@hotmail.com
> MCSE:Security
| |
|
| Thx for your help.
I mean, after Biztalk install, in Administrative Tools/Component Services, I
have some Biztalk Server components. Those components can be shutdown or
start up. I can do that manually, but never appears a Log in Event Log about
it. The question is: How can I configure those Biztalk Server components to
write an Event every time somebody shutdown or start up that component?
"Saravana Kumar" wrote:
> What do you mean by BizTalk Server Component services. If you are referring
> to the BTSNTSVC windows NT service, then it logs the successful start and
> shut down as "information" in the event viewer automatically. You don't need
> to do anything.
>
> If you are referring to any other component like custom pipeline,
> orchestration etc then you can write .NET code to write information into
> eventviewer based on your logic.
>
> Regards,
> Saravana Kumar
> http://www.biztalk247.com/v1/
> http://www.digitaldeposit.net/blog
>
>
>
> "Mario" <Mario@discussions.microsoft.com> wrote in message
> news:056A4FF9-140E-4D0B-A74C-96899272F91A@microsoft.com...
>
>
| |
| Saravana Kumar 2007-04-27, 7:16 pm |
| I'm not sure what components you are referring to, but whatever it's if you
own the source code and rights to rebuild and redeploy the component then
its easy to write some event in the event viewer inside your component
(whether its .net component or COM component) in the startup and shutdown
procedures.
Regards,
Saravana Kumar
http://www.biztalk247.com/v1/
http://www.digitaldeposit.net/blog
"Mario" <Mario@discussions.microsoft.com> wrote in message
news:94763081-1962-4A2C-A269-D47141E038AD@microsoft.com...[vbcol=seagreen]
> Thx for your help.
> I mean, after Biztalk install, in Administrative Tools/Component Services,
> I
> have some Biztalk Server components. Those components can be shutdown or
> start up. I can do that manually, but never appears a Log in Event Log
> about
> it. The question is: How can I configure those Biztalk Server components
> to
> write an Event every time somebody shutdown or start up that component?
>
> "Saravana Kumar" wrote:
>
| |
| Jan Eliasen 2007-05-04, 1:16 pm |
| On Fri, 27 Apr 2007 08:48:04 -0700, Mario
<Mario@discussions.microsoft.com> wrote:
>Thx for your help.
>I mean, after Biztalk install, in Administrative Tools/Component Services, I
>have some Biztalk Server components. Those components can be shutdown or
>start up. I can do that manually, but never appears a Log in Event Log about
>it. The question is: How can I configure those Biztalk Server components to
>write an Event every time somebody shutdown or start up that component?
Are we talking about BizTalk 2000/2002?
--
eliasen, representing himself and not the company he works for.
Private blog: http://blog.eliasen.dk
Private email: jan@eliasen.dk
|
|
|
|
|