Long time no blog. I've been busy attempting to further my comedy aspirations and otherwise building my empire. Also, I've been napping whenever convenient.
Customer error reports are generated when an Autodesk product unexpectedly exits, (i.e. “crashes”). Many folks have created informative blog posts about the importance of Autodesk CERs (like this one from Shaan Hurley), but few have discussed how to make them bow to your will.
Here's a document I created for my support customers.
https://autodesk.box.com/s/hskrrsryfz41bakediw8
And here's a taste of what's inside!
I cross my fingers that you don't crash, but if you do - send in the CER!
Customer error reports are generated when an Autodesk product unexpectedly exits, (i.e. “crashes”). Many folks have created informative blog posts about the importance of Autodesk CERs (like this one from Shaan Hurley), but few have discussed how to make them bow to your will.
Here's a document I created for my support customers.
https://autodesk.box.com/s/hskrrsryfz41bakediw8
Information that is automatically passed to
Autodesk’s CER system includes:
·
Machine Information
o
Operating system version
o
Locale
o
Graphics card and driver version
·
Application information
o
Product name
o
Product version and service pack level
·
Runtime information
o
How long the product has been running, or “uptime”
o
Last 5 commands run
o
Exception thrown (“what happened” to crash the
program)
o
Callstack (information about what routines were
running)
o
Add-ins installed
o
Hotfixes installed
The following information is not part of a CER:
·
License data
·
Company information
·
User-specific information (unless otherwise given in
the email or description fields).
This important data is tracked and frequently
investigated by Autodesk staff, however, messages in the description area are
not read real-time. If you need technical support you must go through your regular support channel.
See Autodesk’s official privacy policies for more
information:
No comments:
Post a Comment