David,

Do you know if fixes are planned to overcome the limitations you mention?

Thanks

Martin

I am sorry to say that the comments above and the Whitepaper on integrating Sharepoint V3 and SBS 2003 leave me totally disillusioned with MS.  As a small business owner having used SBS since its first version I have been pleased with how it has developed, but it appears to be taking a major step backwards.  As I am evaluating Office 2007, and am impressed by many of its features and integration between Office and Sharepoint for Office 2007 it appears as if there are no sensible upgrade paths for SBS users.  Why would I want to have Sharepoint V2 and V3 running alongside each other?  Its already complicated enough managing 1 installation but 2.  Come on get it sorted I can't see Small Business users wanting to wait until the next version of SBS, especially as its likely to be a long time until its launch, as R2 was only released this summer.

OK,

I just found this blog AFTER I tried to install. Now I have this broken server. Does anybody know how I can get back? Unfortunately I can not see if backup ran.

Thanks

Michael

from [email protected]

we installed wss3 on a virtual server running under sbs using win2005 express on that server

no problems with search

incoming email works fine from external email addresses BUT email from internal email addresses does not arrive at the doco folder - the error log says has been processed but the trail runs cold there

any thoughts on a final solution?please reply to email above thx

we have actually been partially lucky because we did not know about these problems as they were well hidden despite i thought staying on top of info thru beta phase- i agree with above that it is bloody appalling that we should hit this wall over basic functionality

Allen Cheyette

David,  I have a quesiton regarding this.  We are currently running Vista machines with office 2007. And of course SBS 2003 r2. We would like to be able to be able to publish a laoding schedule to the local intranet for the dock workers to see.  say on a falt panel monitor.  We could not get this to publish properly in excel 2003 and hold its formating.  I was hoping 2007 would be better.  And it may be from what i have read.  But our sharepoint is currently running off of the sql 2005.  Therefore rendering a sps 3.0 useless.  So do you know if their is a workaround to be able to publish excel to the intranet and keep the formating??

Thanks

In a way I wish I'd read this before I started to install WSS 3.0 on SBS.  In a way, though, I am glad I didn't.

I've been through all the usual loops, migrated MSDE to SQL2005 before the install, successfully installed WSS 3.0, had a working install, then tried to install MOSS 7.0 (why oh why) on top.  Much pain, eventually recovered by uninstalling MOSS, WSS, .Net 3.0, SQL and reinstalling, about 3 times.

The documentation I have just discovered here tells me that companyweb and search won't work.  Well, they do.  I have search, help, the whole shebang.  I am, however, totally grey :-).

And I still have a problem.  SBS Shared Fax works, routes to file folder and email and prints.  It offers me route to document library, which exists on Companyweb (I can browse via web or network places), but can I get Shared Fax to accept the URL?  No.  I cannot browse Company web from inside the Shared Fax utility, and it won't route.  I'm not even getting error messages in the Application log.  I have uninstalled and reinstalled Shared Fax, but no sign.

Is this authentication? Do I need to add additional permissions?  If so, where?  Both the local admin group and Network Service have dbo rights on the sharepoint database, but maybe I need to add some additional rights - for example, doesn't Shared Fax run as Local System or something?

Any opinions gratefully received.

As far as I can tell all of the comments regarding the broken functionality in Sharepoint Services 3.0 when installing on a SBS machine are isolated to a single server environment. Has anyone installed SS3.0 on a seperate windows 2003 (not sbs server). If you do is the email integration still broken? Can SS3.0 utlized Exchange and SQL 2005 on an SBS server if it is running from a separate server?

If so this may be a solution for me as I can buy another server and offline file and print sharing in conjuntion with SS3.0 and leave my SBS server for email, sql, and domain control.

David,

I installed SharePoint Services 3.0 alongside with 2.0 on my SBS box.  I see the value in installing 3.0 and think it's a much better product than 2.0.

Question:  When one is using Remote Web Workplace, and clicks on the "Company Intranet" button, the javascript takes you to the 2.0 SharePoint site (http://companyweb).

Is there any quick way to change the javascript to send one to the 3.0 site (which I happened to setup on port 4444).  

All I need is a quick way to edit the value for the ID 'linkIntranet' from port '444' (companyweb) to port '4444' (my new SharePoint Service 3.0 site).

Thanks.  Mark Como, USA

I really can't believe what you have written in the context of Microsoft[moderated] revenue and profit.  "For the fiscal year ended June, 30, [2006] Microsoft reported an 11 per cent rise in revenue to $44.28bn posting a profit of $2.83bn."  

Your comment "they are indeed working on those fixes, but they are not trivial.  The result is that you are unlikely to see them in SBS 2003, but they will be in the Longhorn version of SBS for sure.

I know this is not an ideal answer, but the product team has limited resources...

[Me: $2.83bn, that reads unlimited resources to me]

...and I am sure we would all rather they spent their time working on LH SBS rather than getting WSSv3 working sooner [Me: You guessed wrong! Just get the integration working as a priority].

Forgot Lornhorne - you're already pissing-off prospective clients in the SME sector.......

When using remote web workplace how do I get into my new sharepoint 3.0 site?

once sharepoint services 3.0 is installed on a sbs 2003 server how do you access the site via remote web workplace.

The only link on the remote web work place is for the old company web.  Also is there a way to skip the RWW and just have the first screen be the sharepoint 3.0 site?

I have a solution for the incoming email problem. Well it seems to work for me!

I have put it up on our website at http://www.mrict.co.uk/resources/incoming_email_for_wss_3_and_sbs.asp if anyone wants to give it a try - no guarantees!

Marcus

Sorry for my earlier rant.  I actually love SBS2003, there's just some stability issues to me.  I've done alot of SBS stuff with small companies and the technology works.

I did yet even more research on my WSSv3 problem.  Since i'm not running SQL 2005, WSSv3 is installing SQL2005Express.  Apparently my issue has something to do with the credentials between sharepoint SQLexpress.  I'm trying a bunch of things right now.  Anymore insight would be useful.

I'm with Trevor Green's idea that he posted earlier:

As far as I can tell all of the comments regarding the broken functionality in Sharepoint Services 3.0 when installing on a SBS machine are isolated to a single server environment. Has anyone installed SS3.0 on a seperate windows 2003 (not sbs server). If you do is the email integration still broken? Can SS3.0 utlized Exchange and SQL 2005 on an SBS server if it is running from a separate server?

If so this may be a solution for me as I can buy another server and offline file and print sharing in conjuntion with SS3.0 and leave my SBS server for email, sql, and domain control.

Does anyone know if this could be used as a workaround?

One question that I have not been able to find an answer to is this:  I want to upgrade (or at least co-install) sharepoint server 2007 enterprise on my SBS 2k3 r2, what are the pitfalls I should be aware of (if it is even possible)?

If you have a problem with the Sharepoint wizard - configuration failed - the following got me past it.

Un-install WSS 3.0

Re-boot (it asked me to)

Re-Install wss 3.0 with Side by Side install with Server Farm

Configuration (even though I do not use a farm)

Once finished, run configuration wizard

Select Create New Sharepoint Database option on first dialog

In server name field enter "server_name\microsoft##ssee"

In Database name "SharePoint_Config" (This was defaulted in mine)

accept all other defaults.

Got past step 2 and finished successfully.... finally!!

see forums.techarena.in/showthread.php for the full thread.

I read a lot of stuff regarding ports like '4444' for accessing the site - which I find really painful.

We use host headers to get around this, and additional entries to our public dns records....  

thus staff.myweb.com

or

intranet.myweb.com

and make these entries to the IIS

Works a treat.

The big question is though......

Once you have successfully installed WSS3.0 on your SBS 2003 box - how do you get an existing site - in ver 2.0 format across to the new wss 3.0??

SMigrate - no!

stsadm - no!

So how??

It seems that unless you tke the whole wss 2.0 onto a spare server and upgrade it and break wss 2.0 - then backup and restore back to the live server there really isn't another way??

Or did I miss that essential piece of information??

What can I do??

Is there a way, in which you install WSS 3.0 on a completly separete windows 2003 standalone server in a SBS 2003 network. and how can you get the company website to point to that.

David,

First, thanks for all the time you spend helping all of us.

I more or less need a confirmation,  I've done the side-by-side install, but my SPS 3.0 alerts are not working, is this one of the limitations and does anyone know of a work around.  Basically, my OUTBOUND emails are not getting out.

Thanks again

Vic

Has anyone found a "simple" way to access WSS 3 from RWW (preferred method) or from SSL?  I'm installing this new SBS box in my environment and really don't see the point starting off in WSS 2 when WSS 3 is so much more advanced.  I don't use inbound faxes so that isn't an issue.  

I think as a group we need to find the easiest way possible to document a solution.  I can't believe there isn't a solution.  I saw one solution out there in 5 parts but frankly that seemed very risky.  I'm simply looking for a way to get WSS 3 to work via SSL and have the company web link on RWW take you to the WSS 3 site.  I've got to believe this is possible.  I see it being a very popular question.

Any real solutions out there?  Especially for a new installation?

Rick

Anyone had this issue. Documents over 300Mb in sharepoint when trying to export them to file using explorer view the progress bar appears then disappears but the file is not moved. No error messages appear. Server is SBS 2003 with SQL 2005 installed.

Thanks

I must agree in part with Alex's sentiment and am strongly concerned with the defensive (turned offensive) excuses for the lagging state of SBS.

It is absurd on the face of it to excuse MS for this sorry state of affairs because of poor allocations of resources when they are fully in control of these same allocations.

As an outsider with over 30+ years in IT, the problem seems much more malignant than simply underfunding and understaffing. More $$$  (US here, no pounds) is not always the answer. Why is the integration of Sharepoint 3.0 non-trival? Is there no coordination between the teams within MS? No participation in the design considerations? Are you saying that Sharepoint 3.0 was simply DUMPED on the SBS team? If so, shame, shame, shame.

Let me be clear. I have nothing but praise and thanks for  the SBS Team. As everyone has pointed out, they are underfunded leading to being understaffed. SBS 2003 and now R2 WAS (emphasis on WAS) an incredible, wonderful product that was far superior to anything we had seen with SBS (I have been a user and supporter of SBS since day one) BUT...

Sharepoint 3.0 - unavailable  for all practical purposes

Exchange 2007 - nope

Frontpage????

WAIT is never an appropriate answer to a REAL PROBLEM. As an SBS user and VAR, I am feeling more and more marginalized. A second-class citizen in the MS community? Absolutely.

I have WSS 3.0 running on small business server 2003 server and am trying to sync my lists with outlook 2007. I can create the connection fine but when outlook does a send and receive it throws an error

"An error occured eith in Sharepoint or outlook. Contact the sharepoint site administrator. HTTP 400"

Has anyone come accross this before? Is there something I am missing.

John ... did your email get to working in w.s.s 3.0?  

I sat down this weekend and got it implemented on our Colo server.   The install was actually pretty smooth and there weren't too many headaches.  I haven't had any luck on getting it to properly publish the intranet company as a live internet site, but I think it's more to do with link translation (I can actually see the site on the internet trying to access the server by name)

But RWW and Exchange are still working.  I think I remember having to do something with either the IP address of the default Sharepoint V3 site since it was sitting on port 80 as well as the default site for Exchange / RWW / OMA et al.

Looks prettier... :)

For us, it was a decision that SBS 2008 is coming out and start getting our techs ready to use the newer setup instead of public folders.  Hopefully this will make an easier migration to Sharepoint V3 on SBS 2008.

I'm looking forward to it...

Have an SBS 2003 Server with a completely dead sharepoint on there. Not sure what happened previously as Im led to believe it never worked. Cant get to it via IIS and right clicking on the companyweb site or via the SBS Server management gui.

My question is.

We would like to now use sharepoint from scratch as its never being used in the past,

On this one 2003 SBS server we have Exchange running with Outlook webaccess with activesync running for the Smart phones obviously with a full ssl cert from godaddy for the activesync to function.

Is it better to / and also can I,

Reinstall sharepoint that came with SBS 2003 originally.

or

Would it be better to / and also could I install Sharepoint Services V3 that ships with the full version of 2003 Std.

Obviously I do not want to corrupt the full exchange IIS Directory in doing eith of the above.

Many thanks

Ok thanks for that exceptionally quick response David.

I prefer personnaly the V3 Option if Im honest,

however Ive seen a few links mentioning re-installing or should I say a repair of V2 in our case back onto SBS, do you have a link yourself to a definitive guide on this.

Thanks very much for your time David I appreciate you taking your time out to help the rest of us who do not specialise in this area.

Loading Windows SharePoint Services V3 (WSSv3) onto SBS 2003 is very feasible during working on this platform after installation.

Did anyone keep record of whatever was here?

www.mrict.co.uk/.../incoming_email_for_wss_3_and_sbs.asp

This was mentioned in the comments above and referenced in one of your old PPTs, David.