Geeks With Blogs
Molnar Tibor blog SharePoint 2007

Things found during SharePoint 2007 development, a lot of workflows included.

"The required windows rights management client is present but the server refused access." message during registering Windows Rights Management Services in MOSS
When registering the Windows Rights Management Services (RMS) in Central Administration in MOSS, I received the "The required windows rights management client is present but the server refused access. IRM will not work until the server grants permission", even if I followed the 'To add SPS-SRV to the RMS Certification Pipeline' step from 'Deploying Windows Rights Management Services with Microsoft Office SharePoint Server 2007 Step-By-Step Guide'. Solution: the Central Administration web application ......

Posted On Wednesday, July 30, 2008 7:34 PM

Application setting for Sharepoint timer jobs
When a new timer job is created for Sharepoint, it has to be programatically installed in a SPWebApplication.JobDefinit... of type SPJobDefinitionCollection. If the timer job have to receive some settings during run time, one option would be to use the .Net application configuration feature. First you might think to copy the configuration section from the app.config of the dll where the timer job resides into the web.config of the web application where the timer job is registered. The first catch: ......

Posted On Wednesday, July 30, 2008 2:19 AM

Security issues installing a Sharepoint timer job from a feature receiver
I don't enter in the details of how to install a timer job. It you are interested, take a look here . After doing the coding, during the testing, I had 2 issues: During feature activation I had: 'System.Data.SqlClient.SqlE... The EXECUTE permission was denied on the object 'proc_putObject', database 'Intranet_Config', schema 'dbo''. After doing a profiling on the database, I saw that the SPJobDefinition.Update() ......

Posted On Sunday, July 27, 2008 9:48 PM

Using Windows Internal Database with Search Server Express Basic installation
WSS (Windows Sharepoint Services) 3.0 simple installation uses the Windows Internal Database (for the configuration database, contrent databases). This database doesn't have size limitation. When Search Server Express is installed without having a previous WSS 3.0 installation to extend, WSS 3.0 is installed b by default (Search Server is based on WSS 3.0) but also SQL 2005 Express is installed and the configuration and content databases will be hosted in SQL Express. There is one issue here: SQL ......

Posted On Monday, June 2, 2008 11:52 PM

Version Info Path forms when versioning workflows in MOSS
Versioning of Workflows with InfoPath forms in MOSS is not supported out of the box. How to do it is described in Dan Herzog's blog ( https://blogs.pointbridge.c... I would add a few words about how to handle the Info Path forms versioning. In the workflow.xml file the namespaces of the InfoPath forms are referenced using Task{Nr}_FormURN elements. From one version of a workflow to another not necessarily all forms will change. The forms which are not changed ......

Posted On Saturday, May 24, 2008 8:24 PM

MOSS workflows: "This task is currently locked by a running workflow and cannot be edited", what the heck?
Context In a production environment we started to receive, apparently randomly this error message. We have a complex workflow using InfoPath forms developed in Visual Studio, we applied multiple patches by regac-ing new versions of the workflow assemblies, retaining of course the fully qualified names of the assemblies. Also we use a test environment, where regression testing was done by dedicated test engineers. Shooting in the dark We found this blog ......

Posted On Saturday, March 1, 2008 2:07 AM

Funny thing in WSS 3.0: three state workflow cannot be started on docs having check-out required
I was playing around with SharePoint Services 3.0 to build a demo site for a customer. I had a document library having the 'Require documents to be checked out before they can be edited? ' set to true. When I started a workflow manually on a document, I got 'Error ocurred', form the logs: 'Unexpected Microsoft.SharePoint.SPExce... The file "abc.docx" is not checked out. You must first check out this document before making changes.'. Fine, I checked out a doc and tried to start the workflfow again. ......

Posted On Tuesday, February 19, 2008 9:36 AM

Assembly form a template conflicts with a same named assembly form another template during MOSS workflow deployment
If during the installation of a workflow feature using InfoPath forms you receive a warning message in the form 'The assembly assmbl1.dll from form template templ1.xsn(urn:....) conflicts with a same named assembly in form template templ2.xsn(urn:....). ' the reason is that one of the Info Path forms being deployed contains in the .xsn file an assembly which has the same fully qualified name as one of the already deployed assemblies. One reason could be that the assembly version property of the code ......

Posted On Monday, February 18, 2008 9:43 AM

Project Server 2007 PSI: Find out the GUID of the cuurent user
Update: g. mipa gave me a much simplier solution: PSSvcResource.Resource myRes = new PSSvcResource.Resource(); GUID currUserID = new GUID(myRes.GetCurrentUserUi... My bad. Thank you! Obsolete: Can be done by: Get the current user from using the WSS 3.0 API Build the Microsoft.Office.Project.Se... instance using the current user's name Call the ReadResources method of the Resource PSI web service PSSvcResource.ResourceDataSet resourceDs = new PSSvcResource.ResourceDataS... // Create ......

Posted On Wednesday, February 6, 2008 12:35 AM

MOSS 2007 Service Pack 1 installation adventure
We installed first time in a stressy condition the SP1 for a production server (a simple farm installation). There was an error during running a custom workflow (developed in Visual Studio 2005) attached to a custom list; we googled out that it was a MOSS bug solved by SP1, which was not installed yet. The plan was to install SP1 and restore a backup from previous midnight for the content database in order to regain the status of a workflow which crashed due to the MOSS bug mentioned above. What ......

Posted On Sunday, January 27, 2008 7:44 PM

Copyright © Molnar Tibor | Powered by: