I have a sharepoint Server that I uninstalled. (I just did it through add-remove programs and uninstall)
Then when I tried to re-install Sharepoint foundations 2010 (the same version I uninstalled) it would seem to work correclty, but it would not give me an option for Stand Alone. Only giving me an option for Existing Web Farm or New Web Farm.
I have tried to delete the instances of SQL Server (Sharepoint) but still getting this problem.
I have Windows 2010 Server (same as Windows 2008 R2)
There is no "Stand Alone" option. I just installed a fresh SharePoint 2010 and only had the options for "Existing Server Farm" or "New Server Farm". As explained in the same dialog: Go for "New Server Farm" when you are installing it on a single server (stand alone).
Related
I've installed SQL Server 2016 (Standard Edition) on a Windows Server 2016, selecting Integration Services to be installed too. I've also installed SSMS and SSDT from the same installation media.
I am running SSMS as administrator and can connect to the local Database engine.
My user is a Windows and SQL Server admin.
However I cannot connect (explicitly using the server name) or even browse to the local Integration Services?
Receiving the following error.
SSIS not browsable and can't connect
Having already searched for an answer to this problem, many suggest checking that the service is running etc. which can be seen in the Services and SQL Configuration Manager.
Services shown as running
I've also tried turning off the Windows Firewall to establish if that is the cause of the problem but it had no effect.
Anyone got any ideas what might be preventing it from being accessible?
I've had this problem last month. In my case I had to install the 32-bit version of access database engine (on my 64 bit windows).
Sql data tools works with 32-bit
https://www.microsoft.com/en-us/download/details.aspx?id=54920
The later SSMS versions (16.x and 17.x) will only connect to their respective versions SQL 2016 and SQL 2017. Microsoft is planning to retire the older method in favor of the SSISDB, which is more secure.
Link to the official statement from Microsoft (in the note box).
I have had the same problem and the solution was to install the old interface on top of the existing one (SQL Server Management Studio 2016). Here's link to the installation file. After having installed this, I can now connect to the integration services. You will have to set it up of course and give yourself Rights
Perhaps this was asked before but I can't find a whole lot on this, so I would appreciate some help.
Our architecture is as follows: Win 7 desktop on a domain with VS 2010. MS Sql server R2 on Win Server 2008 R2 Ent; SharePoint 2007 on Win 2003; SharePoint 2010 on Win 2008 R2 Ent; Visual Sourcesafe on yet another separate Win Server 2008 R2 Ent server. On this server I have just installed TFS and was running Advanced Config Wizard.
As I'm new to TFS all my selected options are based on intuition and perhaps common sense but Reporting Services and SharePoint aren't working. With reporting services after I add my sql server name (and I've tried IP address and dns name) neither the Report Server URL nor Report Manager URL is populated. (Note: What do I need reporting services for anyway?)
So I've opted not to use reporting services, which as I said, I don't know what is the benefit of it.
Next, in the SharePoint configuration, I wanted to use the existing SharePoint farm which is installed on a separate servers. Testing the Site and Administration URLs would throw an error: "The following site could not be accessed. ... Either ... not installed the Team Foundation Server Extensions, or Firewall... "
I suspect it is not the firewall so then the TFS Extensions. Having search that topic as well seems to point back to the TFS's configuration, so I'm a completely at a loss.
Any ideas?
Thanks,
Risho
/posted from a smartphone since employer blocks this site/
Edited: I was looking at this article http://msdn.microsoft.com/library/dd631915.aspx but I don't have the options listed in the step-by-step solution. TFS Admin Console has this: Top tear - server name, below is Application Tear then Proxy Server, build Configuration and Logs. Expanding Application Tear shows Team Project Collections, SharePoint Web Applications, Reporting, and Lab Management.
You have to configure the SharePoint extensions on each SharePoint machine you wish to connect to TFS. Install TFS on whichever SharePoint machine (or both, if you plan to use both). In the configuration wizard, you should have the option to configure SharePoint Extensions. Once done, you should be able to re-run the readiness checks in the Advanced Wizard on your Application Tier machine.
Is it possible that can I use Sharepoint server as development machine also. My mananger has asked me to use one of the newly purchased server for Sharepoint server as well as sharepoint development.
In future we will do some small development so what type of installation do I need?
Please guide me for the following which one I should install or which one is not required.
Standalone or Farms
VM
SQL Server 2008
VS 2010
SharePoint 2010 can run on a 64-Bit Windows 7, as per instructions from Microsoft.
It does not work on 32 Bit Windows as SharePoint 2010 is 64-Bit only, and it does not work on Vista.
Yes, it is possible to use your SharePoint server as a development machine. I'd suggest using a VM as it allows you to quickly and easily switch between, revert and deploy setups should something go wrong (and things WILL go wrong with SharePoint).
At work, my machine runs Win Server 2008 and I remote into a Hyper-V hosted VM which itself runs Server 2008 - I develop and run SP on that VM. Since I have SP, SQL Server and VS2010 all running on it at the same time, I allocate the VM at least 5.5 GB of memory (and it's still hungry for more).
You can develop for SharePoint 2010 on a Windows 2008 Server x64 or on a Windows 7 64bit. A Windows 7 is of course only recommended for development.
Most developers use a standalone machine for their SharePoint 2010 development. Creating a farm is complex and $$.
Personally I develop in virtual machines. I have on clean vm image that I copy for every new project (client). You need a powerful computer to run these virtual machines. At least 4GB memory and a recent multicore cpu.
You will need Visual Studio 2010, SQL server and ofcourse SharePoint. Office can also be handy but is not needed. SQl server express is included in Visual Studio and the SharePoint install also installs SQl server if needed. Certain Visual Studio versions include an "SQL server developer" license.
I will need a Sharepoint Server 2010 install for learning purposes.. I already have a Win 7 x64 os installation with vs2010 and I use it for my current development needs.
The question is ... would you recommend to install sharepoint onto an existing win 7 installation, create a separate OS instance (win7 or win 2008 r2?) for sharepoint development purposes or maybe create a VM for that? I have 4GBs of ram and I wont be able to extend it.
What are your experiences with dev environments for sharepoint 2010? I remember that 2007 was a real resource hog - maybe there is a 'magical' switch that allows sharepoint 2010 related services to be turned off?
If you thought SharePoint 2007 is a resource hog, SharePoint 2010 is even worse. The full installation creates lots of Windows services and IIS application pools. Which makes it really hard to stop SharePoint since all those services start automatically.I agree with others that you should use the VM approach but I think you need Windows Server 2008 R2 to be able to create 64-bit VMs.
Here's a link to powershell scripts for stopping/starting SharePoint services: http://blogs.msdn.com/b/emberger/archive/2009/11/16/stop-and-go-with-sharepoint-2010-on-your-workstation.aspx
I personally always run it in a different instance - either a separate machine or a virtual machine. Sharepoint 2010 is massive, and changes your system with a magnitude not seen by any previous sharepoint version, in terms of databases, scheduled tasks, services...
You should install your SharePoint 2010 in Server2008 R2 if you can ,since then you can do a complete install and use domain account.The installation in win7 is a standalone install and only use system account.It does not match what is in production...
Or if you can, virtualize your SharePoint environment.You need to give at least 4gb ram to SharePoint VM otherwise it is running like a dog.
I am deploying a VB.net 2010 winforms application, and when I install it on the client's machine, the install process also installs an instance of SQL Server 2005 Express. The application connects to a central SQL database on the server. To install, I am using the "Publish" option in VS 2010
Why does it do that? There should be no need for a local instance of SQL Express. Is there a way to avoid installing SQL 2005 Express (I know it is free, but I would rather not have it installed if possible)
It's likely that whatever technology you're using for packaging/deployment is including the installer for SQL. For the default setup project, I believe it is a checkbox for a pre-requisite.