DataEnvironment.Asa Corruption

[Guest_imported]

When you copy a web application from one server to another, the DataEnvironment.asa file is not brought over correctly.&nbsp;&nbsp;I have to, after copying, attach with InterDev, delete and re-add all the connections and commands in the data environment. ( See MS document Q216569.)<br><br>Has anyone encountered this too.&nbsp;&nbsp;After you move a working web app, you get an &quot;exception occured&quot; message.<br><br>Is there a fix for this? The cutting and pasting gets old with 50 commands.<br><br>

 

[MerlinB]

I have just encountered this issue. It is to do with the DataEnvironment.asa keeping a copy of the connection string. When you copy it to another web site - which has a different SQL server name, then the DE commands will fail.

Try adjusting the server name to the target server on your development PC and save the file. copy the DataEnvironment and Global.asa to the target.

Clearly the local web will now suffer! Until you edit the connection strings back again.

 

[Guest_imported]

Of course, I kept the DSN the name.
Since I posted, I talked to MS. This was a known bug at the time, and there was no fix. I ended up changing each with a stored procedure, and accessed each directly with an RS DTC rather than DE references.

tfth