SharePoint User Group UK

Hi,

is anyone aware of any issues with the X64 bit versions of Sharepoint. I've built 2 servers. one on x32 bit tin, and one on x64.

When I select "I need to" task (http://google.co.uk) on x32 - it works

When I select "I need to" task (http://google.co.uk) on x64 - I get status bar message "error on page".

Has anyone seen this? I rebuilt the x64 server from sratch todaybecause I had this fault yesterday, and had convinced myself I'd screwed the install, but I did exactly the same on the x32 and it work, so I'm sure it's not me doing something wrong. When I hover over the arrow to launch the link, in the status bar, I can see it's going to run "Java script: TAT WP_ jump Menu()".

Rgds

Mike

Mike,

Todd Bleeker and Bill English indicated that x64 was not yet stable at the recent SUGUK meeting,  however regular suguk forum poster Matt Groves stated he done this (with the exception of the index server due to limited support for IFilters).

I also know that all of the performance stats coming out of Microsoft are based on full x64 setup, so it must work.

Perhaps Matt could post his experiences here :)....?

Andrew

---

www.21apps.com

One of Bill's main points on X64 was non default web parts that were not out of the box. I am wondering if this is something to do with IE or the 64bit .net framework.

Does this problem occur when you launch the task from the server or is it the same when you try it from an XP Client but connecting to the X64 server ?

Steve Smith

Hi Steve,
it's default out of the box Collaboration site. Not added or taken anything away from the main page. Just added a link on the "I want to" and get the same results if I run IE on server, or if run from and XP SP2 client or any other OS or browser for that matter.

I've done two identiacal setups, one on x32 and one on x64, the x32 works fine. I have a support call raised with MS SharePoint support, who should call me Monday.  I just know I'm gonna be thinking about this all weekend. Guess I'll have a beer or three now, as I've now been looking at this for the last 3 hours from home....sad or what.

Mike

Just had a call back from Microsoft on this issue, we are not alone!

Other people have raised the same issue, so MS know about it. I now have to send them Logs and reports from the server for them to look at. So, if you have 64 bit tin, don't install the 64 bit sharepoint code if you want a working system.....right now that is.

Mike

Well we have had a MS Gold partner on site today, did a complet install of the OS on the x64 server tin, and all the pre-requisites. Installed sharepoint and created the first site, and problem is still there.

So, 100% positive it's nothing we did during the setup, and this MS Partner consultant got the same results as us.

Still waiting on MS support to come back to us, but I suspect this is gonna be some time in the fixing.  Will keep you all informed of progess, and solution once it's available.

Rgds

Mike

We suspect that the install order may have something to do with the Web-Part failure. MS are going to test this in their own labs, but the MS Engineer I've been working with thinks it may be SP2 for the OS which locked something down?? anyway. my system is now working correctly.

Original setup:-

 

1. Windows 2003 OS installed.

2. Windows Service pack 2 installed.

3. KB931836 Installed.

4. KB927977 Installed.

5. SharePoint prerequisites installed - .NET Framework 3.0.

6. SharePoint installed – From MS supplied media – End Item Part No 76P-00601.

7. KB932091 Installed

8. SSP and Collaboration Portal configured.

9. IE 7 Installed

 

Result:- The “I Need To” web-part was failing.

 

 

Current setup:-

 

1. Windows 2003 OS installed.

2. SharePoint prerequisites installed - .NET Framework 3.0.

3. Changed permissions on SQL added SysAdmin, and ServerAdmin roles, in addition to the normal roles required.

4. SharePoint installed – New Download from Microsoft.

5. Windows Service pack 2 installed.

6. KB931836 Installed.

7. KB927977 Installed.

8. KB932091 Installed.

9. IE 7 Installed

10. SSP and Collaboration Portal configured.

 

Result:- The “I Need To” web-part functions as expected.

Mike

Cool,

So you now have 64bit MOSS installation :)

---

www.21apps.com

We sure do, but, my previuos post as to the resolution is complete Bol**X, as soon as I started to lock down the mysites the original error popped up again with the webpart failing. So I back tracked and reporduced the result. See below.....

Ahhh!

OK, I must be stupid - This is what I've done.

Installed Sharepoint

Created the SSP
Created a mysiteweb - In the "My Site Settings" Set the Default Reader Site Group to "IT Department"

Created "eisweb" this is our Collaboration Portal, by default it has the "I Need To" web part. Changed the permissions on this site to allow "Domain Users" read access.

Back in the Shared Services Admin Shared Services 1 - Personalization services permissions, removed "Authenticated Users" and added "IT Department" and gave them Personal Features and Personal Site permission.

So now, when someone from IT Dept browses eisweb (collaboration portal) they can create a mysite (they see the option) and they can run the links in "I Need To" webpart.

When a non IT Dept user browses the eisweb portal, they don't see the "my site" link, and are unable to use the "I Need To" webpart, but the links showing in Top sites work fine.

BAck to the SSP - Shared Service rights, Added Domain Users - and gave them "Personal Features" and now the "I Need To" webpart works.

What am I missing here? Have I misunderstood the rights?

Mike

Andrew,

Nothing really to report, it was a OOTB pilot system, 2 x x64 web/query, with 1 x64 ECS and 1 x86 Index. Only changes were branding and some feature stapling for content types.

Worked perfectly...

---

Matt Groves
Managing Consultant (Information Worker Solutions) - Trinity Expert Systems Ltd [www.tesl.com]
Blog: www.mattgrovesblog.com

Have there been any other issues with x64 and MOSS 2007? I know about the lack of Adobe IFilter support on x64 with Indexing PDF files. Is there anything else I should be aware of?

Also, can someone advise me on the best server farm structure? I have 3 servers available to me (I cannot add any more). Here are the scenarios I have come up with. What are the pros and cons for each? If it were you, which scenario would you choose to have the best performance AND the least amount of problems/conflicts/issues.

Scenario #1

Server #1 = WFE = Windows 2003 R2 64-bit, MOSS 2007 64-bit
Server #2 = Database = Windows 2003 R2 64-bit, SQL Server 2005 SP2 64 bit, MOSS 2007 64-bit
Server #3 = Index = Windows 2003 R2 32-bit, MOSS 2007 32-bit

Scenario #2

Server #1 = WFE = Windows 2003 R2 32-bit, MOSS 2007 32-bit
Server #2 = Database = Windows 2003 R2 64-bit, SQL Server 2005 SP2 64 bit, MOSS 2007 64-bit
Server #3 = Index = Windows 2003 R2 32-bit, MOSS 2007 32-bit

Scenario #3

Server #1 = WFE = Windows 2003 R2 64-bit, MOSS 2007 64-bit
Server #2 = Database = Windows 2003 R2 64-bit, SQL Server 2005 SP2 64 bit, MOSS 2007 64-bit
Server #3 = Index = Windows 2003 R2 64-bit, MOSS 2007 64-bit, FoxIt IFilter Software for PDF's

Or, is there another scenario that would be better?

Thanks in advance for any help you can provide!

Carol

Carol,

You didn't mention the spec of each server, so I will assume they are identical...
Nor do you include if you are using STD or ENT, I will assume ENT.

Server#1 - WFE/Query - Win2k3 R2 Std x64 SP2, MOSS2007 x64
Server#2 - Index/ECS - Win2k3 R2 Std x64 SP2, MOSS2007 x64 (with PDF filter for Foxit)
Server#3 - DB - Win2k3 R2 Std x64 SP2, SQL 2005 Std x64 SP2

You don't need to install SharePoint on the DB server unless you want it to host roles other than DB, which you probably don't, I know I wouldn't.

You don't mention anything about your requirement for availability, given three servers you'd struggle to deploy without a single point of failure. Nor do you mention anything about sizing (both in terms of data and users) or use type (intra/extra or www) - without this info it's hard to give you a detailed response...

Hope this helps anyway!!

---

Matt Groves
Managing Consultant (Information Worker Solutions) - Trinity Expert Systems Ltd [www.tesl.com]
Blog: www.mattgrovesblog.com

Hi Carol,

 

SharePoint is DB intensive so at the very least have a powerful standalone SQL server;  all the better if it's running 64bit.  

 

You could also use the normalised operations per second (NOPS) formula for working out how many servers you require: * i'm not sure how accurate it is? I personally feel the server NOPS supported figures are on the high side.

 

Regards

Andrew

 

A x B x C x D = normalised operations per second (NOPS)

300,000 x E

 

 

A = Number of users

B = Percentage of users that use the system on a typical day

C = Number of operations per active user per day (1-10 normally 8)

D = Peak factor (1 – 10 normally 5)

E = Number of working hours per day

 

Server Configuration	Est NOPS Supported
Small Farm; One MOSS Server and one SQL server both configured with 2GB of memory and a dual 2.8 + GHz CPU	65
Small Farm; One Moss Server and one SQL server, both configured with 2 GB memory and a dual 3.0 + GHz CPU	105
Medium Farm; Two web and query servers, one index and admin server and One SQL server with 2GB memory (2 x 3.0 + CPU’s)	110

 

 

i.e.

 

15000 * 50 * 7 * 10 / (360,000 x 12)

 

=  12 NOPS