需要有关具有 MQ 交互的 WCF Web 服务的帮助
我创建了一个简单的 WCF Web 服务来将一些消息写入 MQ (Websphere MQ)。它托管在 IIS 6.0 服务器中。服务声明成功，但是在将消息写入 MQ 时，它抛出异常，原因代码为 2063。
有没有办法覆盖 Web 服务的连续用户（代码中）？
先感谢您..
I have created a simple WCF web service to write some messages into MQ (Websphere MQ).It was hosted in IIS 6.0 server. Service stated successfully, but while writing the message into MQ it was throwing a exception with reason code 2063.
Is there any way to override the run-on user(in code) for web service ?
Thank you in advance..
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
原因代码
2063 0x0000080f MQRC_SECURITY_ERROR引用了 WMQ 外部的内容。例如，如果应用程序无法访问配置文件、密钥库密码不正确或者 QMgr 或应用程序无法访问域资源。当使用 Windows 服务器的管理员帐户之一访问 WMQ 时，该帐户将在本地主机上解析，并且 WMQ 不需要查询域。但是，当使用域帐户访问 WMQ 时，QMgr 需要查询域以获取请求连接的帐户所属的组。因此，运行中的 QMgr 对于管理员来说显示正常，但从域帐户访问时却失败，这是很常见的情况。
测试这是否是问题的一种方法是确保使用本地帐户解决访问问题。在此示例中，我假设 QMgr 以
MUSR_MQADMIN（Windows 的默认帐户）身份运行。我还将假设服务器名称是bigserver。以下测试将问题隔离到 QMgr 或应用程序。如果尚未这样做，请使应用程序以客户端模式进行连接。使用
MCAUSER('MUSR_MQADMIN@bigserver')更改应用程序使用的客户端通道（替换您自己的服务帐户和服务器名称）并尝试重新连接。如果您收到另一个 2063，则错误出现在客户端应用程序配置中。如果您已连接，则 QMgr 需要被授予查询域的权限。手册中有一个完整的部分向域管理员解释了到底需要什么。如果这是问题，请指出您的域管理员 这里。请不要像这样设置频道。任何能够访问它的人都是WMQ管理员！相反，一旦您开始工作，请将应用程序的服务帐户放入 MCAUSER 字段中，并使用 setmqaut 对其进行适当授权。
The reason code
2063 0x0000080f MQRC_SECURITY_ERRORrefers to something external to WMQ. For example, if configuration files are not accessible to the application, if the keystore password is incorrect or if the QMgr or application are unable to access domain resources.When accessing WMQ using one of a Windows server's administrator accounts, the account resolves on the local host and there is no need for WMQ to query the domain. However when accessing WMQ with a domain account it is necessary for the QMgr to query the domain to get the groups that the account requesting a connection is a member of. For this reason, it is common for a running QMgr to appear healthy for administrators but to fail when accessed from a domain account.
One way to test if this is the issue is to make sure that the access resolves with a local account. In this example, I'll assume the QMgr is running as
MUSR_MQADMIN- the default account for Windows. I'll also assume the server name isbigserver. The following test isolates the problem to either the QMgr or the application.If it is not already doing so, make the application connect in client mode. Alter the client channel used by the application with
MCAUSER('MUSR_MQADMIN@bigserver')(substitute your own service account and server name) and attempt to reconnect. If you get another 2063 then the error is in the client app configuration. If you get connected then the QMgr needs to b granted rights to query the domain. There is a whole section in the manual which explains to domain admins what exactly is required. If this is the problem, please point your domain admin here.Please do NOT leave the channel set up like this. Anyone who can access it will be a WMQ administrator! Instead, once you get it working, place the application's service account in the MCAUSER field and use setmqaut to authorize it appropriately.