MOSS 2007 and .NET Framework 3.5 SP1

At one of our customers we had to faced with a very-very sneaky trouble.

The environment: Windows Server 2003 SP2 x64, with MOSS 2007 Enterprise, and of course .NET framework 2.0 and 3.0. The SQL Server 2005 is installed to a separated hardware. The farm is a test environment on the customer side, with almost 1 year on-time: this is the integration "bridge" between our dev environment and the customer's production one. Every solution is deployed to this server first, here are the user acceptance tests, and after the acceptance they'll be deployed to the production farm.

As we wanted to use Linq4SP in a new solution, we needed the .NET framework 3.5 too.In our developer environment everything was working well, so let's go to the customer. The administrator guy installed us the .NET framework 3.5 SP1. The solution was deployed successfully, so everything seemed to be going well and good. But during the testing we had to be faced that the Records Center wasn't working. The error message: "The DevRC Records Center could not be found or accessed."

I could exclude Records Center (RC) configuration errors, as it was working before. But I had to be sure that it's not an error on the RC side, so started to some tests:

  1. I changed the Records Center settings on the Central Administrations, and set one other RC to the default. Same error.
  2. During a former project we've developed a custom Records Center Web Service and changed the orginal one to that. So I installed it to this server as well and set it to the default instead of the OOTB one. Same error, and our web service haven't received any request.

These facts show me clearly: the error is occured during sending documents to the RC, and not on the receiving. But what the hell is the real cause?…

Let's uninstall the .NET framework 3.5, but don't do anything with 3.0 and 2.0 – Records Center error occured again. OK, that's not enough, but as we assumed that the RC error is occured by something around .NET frameworks. So go forward: uninstall .NET fw. 3.0, then .NET fw. 2.0, finally install them again (first the .NET fw. 2.0, then .NET fw. 3.0). – Oh yes, this is a very good idea, but this step is also attacking the SharePoint itself. It's not a big surprise that the MOSS was capitulated, the IIS can't handle the requests even after running Config Wizard.

First of all: Allow the ASP.NET 2.0 in the IIS. (The default setting is Prohibited after installation…)

Wow, Central Administration became accessible now! But unfortunately the content sites drop HTTP 403 error, even after IISRESET. So the sites are alive, but unavailable to access them because some authentication issue – moreover this happens in the backend, so something went wrong in the IIS or SQL. Well, at this customer we hadn't access to the SQL server directly, and the MOSS admin user is not permitted to create new databases – so we're unable to create new Web Application to the MOSS. Hmmmm… One more option to testing the issue is extend one of the existing Web Applications. Let's choose this option, and extend our existing (but unable to work) Web App on http://dev:80, for example in the Intranet zone, to the http://dev:12345 address. Yes, this new Web App is working!

And here is the surprise: the old http://dev:80 is working again!

I don't know exactly what happened, but I think the SharePoint ran into some configuration issue that occurs an inconsistency before the Web App extending. But after that step this "something" has been set to the corrent value.

Short test: yes, the Records Center works fine. After deleting http://dev:12345 we have the same environment as before the full game. Let's go to reproduce the issue!

But now I was trying a little modified scenario: first I installed the "plain" .NET framework 3.5, without SP1. Well, the Records Center works on. But just after installing SP1 for .NET 3.5, the RC immediately became dead.

Well, the conclusions: in x64 environment, the MOSS Enterprise and .NET framework 3.5 SP1 can be conflicted. As I have any further information about the status of this issue, or maybe about a hotfix to it, I'll inform you immediately!

Linq4SP – RC2 is available to download!

First of all, I'd like say a big thank you for everyone who has been testing Linq4SP RC1. We've fixed the bugs sent by you and found by ourselves, and finally today evening we could relese the next version of Linq4SP. The fixed bugs are the followings:

  • Before RC2 in case of choosing more than one site to generate, the Generator had managed the sites and lists in a wrong way. With RC2 you are able to use more than one site in the same time, without these uncomfortable issues.
  • in case of lookup fields configured incorrectly (for example, task lists of team sites), the Generator skip the wrong column, instead of freezing :)
  • concurency handling

If you're interested, you can download the Linq4SP RC2 from here. Of course, if you find some bugs errors or anything strange, don't hesitate to contact us!

Linq4SP – RC1 is available to download!

image As you probably know, our developer team has been working on the LInq4SP in the last couple of months. Linq4SP is a readable-writable Linq provider to SharePoint (WSS 3.0 and MOSS 2007), with a lot of interesting and useful features: support the handling of list items, documents, folders, content types, enumerations usable for choice columns, etc.

The Linq4SP RC1 is available to download now: you can play with it, try the features and abilities, and feel the power of this brand new developer extension.

Just download Linq4SP RC1 here. To start using it, copy the files to your WSS 3.0 or MOSS 2007 server. The DLL file must be in the same folder as the Generator.

After starting the Generator, open your site collection and select the sites to be available in the Linq4SP context. After that you can select the lists and libraries to be used in your Linq4SP expressions, and finally generate the context.

As next step include the generated source file and the attached dll to your Visual Studio project and that’s it.

Enjoy!

The documentation is under construction, but you can find a simple CHM help file in the ZIP package as well. Moreover, there is a sample site as well as test cases, that can help you in starting to use Linq4SP. I hope, you’ll find them useful.

 

After your playing with Linq4SP, I’d be very happy if you could send us your questions, opinions or any feedback.