Hi Guys,
Migrating the data (using DTS) is dangerous between versions.
If we could see your error messages for the upgrade then we could probably help you fix the problem and allow you to upgrade succesfully. After you upgraded then you can create a fresh install and copy the data over.
However it seems a little silly to want to begin with a fresh install. All an the upgrade does is run SQL commands. No file maniplulations are done. So it should be safe to use a bugnet system after upgrade and no need to "wipe install".
The problem with just copying data in after a clean install, is the new system will have different data in the ASP Membership tables ("aspnet_*" tables). So you need to completely roll that back too. Your install date and machine key are critically important. After you have done a clean install, roll back the machine key and install date settings. This will allow BugNET to decrypt the passwords after you copy the data.
However, I dont see any issues with this if you wipe all the tables and copy only the table data in from a database of the same version.
NB: PLEASE NOTE this needs to be doen on a fresh system. You can't "Add issues" to an existing system. All the projects, issues and all kinds use integer primary keys which start from 1. Let me know if you need help with this.
Also remember to copy your UPLOADS directory for the attachments. You need to check your previous setting in the main bugnet administration screen (the setting for storing the attachments on the file system or in the db). This setting needs to be the same on the new bugnet.
Long explaination. I hope it helps. Let us know.