Developer and entrepreneur Leon came up with a Troubleshooting Checklist while developing an application.
Check it out at http://www.secretgeek.net/simple_checklist.asp
Leon's a funny guy - here are some of his Gems
- blame the guy who left last week
- disable the customer experience improvement program
- what would Jesus do?
- reboot 3 times
- temporarily allow Popup's
- remove and then recreate all Bluetooth partnerships
There are 164 items, enough to Keep you busy, if nothing else !
Inspired, here is my list for
Troubleshooting a Common GP Problem
All the items don't apply to all cases, looking at the problem you normally know which ones to look at first. I'll probably update this - but these were all the things I could think of at the top of my mind.
- Note the exact error Message
- Search Knowledgebase with exact search on
- Search Microsoft GP Groups
- Search your system using Google Desktop or Microsoft Desktop
- Does the problem occur only on one machine ?
- Gather the following information from the machine that has a problem
- Generate a DexSQL Log and review it
- Get a copy of Dex.ini and Dynamics.set
- Check Version of Software (GP, FRx, IM, Biz Portal, 3rd Party, SQL)
- Check Windows version and service pack
- What 3rd party products are being used ?
- Check the ODBC
- Is the user using named printers ?
- Does the logged in user have restricted permissions ?
- Does the user have required permissions in the required folders on their machine and on the network
- Check Hard Disk Space
- Are any Anti-virus software's running on the machine ?
- Have any changes been made to this machine recently ?
- Check Event Log
- Create a new ODBC
- Check the user's security, try the process with a user with full permissions
- Talk to the IT guy to get this view
- Try and replicate the problem on the test server for the company
- Try and replicate the problem on your test server
- Check queries fired in Profiler
- Use the Support Debugging tool
- Ask a consultant who has used Great Plains in the last millennium
- Open a support ticket with Microsoft Support
And then, follow up with the user after a couple of days for small talk, and to make sure they are doing fine.