Dreamweaver Template Error: Error reading file (Site Location/info) returned incomplete data

Question

Hello!
I am working on new website we are creating for our company. I have never really had any Dreamweaver template file errors before...so this one has me really stumped! We purchased the site files from Template Monster and I have contacted their tech support, but I have not had much luck with them.
I started out by creating the Dreamweaver template folder that includes the template files that I would like to use. I started creating some pages using the template. I placed all the html pages in the main folder of the website. When I go to update the template to those pages I get the following error: "Error reading file (Site Location\Folder name\Dreamweaver template name) returned incomplete data".
I am not sure what I am doing wrong. Any help and advice would be greatly appreciated!
The site is a CSS based site with a Flash navigation menu. Since it is in the production phase, I do not yet have it placed on a server so you can take a look at it at this time (although if really needed and we cannot find an answer, I may be able to get the test site on line - if someone thinks they can help me answer this problem by viewing the site). Right now the site is housed in the same place we house all of the other sites we have produced and all of our other templates on our other websites work just fine. The main difference with this site is that we did purchase files from Template Monster to help speed us along during the construction of the page structures and also this site has a Flash Navigation Menu and a few other Flash elements (something our other sites do not really have).
I am using Abobe Dreamweaver CS5 and Windows 7
Thanks again for taking the time to help find and answer to this problem!
-J

Answer 1

I am curious as to why no one likes them around here.
They have spammed these forums in the past.
The code on their pages is rarely 'best-practice' code.
There are much better choices available.
My co-worker and I have to share the files, since we are editing the site together. The files are not local on our computers, but on the company's f drive that have Novell on it.
This arrangement is a recipe for disaster.  The correct way to collaborate on a site with a colleague is with the following setup:
Each of you must have a LOCAL site (local to your workstation)
You would use a single remote location as a staging area, so each of you would have a site definition that specifies your own workstation for the local site, and the same network shared location as the Remote site
You will both need to enable Check In/ Check Out
You will both have to agree to PLAY BY THE RULES!
One (or both) of you will also need to have a second site defined that has the staging server as the local root folder, and would have the PRODUCTION server as the remote site.  I'll explain how to use this site soon.
When you use CI/CO, your 'gold-standard files' are on the staging server.  To begin working, you would connect to the staging server, and double click on a file, which will a) fetch the file from the staging server to your local site, and b) CHECK OUT the file to you.  As long as you have the file checked out, it cannot be edited by your colleague.  When you are done with your edit, you would CHECK IN the file (which uploads it to the staging server).  It can now be edited by your colleague.
When you add templates to this scenario, things get even more complicated, although manageable.  If you ever need to make a change to a template you must use the following procedure:
ALL FILES MUST BE CHECKED IN - this includes both you and your colleague.
One of you would connect with the SECOND SITE, open and edit the template, and save it propagating the changes to all "LOCAL" files (i.e., on the staging server).
Each of you would then need to return to the FIRST SITE, and again check out any files you want to work on.
When changes are done, and files are ready to publish, connect to the SECOND SITE, and upload the files from STAGING to PRODUCTION.
Does that make sense?  It's important that it does.
I need to add in one more tab/link to the Flash nav bar.
Using Flash for navigation is a VERY POOR CHOICE, unless you also have redundant, text-based navigation on the pages.  By using Flash to navigate, you guarantee: a) your pages will not be spiderable by search engines, b) your pages will not be navigable by iPlatforms, and c) your pages will be inaccessible to anyone browsing with screen assistive devices.  Someone is making bad decisions about this site, in my opinion.