Archive for September, 2007
EPMsync tool between Project Server and Portfolio Server has been released on CodePlex
25 September 2007“Microsoft Office Project Server 2007 (Project Server) and Microsoft Office Project Portfolio Server 2007 (Portfolio Server) integrate via the Portfolio Server gateway. Data is exchanged by running either an import or an export from Portfolio Server. But this exchange is done in bulk and typically batched. There is a desire to have a more granular experience in near real-time. The EPMSync Solution Accelerator is a proposed solution to this problem. The EPMSync Solution Accelerator synchronizes Portfolio Server attributes with Project Server custom fields (and a set of project level built-in fields). The solution is made up of a Windows Service and a number of supporting applications.”
http://www.codeplex.com/EPMSync
Popularity: 1% [?]
Firefox WYSIWIG Compatibility for SharePoint
24 September 2007Firefox does not support Rich text editing for SharePoint 2007 and MOSS.
http://blogs.msdn.com/sharepoint/archive/2006/07/19/671735.aspx
Possible Solution
http://www.telerik.com/help/radeditormoss/
Popularity: 1% [?]
MOSS Integration with SQL 2005 Reporting Services – Common Problems
24 September 2007Few days back I was trying to install MOSS Add-In for SQL Server Reporting Services. The number of links below can show the problem that I have faced. Its very simple to install the add-in but configuration is not easy. Do read the installation and configuration guide before installing it on your server.
MOSS Add-in for Reporting Services Download (Important)
http://download.microsoft.com/download/f/d/c/fdcb3a53-0cb1-4e67-a1b6-45b89b3c59cf/SharePointRS.msi
Microsoft SQL Server Reporting Services - Installation and Configuration Guide for SharePoint Integration Mode (Important)
From looking at the comment stream for the "Microsoft SQL Server 2005 SP2 Reporting Services integration with WSS 3.0 and MOSS 2007" blog entry that was posted back in February, I can see that some people are still having difficulty installing and configuring SSRS in "SharePoint Integration Mode." Fortunately for you, Raju Sakthivel, an architect in the Microsoft Consulting Services group, has taken the time and effort to perfect and then document the whole process in the attached installation/configuration guide (3.5 MB in Word 2007 format). I hope that you will find it useful. Please leave a comment if you have any additional questions or issues.
SSRS and SharePoint make a powerful combination! If you have implemented an innovative or value add solution with the combo, please leave a comment with a description of what you’ve done.
Introduction to SQL Server Reporting Services
http://www.simple-talk.com/sql/sql-server-2005/business-intelligence-in-sql-server-2005,-part-1/
http://www.simple-talk.com/author/dejan-sarka/
SQL Server Recovery
http://blog.bpsnw.com/2007/09/my-steps-to-recovery.html
Report Builder and Forms Authenticaton in SQL Server Reporting Services 2005
http://blogs.msdn.com/bimusings/archive/2005/11/29/497848.aspx
Publishing Reporting Services reports to MOSS
Today! (Cleaning up Reporting Services SharePoint Add-In Setup Problems)
Direct Reports (Brian Welcker’s Weblog) : Reporting Services
http://blogs.msdn.com/bwelcker/rss_tag_Reporting+Services.xml
Microsoft SQL Server 2005 SP2 Reporting Services integration with WSS 3.0 and MOSS 2007
BI Whitepaper SQL Server Business Intelligence
|
Readme for Microsoft SQL Server 2005 Reporting Services Add-in for SharePoint Technologies | ||
wnload.microsoft.com/download/f/d/c/fdcb3a53-0cb1-4e67-a1b6-45b89b3c59cf/readme_rsaddin.htm”>ownload/f/d/c/fdcb3a53-0cb1-4e67-a1b6-45b89b3c59cf/readme_rsaddin.htm
SQL Reporting Services, Cannot create a connection to data source login failed for user ‘null’
http://www.experts-exchange.com/Microsoft/Development/MS-SQL-Server/Q_21495110.html
Help with setting up Reporting Services
http://forums.asp.net/p/1061289/1530295.aspx
how can associated ’sa’ with a trusted SQL Server connection in sql server 2005?
http://forums.asp.net/p/939856/1221882.aspx
how can associated ’sa’ with a trusted SQL Server connection in sql server 2005?
Configuring Reporting Service Add-in for sharepoint - HTTP status 401: Unauthorized.
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1379070&SiteID=1
Help!! "The report server has encountered a configuration error…….."
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=150192&SiteID=1
Report deployment error in SharePoint Integration mode
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1609891&SiteID=1
IIS 6 MMC problem with ReportServer and ASP.NET configuration
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=250225&SiteID=1
Error "Connection Could not be made to the report server" when attempting deployment
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=335663&SiteID=1
Reporting Services and SharePoint 2007 install
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=588158&SiteID=1
Sharepoint integration - User cannot be found??
http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=1483741&SiteID=17
rsAccessDenied when accessing Report Server –
Cannot use ‘partitionResolver’ unless the mode is ‘StateServer’ or ‘SQLServer’ on server running SharePoint 2007
http://rfinn.spaces.live.com/blog/cns!4E19D0E183DFC38B!180.entry
You receive an "HTTP Error 401.1 - Unauthorized: Access is denied due to invalid credentials" error message when you try to access a Web site that is part of an IIS 6.0 application pool
http://support.microsoft.com/kb/871179
Error message when you try to modify or to delete an alternate access mapping in Windows SharePoint Services 3.0: "An update conflict has occurred, and you must re-try this action"
http://support.microsoft.com/kb/939308
How to use Trusted Connection when SQL server and web Server are on two separate machines.
http://weblogs.asp.net/achang/archive/2004/04/15/113866.aspx
Reporting Services Trouble Shooting SQL Server Books online
http://technet.microsoft.com/en-us/library/ms159704.aspx
Popularity: 8% [?]
Project Professional 2003 and Project Server 2003 Service Pack 3
23 September 2007
Project Professional 2003 Service Pack 3
The new Service Pack for Project Professional is here for Project
The good news is that Project Professional 2003 can open Project Professional 2007 Files.
Project Server 2003 Service Pack 3
Project Server 2003 Service Pack 3 is now available for Download at
Issue that are fixed by project server 2003 Service pack 3
http://support.microsoft.com/kb/938796/
Jerry
Popularity: 2% [?]
Golden Glow
23 September 2007
I heard my blog doesn’t look as good as it used to so I’ll post a few pictures while you are all waiting for my next post on formatting your gantt chart.
This is the Golden Gate Bridge in fog taken on my way home from a company dinner a few weeks back.
Popularity: 1% [?]
Publishing Reporting Services reports to MOSS
21 September 2007(Many, many thanks to Heidi Steen of the super-duper UE team at Microsoft for providing the material below. Hell, she even created screen shots!)
Now that lots of folks are happily playing around with SSRS/MOSS integration, it’s important to understand exactly how you publish the things to MOSS via Business Intelligence Studio. You still use the same dialogs you’re used to, but plug different values into them. Here are some nice, step-by-step instructions:
1. In SQL Server Business Intelligence Development Studio,
open an existing or new Report Server project.
2. From the Project menu, click Properties. The <project>
Property Pages dialog box opens.
3. Choose the Configuration you use to publish to a SharePoint site.
For example, Active(Debug) or Production.
4. In the Deployment section, for the optional TargetDataSourceFolder,
type a fully qualified URL to a library or library folder. For example,
http://server01/mycustomreportingsite/Shared Documents.
If left blank, this defaults to the TargetReportFolder value.
5. For TargetReportFolder, type a fully qualified URL to a
library or library folder. For example,
http://server01/mycustomreportingsite/Shared Documents.
6. For TargetServerURL, type a URL to a SharePoint
top-level site or sub-site. If you do not specify
a site, the default top-level site is used. For
example, http://servername, http://servername/site
or http://servername/site/subsite.
7. Click OK.
8. In Solution Explorer, right-click on the report
you want to publish, and click Deploy. The report
is published to the location specified in
TargetReportFolder. Deployment errors appear in the Output window.
NOTE: In order to upload data sources and reports to MOSS, the user in question must have “Contribute” or “Full Control” permissions.
Below, I’ve attached some screenshots which demonstrate publishing to a library in a custom and default MOSS site (again, thanks to Heidi!)
NOTE
Although the blog entry provides all the details for such activity but there are some pre-requisites to do that.
- SQL Server 2005 Reporting Services – hosts Reporting Services reports and communicates with Office SharePoint Server 2007 using a Web Services interface. The Reporting Services server also manages subscriptions and report caching. This server can be separate from the Office SharePoint Server 2007, but if it is, you must also do a basic install of Office SharePoint Server 2007 on the Reporting Services server to ensure that the Windows SharePoint Services (WSS) 3.0 object model is installed.
- SQL Server 2005 Service Pack 2 – enables Office SharePoint Server 2007 and Reporting Services integration on the report server.
- Office SharePoint Server 2007 –Serves as the central access point for all reports and business data. Alternately, you can use Windows SharePoint Services 3.0.
- Microsoft SQL Server 2005 Reporting Services Add-in for Microsoft SharePoint Technologies - This feature includes the Report Viewer Web Part and the new report management user interface.
ired components to integrate Reporting Services with Office SharePoint Server 2007, both the report server and SharePoint server need to be configured. The following sections outline the configurations necessary to achieve integration.
Report Server Configuration
After installing SQL Server 2005 Service Pack 2 on the Reporting Services server, a new configuration option becomes available, called SharePoint Integration, as shown in Figure 2.
Figure 2: Configuring Report Server SharePoint Integration.
SharePoint Server Configuration
After installing the Microsoft SQL Server 2005 Reporting Services Add-in for Microsoft SharePoint Technologies feature of the Feature Pack for SQL Server 2005 Service Pack 2, a new application becomes available under the Application Management tab. This new application is shown in Figure 3.
Figure 3: Configuring the Reporting Services Application in Office SharePoint Server 2007.
To configure Reporting Services, you must set each of the options shown in Figure 4, as follows:
- Manage integration settings – To configure the Report Server Web Service URL and Authentication Mode (either Windows or other trusted account).
- Grant database access – To configure the name of the report server database server instance name.
- Set server defaults – To configure report server timeouts and other options.
Read
Microsoft SQL Server 2005 SP2 Reporting Services integration with WSS 3.0 and MOSS 2007
olute” alt=”" width=”0px” height=”0px” src=”http://c.live.com/c.gif?NC=31263&NA=1149&PI=88469&RF=&DI=3919&PS=85545&TP=yasirbutt.spaces.live.com>1=Yasirbutt”>
Popularity: 3% [?]
PSI: Filter constraints and escaping the recursive event handler
21 September 2007A couple of topics that have come up through support incidents and comments posted here. The first on the use of the filter or xmlFilter parameters available in a few of the web services, and the second talking about event handlers and what happens if you fire an event based on Check-In that then issues a check-in - how do you break the loop?
Filters
The SDK details how the xmlFilter parameter can be used to filter the returned dataset and the sample code covers the CustomFields dataset. However there are a couple of limitations that you should be aware of. You can use the PSLibrary.Filter.Fields.Add to control the columns returned in the dataset and PSLibrary.Filter.Criteria to control the rows. The criteria can only be used against the main tables of the dataset and cannot be used to filter rows in the secondary datasets. For example the Resource web service has the ResourceDataSet which contains the ResourcesDataTable as the main datatable and also several others including the ResourceAvailabilityDataTable. Only rows in the ResourcesDataTable can be filtered using criteria. You will get a ResourceFilterInvalid Exception (or CalendarFilterInvalid exception if you try to use criteria on CalendarExceptionsDataTable of the Calendar web service). This should be fairly obvious as the construction for the criteria does not allow for a specific DataTable to be referenced. The other limitation is less obvious and will be corrected in our documentation shortly. The ResourceCustomFieldsDataTable cannot be filtered at all using the filter parameter - you will get a ResourceFilterInvalid exception. In both cases you can of course use filter on the client once you have the full dataset returned. Another option would be to create your own PSIExtension that does the extra filter and keep everything server side.
Recursive Event Handlers
I addressed this question from a comment but might be useful for a full posting. So if as part of your workflow you have an event handler for check-in, and when it fires you need to update something in the project then you will also need to check-in when you have finished, which will then fire the event handler and so on. The best way I could think of to break the circle is to set a specific string as the session description when you use the check-in in your event handler. Then you can check in your code before checking out if the sessions description in the project dataset is the one for your event handler - or a user session description which will be of the format machinename\pwa_account. If it is your setting then no need to continue. If anyone has a better way then please share.
Technorati Tags: Project Server 2007
Popularity: 2% [?]
Project 2003 Service Pack 3
18 September 2007It’s now available and ready for download:
Popularity: 2% [?]
More on Using Kanban to manage your maintainence backlog
18 September 2007As I mentioned in a previous post, I've been experimenting with using the I saw David Anderson mention Kanban System to test how this would work in our organization. As mentioned earlier the paper A Kanban System for Sustaining Engineering explains This method. See my previous post for an explanation of what we are attempting.
I wanted to share a couple of issues I've encountered and how I deal with them. First, we have set up the system so that we are not accepting any more changes until the current batch are complete. The biggest plus so far has been the huge visibility to management. We can see what tasks are still to do, and we were able to determine that a certain type of task with only one developer had over half the issues. We were able to get resources to back this other resource up, which is helpful
The other issue that affects this system are what I call "emergency changes" that ensue from issues around the User Interface. For instance if you are using a technology and having problems with that technology how is that captured? Right now we're treating that not as a change, but a problem. I'd like to hear if anyone else is doing anything else with this.
Happy PMing/Coding!
Popularity: 1% [?]
Project 2003 SP3…Still Piping Hot!
18 September 2007The new SP is here for Project and here for Project Server.
Notable additions for the desktop is the ability to open Project 2007 mpp files.
Popularity: 1% [?]