Discussions

nope spoke to soon. The vista machine goes to open the explorer view , doesnt prompt for password and just gives a "web page cannot be displayed" message

How odd, I managed to sort it on the xp machines by adding the server to the trusted sites list in internet options. Gonna test the Vista Machine see if it needs the same doing to it

Hey !!

Well i finally got round to installing Visual Studio 2008 on my Vista developer machine. My other machines ive kept on VS2005 SP1 for the moment whilst i play with 2008 a bit more.

Now im having a very odd problem with Team foundation server. Basically i have a LAN with 5 machines that run in a workgroup (no domain here at home) and at the centre of activity is a Windows Server 2003 machine. The Windows Server 2003 Machine runs virtual server and Team Foundation server 2005 (its quite a beefy machine with 8gb of ram allowing me to run multiple virtual machines). Now this weekend ive setup a new virtual machine on the server 2003 box. The new virtual machine is server 2003 with VS Team found server 2008.

To keep a long post short all the boxs can see the new team foundation server and connect to it ok. However the VS2005 with sp1 i had to install a compatability patch for team explorer to be able to create projects on WSS3.0.

Ok so the new virtual machine as i said its server 2003 , windows sharepoint services 3.0 and sql server 2005 enterprise edition.

All seems to be running and working ok. The vista machine can connect to the VSTFS2008 , can check files in, can even make builds.

Now te odd problem im having is if i right click on the project and select show project portal , the project portal comes up in a new IE7 window. Now if i select "Project Management" on the left hand side, then when it loads the documents if i select explorer view it asks for my name and password. So if i input this it then pops up again and repeats popping up until i press cancel. Now on the vista machine when you press cancel i just get a "IE could not load this page" etc etc. On the xp machines when you press cancel the explorer web folder view loads if i try directly on the server it just plain fails but from researching i understand this is because server 2003 doesnt support webdav.

Now on VSTFS2005 i didnt have this problem and web folders in explorer view loaded fine.

Whats missing here ? how can i get web folder expplorer view for project portal documents to work as it should ? any ideas ?

Ive looked at all permissions and authentication and i cant see basic authentication being used anywhere (as the sharepoint server whitepaper suggest this can be a cause). The fact that the xp machines can connect to the vstf2005 and view explorer view in the project portal ok, but not with vstfs2008 suggests this is a vstfs2008/wss 3.0 problem ?

Any help would be appreciated

im in a bit of the same predicament at the moment. Been off woork ill last couple of weeks but just after VS2008 Team was released i was looking into how it would effect our current VS2005 TFS servers. The only informaiton i could find was that VS2008 and TFS2005 were not compatible. If you tried to do a build on something which is new in 2008 e.g. wpf applications on TFS2005 it would not work. Can anyone shed some light as to what is and isnt compatible with TFS2005 and VS2008 ?

Hmmm , your limited as to what you can do with citrix. If its a citrix environment where the users are on thin clients your going to be limited as to what you can pull off. Remember most thin clients have very very limited specs (at least the ones i support have 16mb ram and a screen res of 640 by 480)

To optimize performance ditch animations, images and make sure your code is highly optimised.

http://channel9.msdn.com/ShowPost.aspx?PostID=345561#345561

finally found the answer to the problem

1st step was to go into sql server config manager > right click MICROSOFT#SSEE > Hide Instance change from yes to no

2nd step is to go into surface config area > set remote connections for MICROSOFT#SSEE for TCP/IP AND NAMED pipes.

I can now connect remotely to MICROSOFT#SSEE via SQL management studio.

There should be something in the Sharepoint 3.0 documentation about this as the default install renders surface area config manager useless

for example here is SACFSAC

http://img338.imageshack.us/img338/2553/picture1mb6.jpg

NOTICE microsoft#ssee and mssql server both appear !!!

here is SACFF

http://img338.imageshack.us/img338/8226/picture2lq4.jpg

This screen stays up for about a minute trying to connect to both instances however it eventuallt fails

http://img338.imageshack.us/img338/7010/picture3yr7.jpg

BUT REMOTE CONNECTIONS ARE SET FOR BOTH TCP/IP AND NAMED PIPES !!!! grrrrr very frustrating. Why WSS installs embedded edition , why cant it just create a new instance in mssqlserver ? if i stop MICROSFT#SSEE in the sql configuartion manager i am able to get back into SACFF !!

not true. In the surface area config you have "Surface are config for services and connections" and "surface area config for features". SACFSAC connects fine to both the MSSQLSERVER and MICROSOFT#SSEE whereas SACFF attempts to connect but bottoms out with an sql error 26 with remote connection, whereas I explicitly know remote connections are allowed. Like wise any computer in the network cant remotely connect to that MICROSOFT#SSEE instance because the problem as i see it the instance name here is MSSQL$MICROSOFT##SSEE ???

I believe there is a bug with sql EE and the SQL surface area configuration tool.

Basically I was running SQL Server 2005 standard edition for general visual studio development. The servcie name for the sqlserver instance is MSSQLSERVER and the display name is SQL server (MSSQLSERVER). Now recently i installed WSS3.0 (the server previously had no instance of windows sharepoint services). When WSS 3.0 installed it installed the sql server embedded edition instance. So now I have 2 sql instances on the server. One named MSSQLSERVER and the other named MICROSOFT##SSEE which are the names taken from the sql server configuartion manager. HOWEVER if i go back into the SQL server 2005 surface area configuartion tool and launch "Surface are configuration for services and components" whilst the name and display name hasnt changed for the MSSQLSERVER instance there is an inconsistancie with the MICROSOFT##SSEE instance. The service name displays as MSSQL$MICROSOFT##SSEE. Now the problem is if I launch "surface area configuartion for fetures" it complains it cant connect to localhost\MICROSOFT#SSEE because remote connections are not enabled. However both named pipes and tcp/ip are allowed and in the surface area configuartion tool remote connections are allowed for that instance. Does the surface are configuration for features connect to the sql instance using the display name or service name ? because if its the service name surely it should be connecting to MSSQL$MICROSOFT##SSEE and not MICROSOFT#SSEE ? if this is the problem how do i rename the service name from MSSQL$MICROSOFT##SSEE to MICROSOFT#SSEE ???