As I read through the report, a few things stood out:
- It's from someone at Microsoft
- The title refers to an "Octopus Agent". We have a "Tentacle" but we don't refer to it as Octopus Agent.
- There's a COM+ error that I've never seen before
- The product version number starts with 15. I'm still working on version 1
This isn't the first time I've received a bug report like this:
- Error: Setting up the Octopus Agent failed: System.NullReferenceException
- Error: Setting up octopus agent failed
It turns out that these bug reports refer to a Microsoft tool that seems to go by the name of "Octopus Deployment Tool". I don't know much about it, but it seems to be an internal Microsoft tool that might have something to do with BizTalk.
What really made me chuckle is that the post was from a Microsoft email address (although at least it was only a v- vendor account). I suppose when Microsoft users come to me to ask for support for their own internal tools, I must be doing something right.
What should my standard reply for these kinds of wrongly-directed bug reports be? Here's my attempt:
Enjoying these posts? Subscribe for moreSubscribe now
Already have an account? Sign in
Hello, I'm Paul Stovell
I'm a Brisbane-based software developer, and founder of Octopus Deploy, a DevOps automation software company. This is my personal blog where I write about my journey with Octopus and software development.
I write new blog posts about once a month. Subscribe and I'll send you an email when I publish something new.Subscribe