On Microsoft’s MSMQ forum, David Wellna got to the bottom of a problem being seen with not being able to use all 124 characters for a queue name. Although the queue could be created at this length, it was not possible to change any of its properties without receiving a “Format name buffer supplied to the API was too small to fit the format name” error. As discussed in this MSDN article, Queue Path Names, the full address for a queue is made up of 256 characters for the machine name and 124 for the ......
That was certainly hard work. Find a solution. After browsing the Internet forums a lot, I decided on the free trial version of Jeyo Extender for Outlook (normally costs $20). Install the Outlook add-on and try to connect to the phone. No joy – although this may be because I didn’t accept a firewall change during setup. I tried adding a port exception for 9035 but that didn’t seem to help. Reinstall/reboot/hack the registry – all to no avail Install the Jeyo product on another machine – success! ......
Over on “The autistic coder” blog there is a new post entitled: Limits on message size and why it might be a problem for you “Message queuing technologies always have an upper limit set for the message size they are able to transport. The size limit is usually related to some constraint imposed by the underlying technologies used to implement the queuing system. Usually this is not a problem since the limit for the common enterprise messaging systems are quite large. MSMQ for example has a limit ......
When Windows 2003 came out, Microsoft introduced the ability to broadcast messages to any machines that were listening back. All you had to do was send out a message on a particular port and IP address and any client that had set up a Multicast queue with matching port and IP address would get a copy. Since its introduction, there have been a couple of security vulnerabilities that needed to be removed: Microsoft Security Bulletin MS06-052 Vulnerability in Pragmatic General Multicast (PGM) Could ......