By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
445,678 Members | 1,146 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 445,678 IT Pros & Developers. It's quick & easy.

asynchronous logging with enterprise library logging application block.

P: n/a
I am trying to use asynchronous logging using MSMQ and I have configured the
properties as defined in the help (see below) I don't understand where the
property 'MsmqPath' is in the app.config for MSMQDistrbutor.exe is it meant
to be an aplication settings or an enterprise library setting in the
app.config?

I have tried creating an application setting value for it but it still fails
to write to the logging destination?

Also is this meant to be registered as a service?
To choose asynchronous logging.

1.. In the Enterprise Library Configuration Console, expand Client
Settings, right-click Distribution Strategies, point to New and then click
MSMQ.
2.. Select the strategy and then specify the QueuePath for the strategy.
3.. Select Client Settings, and then modify the DistributionStrategy
property to select the MSMQ distribution strategy you created.
4.. Open the MSMQDistributor.exe.config file with the Configuration
Console, located in the directory containing the file MSMQDistributor.exe.
Modify the MsmqPath property of the MSMQ Distributor Service to match the
QueuePath property of the MSMQ distribution strategy you selected in step 2.
This distribution strategy will be used for all messages that are not
filtered out.

Note Do not use the In Process distributor strategy and the MSMQ
distributor strategy to log to the same flat file sink. Using both the In
Process and MSMQ distributor strategies with the same flat file sink may
result in simultaneous attempts to write to the same file. This will result
in failure due to the file resource being in use by another process.

Has anyone got any ideas?

I followed the instructions below to allow for an MSMQ not registered with
AD.

http://mvwood.com/blogs/blog/archive...03/04/321.aspx

Cheers

Ollie Riches
Nov 17 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
found the problem, the 'install services' had not installed the
MSMQDistributor service correctly.
"Ollie Riches" <ol**********@phoneanalyser.net> wrote in message
news:%2***************@TK2MSFTNGP09.phx.gbl...
I am trying to use asynchronous logging using MSMQ and I have configured
the properties as defined in the help (see below) I don't understand where
the property 'MsmqPath' is in the app.config for MSMQDistrbutor.exe is it
meant to be an aplication settings or an enterprise library setting in the
app.config?

I have tried creating an application setting value for it but it still
fails to write to the logging destination?

Also is this meant to be registered as a service?
To choose asynchronous logging.

1.. In the Enterprise Library Configuration Console, expand Client
Settings, right-click Distribution Strategies, point to New and then click
MSMQ.
2.. Select the strategy and then specify the QueuePath for the strategy.
3.. Select Client Settings, and then modify the DistributionStrategy
property to select the MSMQ distribution strategy you created.
4.. Open the MSMQDistributor.exe.config file with the Configuration
Console, located in the directory containing the file MSMQDistributor.exe.
Modify the MsmqPath property of the MSMQ Distributor Service to match the
QueuePath property of the MSMQ distribution strategy you selected in step
2.
This distribution strategy will be used for all messages that are not
filtered out.

Note Do not use the In Process distributor strategy and the MSMQ
distributor strategy to log to the same flat file sink. Using both the In
Process and MSMQ distributor strategies with the same flat file sink may
result in simultaneous attempts to write to the same file. This will
result in failure due to the file resource being in use by another
process.

Has anyone got any ideas?

I followed the instructions below to allow for an MSMQ not registered with
AD.

http://mvwood.com/blogs/blog/archive...03/04/321.aspx

Cheers

Ollie Riches

Nov 17 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.