AMQ8075: SID not found for ASPNET

[jg1007]

Folks:

Any help would be appreciated. I am writing a project in ASP.NET that communicates with MQseries using the ActiveX COM MQAX object. We are getting an error on the Queue manager server to the affect of

AMQ8075: Cannot find the sid for userid 'ASPNET'.

Apparently since I am connecting through a .NET web app, it tries to connect to MQSeries through this userid instead of the domain account we had prviously set up in the mqm group.

I saw on another fourm that someone suggested to add the aspnet account to the mqm group on the server. However, our server doe snot have that account! It does not have the .net framework installed. Does it need to? Is there another way?

Also, if I just add the local aspnet account on the server, is it going to work? Isn't that a different account than the one I am using to authenticate.

Anyone who has had this issue, I could really use some help here!

Thanks,

JG

 

[kevinf2349]

If you are trying to use a .net application you are going to need the .net framework installed....at least that is my experience.

 

[jg1007]

No offense, but that seems kinda silly doesn't it? The server is not running any .NET applications, it is simply receiving my MQ message and transporting it. Isn't MQSeries supposed to be platform independent?

I understand my web application having to have the .NET framework, but you are telling me that the MQ Manager server needs to have the .NET framework just so that I can add the aspnet account to the mqm group?

Thanks,

JG

 

[kevinf2349]

Aha I see what you mean now. You are client connecting to a server and it is the server that is looking for the ASPNET userid in its groups.

What is defined for the client channel? Do you code an MCAUSER ?

 

[jg1007]

Kevin:

No we don't use MCAUSER because there are security implications by using that.

However, this is what I did. I went to the server and created a 'aspnet' local user with no password, and added it to the mqm group, and now it is working.

Does that make any sense to you?

I need to test fully to make sure this is really fixed, but why would it now find the aspnet account simply by adding a local account with that name? It is not the same SID as the one I came in with.

I will update on my tests....

Thanks for your reply...

JG