Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Unable to establish a connection with Active Directory

465 views
Skip to first unread message

Gerardo Porras

unread,
Feb 19, 2001, 11:03:33 AM2/19/01
to

Hi, folks.

I gotta problem that I hope you can help me to solve.

I'm trying to open a queue on a W2k Server access mode MQ_RECEIVE_ACCESS but I
get the error "-1072824301 - Unable to establish a connection with Active
Directory. Verify there are sufficient permissions to perform this operation".

I've already gave permisions to the domain administrator which is the account I'm
using to connect. To perform this operation an independent client is installed on
the machine where I try to open the queue.

Any help would be appreciated.

Thanks in advanced.

Doron Juster

unread,
Feb 20, 2001, 1:06:49 AM2/20/01
to
Your computer is probably "offline" as far as msmq is concerned. You
probably don't have connectivity with the active directory (or MQIS servers,
if you deploy them).
After boot, you should see an event in application events log saying that
msmq is online. If your computer cannot access a msmq server running on
win2k domain controller, then you're offline.

Doron

"Gerardo Porras" <porr...@bccr.fi.cr> wrote in message
news:3e4301c09a8d$82959040$b1e62ecf@tkmsftngxa04...

Gerardo Porras

unread,
Feb 20, 2001, 11:51:25 AM2/20/01
to

But how is that possible even when I'm able to send messages and make a query and
it returned the right result?

What does it mean to be "offline" to msmq? I've checked out the service and is up
and running.

Event Log at DC says everything is ok. Besides I'm able to open the queue for
read access when the client is an Advanced Server but if fails awkwardly when is
a W2k Professional connecting as DC Administrator account. We tested the same
program with Advanced Server and Professional running in another network and it
worked just fine ?!?!?!.

I don't know if that problem maybe produced by some kind of delay between clients
and DC.


BTW Thanks for your help.

Doron

Hi, folks.

Thanks in advanced.


.

Frank Boyne

unread,
Feb 20, 2001, 2:16:29 PM2/20/01
to
"Gerardo Porras" <porr...@bccr.fi.cr> wrote in message
news:37dd01c09b5d$5ca73660$a5e62ecf@tkmsftngxa07...

> But how is that possible even when I'm able to send messages and make a
query and
> it returned the right result?

Two Queue managers can interact with each other successfully even when one
(or both) of them cannot communicate with the MQIS (the MSMQ Information
Service). For MSM! 1.0, the error you are getting 0xC00E0013 is
MQ_ERROR_NO_DS which means "No connection with this site's controller(s)."
I suspect the Active Directory references are the Windows 2000 translation
of this error message.

> What does it mean to be "offline" to msmq? I've checked out the service
and is up
> and running.

Offline means different things in different contexts. Mostly it means
disconnected from the network (see for example the MSMQ help sections on
"Working Offline"). However, when you are disconnected from the network you
can not reansfer messages in or out of the system, and you cannot
communicate with your site controller. If the Site controller is
dosconnected from the network, you can transgfer messages but you still
can't communicate with the controller. I'm not sure if the MSMQ Queue
Manager considers an unavailable controller as being offline or online. I
suspect online since you report not seeing the "offline" event log entry.

> Event Log at DC says everything is ok. Besides I'm able to open the queue
for
> read access when the client is an Advanced Server but if fails awkwardly
when is
> a W2k Professional connecting as DC Administrator account.

Are you using pathname or format name to specify the queue? I'll guess
pathname. To translate pathname into format name, the local QM has to
contact the MQIS (in windows 2000, the MQIS is Active Directory). Then,
using the format name the QM can actually open the queue. If the MQIS
interaction fails, you can't open the queue but you can still send and
receive messages to/from other queues you already have open, or can open
without the MQIS.

Mostly 0xC00E0013 is a security problem, at least that was the case in MQIS
1.0. I don't know enough about AD security to comment intelligently.


0 new messages