I am facing problem while installing Sharepoint 2010 Server on Windows-7 Professional I have followed the steps given in this MSDN page. Still I am getting the following error while trying to run Setup.exe.
Can anyone help me on this?
Thanks
It seems that SharePoint Server 2010 is only compatible with
Windows Server 2008 x64. But it's not. check this.
Source: Installing Microsoft SharePoint Server 2010 on Windows 7 x64
It is much simple to do this. Just a little work and your SharePoint Installation ready to work on Windows 7 64 bit Client OS.
You can simply install SharePoint Server 2010 on your client OS just by modifying a config file.
Copy CD contents to a folder on your hard drive and Follow following steps:
Go to the Files folder
Go to the Setup folder
Open config.xml
Add the following line before the closing </configuration> tag
<Setting Id="AllowWindowsClientInstall" Value="True"/>
Save the file and Run the Setup.exe. now it will work fine.
Remember: These lines are Case Sensitive so Write them correct.
On Windows 7, install the following additional prerequisites required before running Setup.exe:
Microsoft FilterPack 2.0. At a command prompt, type the following:
installation directory folder\PrerequisiteInstallerFiles\FilterPack\FilterPack.msi
Microsoft Sync Framework
SQL Server Native Client
Windows Identity Foundation (Windows6.1-KB974405-x64.msu)
Chart Controls (this is not required if you are going to install SharePoint Foundation 2010).
SQL Server Analysis Services - ADOMD.Net (this is not required if you are going to install SharePoint Foundation 2010).
For more detailed installation tutorial go through MSDN - Setting Up the Development Environment for SharePoint 2010 on Windows Vista, Windows 7, and Windows Server 2008
It seems like your copy of Sharepoint 2010 Server is intended to be installed onto a machine running Win Server 2008 SP2 or later. Not win 7. Either upgrade your machine or see if there's a more compatible copy of share point server.
Related
I am testing an upgrade from TFS 2008 to TFS 2012. Currently I'm using SharePoint 2007 on a separate server, running Windows Server 2003 Enterprise x64 Edition w/ SP2. I do NOT want to upgrade SharePoint as part of the TFS upgrade.
My understanding is that to continue to use SharePoint with TFS 2012, the TFS extensions must be installed on the SharePoint server...
When running the tfs_sharePointExtensions.exe, I immediately get an error message that:
Error : TF400436 : Team Foundation Server Extensions can only be installed on a Server Operating Systems.
TFS setup did not detect an existing instance of SharePoint installation on this machine.
TFS SharePoint Extensions cannot be installed on a 32-bit operating system unless SharePoint is already installed.
Either install SharePoint manually on this machine, or run this installation on a 64-bit OS and we will install SharePoint for you.
In the installation log I see these lines:
Condition 'TFSDev10Installed' evaluates to false.
Condition 'NOT ((NTProductType = 3
AND (VersionNT64 = v6.0 OR VersionNT64 = v6.1 OR VersionNT64 = v6.2))
OR (VersionNT = v6.0 AND NTProductType = 3 AND
(SharePoint12_32bitExists OR SharePoint12_64bitExists OR
SharePoint14Exists)))' evaluates to true.
[Error] TF400436 : Team Foundation
Server Extensions can only be installed on a Server Operating Systems.
TFS setup did not detect an existing instance of SharePoint
installation on this machine. TFS SharePoint Extensions cannot be
installed on a 32-bit operating system unless SharePoint is already
installed. Either install SharePoint manually on this machine, or run
this installation on a 64-bit OS and we will install SharePoint for
you.
This is clearly a server OS, 64bit, with SharePoint installed and running, so it isn't clear to me how I might be able to correct this. I haven't been able to get any guidance using Google.
Any ideas on what I might need to do to be able to continue with the SharePoint extensions installation?
the problem is the Server 2003 you can not install TFS2012 (or it's SharePoint-Extension) on Windows Server 2003
See Requirements:
http://msdn.microsoft.com/en-us/library/vstudio/dd578592%28v=vs.110%29.aspx
or this:
Installing TFS Express on win 2003 server
Maybee you can try to Install the SharePoint extensions for TFS 2010 and try to connect them with your TFS 2012. Maybee this work.
Regards
I recently setup a sharepoint server 2013 on our company and have found really good examples how you can override the suitbar with custom links.
Now that I'm trying to implement those examples i get to that point where Visual Studio 2012 and Office development tools is installed.
When i choose to start a new project I select New Project > Templates > Visual C# > Office/SharePoint > SharePoint Solutions > SharePoint 2013 Empty Project hit ok and i get an error that says Sharepoint not installed?
Am I supposed to install VS 2012 and develop om my Sharepoint 2013 server directly?
A very common way to develop SharePoint applications is to run a virtual machine (hyper-v under windows 8 for example) on your development workstation.
You can also dual-boot into a vhd file.
You can also install Windows Server 2012 and use one of the many desktop conversion techniques to use it as your primary operating system on your workstation.
Another often seen technique is to have a virtual machine hosted in the cloud or a datacenter, running both SharePoint Server and Visual Studio. Then connect to that machine using Remote Desktop.
With some trickery, you could have the SharePoint 2010 installer install om a workstation OS. This no longer works on SharePoint 2013. The reason this support was removed is due to the inclusion of Boot from VHD and Hyper-v into Windows 8.
It is my experience that if you just want to build your application and not run or debug it, that just having the assemblies copied over from an actual SharePoint Server will allow you to do that. I haven't found an updated document for SharePoint 2013 yet.
Yes. You have to develop on the sharepoint server directly using Visual Studio as Sharepoint server GAC has the required server object models to work programatically with sharepoint server object model.
You can aslo develop on client machine using Client Object Model or WCF Data Services Framework.
I know there are so many questions and articles on this topic and I have searched hours and hours on the Internet so far, but I still couldn’t find the right answer for my question. I was assigned the task to investigate the development environment for SharePoint web parts by my company. The money is not an issue but it must be the proper way to do it.
Here is my ideal plan: at developer desktop, install VS2005/2008 (it is already installed), VS2005/2008 Extension for SharePoint and WSPBuilder. It is also installed a Virtual Machine and the VM runs windows server 2003/2008. WSS3.0 and SQL Express 2005/2008 will be also installed on VM.
Developer’s desktop is a web parts development environment. Developers use VS to develop the SharePoint web parts and then run the WSPBuilder, it will deploy the web parts into the SharePoint testing environment on VM. So the VM is just a SharePoint testing environment.
It looks like a good idea, however, it doesn’t work. Why? Because VS extension can't be installed on developer’s desktop as it doesn’t have WSS3.0 installed!
I definitely don’t want to install the VS on the VM, because our developer desktop has installed VS and we don’t need to have 2 VS licences for 1 developer.
Any idea what is the best way to set up the development environment for SharePoint web parts?
Thank you in advance.
You won't be able to develop for SharePoint (WSS 3.0) unless your development environment includes an installation of at least WSS. In general, development is done on a Windows Server 2003 Virtual Machine (Visual Studio is installed directly on this machine). However, SharePoint can be installed on Windows Vista and Windows 7 machines, so your development machine may be able to host SharePoint itself, but it is far easier to do this on a VM.
My SharePoint development VM has the following installed:
Windows Server 2003 R2
SharePoint 2007 (Including SQL 2005)
Visual Studio 2008
Visual Studio Tools for Office
Office Server SDK
Visual Studio Extensions for WSS 1.3
Obviously you can use WSPBuilder instead, but I much prefer VSSWSS 1.3, but that is developer preference.
I believe (should be verified with Microsoft) that the licensing for Visual Studio can be extended to Virtual Machines when used by the same developer (depending on your agreement).
An alternative for you which may or may not work depending on your priorities.
Install Visual Studio 2010 and SharePoint 2010 Foundation to your development server.
Grab a copy of Microsoft.SharePoint.dll from a SharePoint 2007 server.
Use VS2010's tools to develop a web part but manually change the reference to the 2007 dll's (+ also see "Build a SharePoint 2007 Web Part with a Visual Studio 2010 Visual Web Part Project") so you are outputing a 2007 compatible web part.
When you delploy your 2007 web part to your local 2010 server it will just work (as its backwardly compatible)
When you deploy your 2007 web part to your test/qa/production servers it will work too.
Advantages
You're working with latest greatest
version of VS and the sharepoint
tooling so you get one click deploy,
automatic creation of WSP packages
etc. Nothing against WSP Builder etc (they are great) but my moneys on vs2010 sharepoint extensions for the future.
You're ready if/when your
company moves to 2010.
You're developing on a Windows 7 machine, not a 2003/2008 server and or a VM so this has advantages for licensing, speed and ease of use (dual monitor support from VS running on a VM?)
Edit - to deploy web parts to other servers you create a .wsp package and then deploy via STSSADM or another tool (SharePoint solution installer or other admin tools).
I haven't used VSSWSS or WSPBuilder. I've always used STSDEV for SharePoint 2007. And I've always used Windows XP to do it. I don't know if VSSWSS and WSPBuilder act the same, but, as Ryan was saying, I copy whatever SharePoint DLLs I need from a SharePoint 2007 server into a Solution Folder in my Visual Studio solution. I then select Add Reference in my project and browse to the DLL.
In four years, I've never had any problems with this method. The solution packages build just fine and work on any SharePoint server. I lose the option to debug, but I'd rather stay on my machine than go into a VM or Remote Desktop.
After installing sharepoint server 2010 on server 2008 64 bit . every thing goes well no errors,but after clicking sharepoint server 2010 central administration from the program menu i got this message
The version of this file compatible with the version of windows you you're running .Check yourf computer system information to see whether u need an x86 or x65 version of the program , and then contact the software publisher
browser issue? what could be wrong?
Try to launch a few times the configuration wizard in sql server and in your SP server and it will come back.
It worked for me
I've been struggling for some time now to be able to use the built-in functions in Visual Studio 2008 to handle *.mdf database files with SQL Server 2008 Express. I'm running on an x64-based system, and I've read that there is a known problem with this setup, but the hotfix has not solved my problems.
Basically, what happens is that when I try to add a new *.mdf file to the App_Data folder of a project, I get an error message saying:
Connections to SQL Server files (*.mdf) require SQL Server Express 2005 to
function properly. Please verify the installation of the component or download
from the URL: http://go.microsoft.com/fwlink/?LinkId=49251
My (unsuccessful) steps to solve this:
Uninstall all possible associated programs to Visual Studio, SQL Server or .NET Framework (which left .NET 2.0 Compact Framework and .NET 3.5 Compact Framework, and nothing else .NET related, installed).
Reboot.
Install .NET 3.5 SP1, SQL Server 2008 Express and SQL Server Management Studio 2008 Express via the Web Platform Installer 2.0 (Beta).
Reboot.
Install Visual Studio 2008 Professional from disc.
Reboot.
Install Visual Studio 2008 Service Pack 1.
Reboot.
Install hotfix.
Reboot.
Start VS, create new Web site and try to add database. Still get the error message...
When I look in the Help/About dialog, the hotfix shows up among applied updates. I have also checked and double-checked that the SQL Server instance name is correctly set in Visual Studio (I copy-pasted the instance name from the login screen in SSMS).
Why does the hotfix not solve my problems? Am I doing things in the wrong order, or do I have the wrong software versions somewhere?
According to the KB article, the problem is that Visual Studio doesn't correctly detect "some registry keys" - but nothing is said about which keys. Does anyone know how to fix this manually?
Oh, and yes - I've seen this post. I know I could just "downgrade" to the x86 version of SQL Server, but I really want to make this work with the x64 version (if nothing else, just because it's supposed to work...), so that solution doesn't really solve my problems. Please don't close this as a duplicate.
I had this same error, VS 2008 SP 1 on Vista Ultimate 64 bit with SQL 2008 Express 64 bit. Downloaded the hotfix and rebooted, started up SQLEXPRESS and still got the error.
Then I changed my "SQL Server Instance Name" (under VS 2008 -> Tools -> Options -> Data Connections), which was blank, to "SQLEXPRESS" (versus ".\SQLEXPRESS", which is what I use in my login screen under SSMS.) and now it works like a charm!
Dave
Try changing the user on which the SQL Server Express is running. This can be changed in Services managment (press Win+R, type in services.msc). Choose SQL Server Express, right click -> Properties. 'Log On' tab and select: 'Local System account', tick the 'Allow service to interact with desktop' - this is what worked for me.
I'm not sure I ever solved this, but I've now moved over to Visual Studio 2010 (RC at the moment, but I'll get the full version when it's availabel) and everything works seemlessly.