I started doing some COM+ (or is that COM-?) work and am having tons of trouble getting my queued components to run, I set them up but I get loads of errors in the application event viewer about the MSMQ API not being able to locate resources and other stuff. I wont go into it too deeply now, suffice to say that I can't find any info anywhere, I wondered if anyone else was messing about with this stuff and had "conquered the beast"
Thanks :confused:
Dont know about MSMQ in COM+ off hand, but I know it was always a pain to set up under NT4. Once working it didn't go wrong, but to get there could be a real headache. Try uninstaling and re-installing MSMQ. Can you post to MSMQ without going via an APP (just to ensure that it works) can you run the Sample MSMQ progs that come with VB Enterprise.
Yeah, I can post manually, the problems are quite deep rooted I think:
I could only run MSMQ in WORKGROUP mode, so:
I had to configure DNS to enable me to:
Install active Directory to:
Promote my (standalone home machine) to a DC to:
Enable me to run a public MSMQ to:
enable me to run QC under this queue (ARRRRRGGGGHHHHHH!) :eek:
I have a feeling something else has gone wrong cause I cannot look at the Group Policy editor (it always fails to load the object)
Thanks for your help Bill, I think i'll build a seperate machine, disable security for my COM+ components and try and run them in WORKGROUP mode and see if that helps - otherwise i'll just go with the theory - I think I get the gist of it after all this!
Thanks again
BTW: Even after running my machine P500 196mb RAM Abit BE6 board with all the following on it it still runs like a greyhound with a rocket up its arse:
W2000 Advanced Server w Active Directory as a DC
SQL Server 2000
Exchange Server 2000
I know the machine is not attached to any others and isn't validating logins or anything, but I thought this lot would kill it!
I dunno what they did to the OS but I was pleasantly surprised for once :)