issue:

you might have created recordsets using the data binding panel and even test them successfully but when they create some dynamic content on the page and try to switch to live data preview you get an error message

reason:
this has usually to do with an error in the site definition - or the server is not working at all or cannot run ASP in the specified directory.

the reason that you can test recordsets in the data bindings window is that at that stage Ultradev retrieves the data directly from the database.

when you drag some of the data components to the page you create ASP, JSP etc code that will later retrieve the data on the server. "Live Data Preview" lets you test this code within Ultradev (you don't have to preview it in the browser) but Ultradev does not interpret the ASP itself but uploads the files to the server and retrieves the results via http:// and displays them on your page.

this is why it is important that the server settings are correct.

troubleshooting:

1) make sure that the server is running.

just upload any file and try to view it in the browser via it's http:// address. if it doesn't show you don't have to bother with Ultradev yet, you must get your server running first.

click here to download a simple ASP file that returns the location of the server root. this would be a good testing file since it will show not only if the server works but as well if ASP will work in the specific directory (you might not be allowed to run ASP from just any directory on a server).

2) check your site definition

if you look up the site definition you will find two settings for "Application Server Info": "Local Web Server" and "Remote Web Server"
an easy missunderstanding might be that you set it to "Local Web Server " just because you have a server installed on the machine you are working on, regardles where the local site folder is situatet.

here is how the settings should be used:

"Local Web Server":
this works only, when your local site folder (= what you might know from Dreamweaver as your local root folder) is situated within the root of the server.

e.g. for Personal Web Server the server root is normally C:\Inetpub\wwwroot
the local folder could therefore either be this folder itself or any subfolder within, like C:\Inetpub\wwwroot\mySite

since this files are already on the server they don't have to be sent anywhere to be executed. in this case the "Application Server Info" can be set to "Local Web Server" and the "Web Server Info" (which tells Ultradev the upload path of your files) can be set to "none" ( as said before, you don't have to upload this pages. they are already on the server. think of it as working only with a local site but no remote site at all)

"Remote Web Server"
if your local site folder is anywhere else like C:\Windows\Desktop\mySite or any other drive on your local network the files have to be sent(=copied) to the server should they be executed.

in this case you have to set the the "Application Server Info" to "Remote Web Server" AND define the proper upload path in "Web Server Info". if the server is on your machine you most likely don't use FTP but "Local Network" and define the path (in our sample) as C:\Inetpub\wwwroot