The msi on Microsoft Downloads for TaskVision Source requires that my SQL Server default instance is named â€œlocalâ€?  But I don't have such an instance.  I have only the named instance "CORBIN\NETSDK" and do not see in SQL Books Online how to change this name to "local".  Do I have to reinstall SQL Server on my laptop in order to run this msi, or is there some kind of workaround?  Perhaps there is an alternate msi out there that allows me to designate the name of my instance during installation of TaskVision?

Someone please help!

Thanks, 
Corbin

I found this....


I've had the same problem, it took me 2 days to work it out. Ofcourse,
Its pretty simple, once you know how to fix it.

A. Firstly, my VS.net configurations, I have the following software
installed in order. This is important, particularly with IIS:
1. IIS 
2. Visual Studio.net (VB.net) 
3. MS SQL Server Desktop Engine (MSDE) 

B. Copy "taskvisionsource_1.1.0.0.msi" to another directory 
1. Install taskvisionsource_1.1.0.0.msi 
2. Get the error msg "Unable to locate the localhost databaseâ€?".
Don't close this.
3. Go to the directory you selected for installing the source code and
copy all in another directory. Then close the error msg and let the
setup rollback installation.

C. Install database 
1. Go to the directory you copied the source code to and find the
directory "…setup\SQL\".
2. The files SqlServer_TaskVision_Create_DB.sql and
SqlServer_TaskVision_DataLoad.sql should be there, ingnore the 3rd
file.
3. Type "OSQL -S %COMPUTERNAME% -E /I
SqlServer_TaskVision_Create_DB.sql" This will create the sql
TaskVision database to your (local) sql sever.
4. Type "OSQL -S %COMPUTERNAME% -E /I SqlServer_TaskVision_DataLoad.sql" 

D. Let IIS know that the application is there to use. 
1. Go to the directory you copied the source code to and locate the
directory "TaskVisionUpdates" and directory "TaskVisionWS".
2. Copy these 2 directories (including the files) into c:\Inetpub\wwwroot\ 
3. Goto Control Panel -> Administrative Tools -> Internet Information Services 
4. Expand the server node | Web Sites | Default Web Site. 
5. Locate and click on TaskVisionWS directory. 
6. Right-click on TaskVisionWS directory and select Properties. A
dialog box will appear.
7. Select the Directory tab and click on Create button to tell IIS to
let you use this application. The icon on the TaskVisionWS directory
should change from folder icon to IIS icon.
8. Locate TaskVisionUpdates directory. Rick-click, select Properties.
Then click the Create button. The folder icon should change to IIS
icon.

E. Modify the connection in the program to let it know where the databases are. 
1. Go back to the directory you copied the source code and find the
file TaskVision.sln. Then run it.
2. Find the TaskVisionWS project and double-click on AuthService.asmx. 
3. Select "dbConn" sqlconnection contorol, go to "Properties" and
change the "Connection string" to the "TaskVision" sql database you
created in step C3. above.
4. The easiest way is to select <New Connectionâ€?gt; 
5. (local) for server name. Tick "Use WIN NT Integrated security".
"TaskVision" for the database

G. Run TaskVision.

THANKS SO MUCH!  I was having a problem getting the Server side of TaskVision installed, and this worked for me.  The other thing that was strange is that I didn't have 1.0 of the .NET framework installed on the 2003 server, so I just recompiled the code in 1.1 and then deployed the new dll's to the WebService bin directory.  Once I got all of that figured out, it worked like a dream.

Thanks for posting!

-Jason

Okay, so that all worked great for the server setup...could connect to the server and everything...But now, the updates are not coming down properly.  In fact, there for awhile, it was bringing updates down for the old version from the main taskvision site.  Finally I figured out that I had to give the virtual directory created for updates Directory Browse capability.  This started to look more promising...until I recieved this error half way through and update:

"The auto-update of this application failed with the following error message:

Download of a new update from 'http://myserver/taskvisionupdates/1.2.0.0/' failed with the network error:  The remote server returned an error: (403) Forbidden.

To correct this problem, try rebooting the computer & re-launching this application."

Anyone ever seen this error?  Of course, when I navigate to 'http://myserver/taskvisionupdates/1.2.0.0/' in a browser, i can see all the files just fine...What's going on?

Thanks!

Okay, after some trial and error, I finally got this working.  All I had to do was make sure in IIS for the taskvisionupdates folder was to have Application Name on the Directory tab be blank, Directory Browsing must be checked, and Execute Permisions must be set to Scripts Only.

Now it works!!  :D