3

We installed SBS 2011 (Sharepoint 2010) a couple of years ago and it's running fine. We never used Sharepoint features.

Now we wanted to explore Workflow features so I went to http://sites and logged in as a Sharepoint administrator (successfully).

My problem is that whenever I need to go into the web-based Sharepoint Designer, I get an error. The designer is active on the server, it should be available at https://sites:987, but I always get Connection reset when I browse to that address.

I even tried momentarily bringing down the Server Firewall to check if it was a firewall problem, but the same thing happens...

A distinctive circumstance of this server is that it is not connected to the Internet(that's a company requirement, I can connect occasionally for updates, but not permanently). I've been told this shouldn't be a problem for what I'm trying to do.

Can you please advise, and help me troubleshoot? Thank you.

Improve this question
13
  • Are any events logged in the Windows Event logs when you try to load the web-based SharePoint designer? If so, please include them in your question.
    – I say Reinstate Monica
    Feb 9, 2015 at 16:39
  • Sorry, nothing. I checked these logs: Windows\Application, Windows\Security, Windows\System, Microsoft\Sharepoint_Products\*, Microsoft\Windows_Small_Business_Server\*.
    – pgr
    Feb 9, 2015 at 17:25
  • 1
    I find it very stranged that nothing is getting logged. There must be something in some IIS log that I don't know of...
    – pgr
    Feb 9, 2015 at 17:25
  • Are any related SharePoint events logged when the server is booted?
    – I say Reinstate Monica
    Feb 9, 2015 at 19:01
  • 1
    I connect monthly for updates. I think it has all the updates up to mid-January, and will soon be getting the latest.
    – pgr
    Feb 11, 2015 at 13:21

1 Answer 1

Reset to default
1
+50

Microsoft provides a helpful guide on TechNet for repairing SharePoint Foundation 2010 on Windows Small Business Server 2011. You can complete the following repair steps without deleting any existing data:

  1. Repair the SharePoint Foundation 2010 Domain Name System
  2. Repair user access to the internal website
  3. Repair user access to SharePoint Foundation 2010

If these repair attempts fail, your next step is to Recreate your SharePoint Foundation 2010 application and content database. This step is more invasive but still leaves you with your own data, as noted in the article:

This topic describes the steps necessary to repair the Windows SBS SharePoint web application and content database. If you experience problems with a different SharePoint Foundation 2010 web application, you can follow the steps in this topic to repair the content database for that application.

This is a lot of work to save content you've never created. If I were in your shoes I'd jump right to the end and Reinstall SharePoint Foundation 2010. No, you don't walk away knowing exactly what broke your old environment, but you will probably save yourself a lot of time chasing an answer that may never be found anyway.

Improve this answer
2
  • This means hours of work, and off work hours, I will try to avoid it. It is a "blind" solution to a problem that I thought was very simple. But if nobody gives any better solution, maybe the problem is not that simple! :-) I will award the points to you at the end of the bounty period if nothing better comes along. Once again, thanks for all your efforts.
    – pgr
    Feb 13, 2015 at 9:52
  • I completely understand and would also search for a direct solution as you are doing. It would be great if you find one, but if not, this is likely what you'll have to do.
    – I say Reinstate Monica
    Feb 13, 2015 at 12:28

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .