As some of you who work with SharePoint might have noticed, when creating a web-part-page-document-library, the new pages loose the quick launch. Patrick Tisseghem has written a blog on why this is and how to fix it using SharePoint Designer.
Gustaf Westerlund
CRM and SharePoint Consultant
Humandata AB
www.humandata.se
As many of you might know, the functionality of double directional syncronization between SharePoint lists and Excel sheets was removed in the 2007 version. Why? I don’t know, it probably didn’t make the magic features-that-will-be-included-line. However, an add-in for Excel 2007 can now be downloaded that enables this feature.
Check it out: http://www.microsoft.com/downloads/details.aspx?FamilyID=25836e52-1892-4e17-ac08-5df13cfc5295&DisplayLang=en
Gustaf Westerlund
CRM and SharePoint Consultant
Humandata AB
www.humandata.se
Well, my daughter is sleeping so I have some time to blog a bit and read some other blogs.
The so-called May-VPC containing a CRM Demo environment will soon be out-dated and a couple of guys are working on a new environment. It will contain SharePoint 2007, VS 2005 and a lot more which is good news, since it therefore can be used for demos, education and simple development projects (larger development projects should be based on an empty CRM, with some customer specific data). I am looking forward to it! Read a bit more about it on Mennotk’s blog: http://blogs.msdn.com/mscrmfreak/archive/2007/06/12/new-microsoft-dynamics-crm-vpc-update.aspx
Gustaf Westerlund
CRM and SharePoint Consultant
Humandata AB
www.humandata.se
Looking for some good links to SharePoint related material, have a look bellow:
SharePoint whitepapers:
http://www.combined-knowledge.com/Downloads%202007.htm
Office SharePoint Server 2007 on TechNet
http://technet2.microsoft.com/Office/en-us/library/5233cf43-6a8f-40cb-9014-0724600e7e381033.mspx?mfr=true
Microsoft Office Systems for Architects
http://msdn2.microsoft.com/sv-se/architecture/aa699381.aspx
Application Templates
http://www.microsoft.com/technet/windowsserver/sharepoint/wssapps/templates/datasheets.mspx
I will publish more when I find anything useful!
Gustaf Westerlund
CRM and SharePoint Consultant
Humandata AB
www.humandata.se
I was working with setting up a demo/lab environment with SQL 2005, MOSS Ent 2007 and MS CRM 3, Office 2007 Ultimate.
However, I had problems getting the reports to work, when trying to access the reportpage, I got the error: “Reports.config has invalid schema”.
I looked around a bit on the net and found that one of the blogs I suibscribe to actually discussed the problem at hand.
http://blogs.msdn.com/mscrmfreak/archive/2006/05/17/599371.aspx
It seemed that the reason for the error was that .NET 2.0 had been defaultet for the CRM 3 website (and we all know it is .NET 1.1, right!). So, tried to run “aspnet_regiis -r” as described but I got the same error as the comment by “Matt Thomas“, my CRM just stopped working.
So, what to do. I found that when you run “aspnet_regiis -r” it resetts all websites to the version of .NET that you run it from (ex. C:WINDOWSMicrosoft.NETFrameworkv1.1.4322aspnet_regiis -r, will set all websites to use .NET 1.1). This is not desirable since my MOSS 2007, SQL 2005 RS and all MOSS admin sites (central admin, my site, SSP) all should run .NET 2.0. So, I thought it better to reset all sites to .NET 2.0 and then manually set the CRM site to 1.1. And so I did, and CRM just stalled when loading. No error message, no nothn’!
This got me thinking that you should be able to run one version of aspnet_regiis for just one website. So, by trying the all-usefull “/?” parameter I found that using “aspnet_regiis -lk” will list all different IIS-paths and show which version they were running. This was what I found:
C:WINDOWSMicrosoft.NETFrameworkv1.1.4322>aspnet_regiis -lk
W3SVC/ 2.0.50727.42W3SVC/1/ROOT/ 2.0.50727.42
W3SVC/1/ROOT/_layouts/images/ 2.0.50727.42
W3SVC/1/ROOT/_layouts/inc/ 2.0.50727.42
W3SVC/131316714/root/ 2.0.50727.42
W3SVC/131316714/root/Reports/ 2.0.50727.42
W3SVC/131316714/root/ReportServer/ 2.0.50727.42
W3SVC/1720207907/root/ 2.0.50727.42
W3SVC/2/ROOT/ 1.1.4322.0
W3SVC/2/ROOT/MSCRMServices/ 2.0.50727.42
W3SVC/2075257487/Root/ 2.0.50727.42
W3SVC/2075257487/Root/_layouts/images/ 2.0.50727.42
W3SVC/2075257487/Root/_layouts/inc/ 2.0.50727.42
W3SVC/425288717/Root/ 2.0.50727.42
W3SVC/425288717/Root/_layouts/images/ 2.0.50727.42
W3SVC/425288717/Root/_layouts/inc/ 2.0.50727.42
W3SVC/493651791/Root/ 2.0.50727.42
W3SVC/493651791/Root/_layouts/images/ 2.0.50727.42
W3SVC/493651791/Root/_layouts/inc/ 2.0.50727.42
Aha! Can you see what is wrong? Well, when I manually set CRM to .NET 1.1 it didn’t do that recursivly! The CRM webservice is running as a separate application, and I hadn’t changed that. This is the row that shows what’s wrong:
W3SVC/2/ROOT/MSCRMServices/ 2.0.50727.42
So, I checked what parameters you could use with aspnet_regiis and found that “-s
aspnet_regiis -s W3SVC/2/ROOT
I think it might just have worked with going in to the CRM site and changing it for the MSCRMService virtual directory, but I thought it better to set it to the entire MS CRM 3 website recursivly to make sure everything was ok. When it had completed (takes a minute or two), I ran “aspnet_regiis -lk” again to check the current status:
W3SVC/ 2.0.50727.42W3SVC/1/ROOT/ 2.0.50727.42
W3SVC/1/ROOT/_layouts/images/ 2.0.50727.42
W3SVC/1/ROOT/_layouts/inc/ 2.0.50727.42
W3SVC/131316714/root/ 2.0.50727.42
W3SVC/131316714/root/Reports/ 2.0.50727.42
W3SVC/131316714/root/ReportServer/ 2.0.50727.42
W3SVC/1720207907/root/ 2.0.50727.42
W3SVC/2/ROOT/ 1.1.4322.0
W3SVC/2/ROOT/MSCRMServices/ 1.1.4322.0
W3SVC/2075257487/Root/ 2.0.50727.42
W3SVC/2075257487/Root/_layouts/images/ 2.0.50727.42
W3SVC/2075257487/Root/_layouts/inc/ 2.0.50727.42
W3SVC/425288717/Root/ 2.0.50727.42
W3SVC/425288717/Root/_layouts/images/ 2.0.50727.42
W3SVC/425288717/Root/_layouts/inc/ 2.0.50727.42
W3SVC/493651791/Root/ 2.0.50727.42
W3SVC/493651791/Root/_layouts/images/ 2.0.50727.42
W3SVC/493651791/Root/_layouts/inc/ 2.0.50727.42
As you can see, the MSCRMService is now also .NET 1.1.
After this I restarted the IIS with “iisreset”, and tried to run CRM and the reports;
Everything worked as it should!
Gustaf Westerlund
CRM and SharePoint Consultant
Humandata AB
www.humandata.se
Recent Comments