Bei mir endete dieses Uninstall sehr früh, aber auch ohne Fehlermeldung. Repair half nicht. Geholfen hat aber, im IIS alle SharePoint-Sites zu löschen, alle Application Pools zu löschen und auch im SQL Server alle SharePoint Datenbanken zu droppen. Jetzt läuft das Uninstall und ist auch schon fast durch.

Ursache ist wohl, dass das Entwicklungsimage, auf dem ich arbeite, durch Kopieren und Umbenennen entstanden ist, denn die alten App-Pools liefen auf ALTERRECHNER\Administrator, was dann wohl auch zu der IdentityNotMappedException führte, welche ich im Eventlog gesehen habe.

---
Unterstütze mich und meinen Blog und kauf dir was Nettes (über diesen Link)

In case the link “Create or extend Web application” is missing in your SharePoint Management Portal, you should try to run your IE as Administrator. This worked for me. (Also make sure, your page is in the local intranet zone!)

---
Unterstütze mich und meinen Blog und kauf dir was Nettes (über diesen Link)

Consider a two-step approval process for your travelling expenses as shown in the following figure:

It is worth noting, that you need to ask the right manager for approval in the first step but that everyone from the HR department should be able to approve the second step.

To implement this workflow using K2 you could use the Visio-integrated designer or the designer inside Visual Studio. I decided to use the Visual Studio Designer because it is more powerful and you can draw connection easier.

So you start the K2 Designer for Visual Studio and start modeling the process. In case you know what you are doing, you may come up with something equally to the following:

The workflow is bound to a Sharepoint library and starts automatically if someone submits a new form to this library. The manager is determined depending on the user who submitted the form. The manager gets a notification via e-mail about the new workflow instance or he will see his task if he checks his Sharepoint task list or his K2 Workspace page. He can open the InfoPath-form, add comments and decide whether he want to accept or reject it. In case of a rejection the originator of the request gets notified and has now the possibility to adjust his form.

In case the manager agreed with the form it is routed to everyone in the HR group. The first HR group member opening the task has again the possibility to add a comment and to choose between accept and reject.

After the approval of a HR coworker the originator and his manager are informed via e-mail about the final approval and the form is saved inside a Sharepoint library for further processing.

K2 allows you to draw the complete workflow in a matter of minutes and its flexibility allows for other additions such as “auto-approve request below xx €” or “enrich the form with the last requests from this employee for the manager/HR view”. The visual representation of the workflow is easily readable which is good for the client, for the documentation and for the needed development time as well.

---
Unterstütze mich und meinen Blog und kauf dir was Nettes (über diesen Link)

"The evaluation version of Microsoft Office SharePoint Server 2007 for this server has expired."

But it should work at least until April 2009! (source, source’s source).

It looks like the error message is wrong. Basically it tries to tell you that the used identity for the application pool should be in the administrators group. Isn’t that obvious???

---
Unterstütze mich und meinen Blog und kauf dir was Nettes (über diesen Link)

The used feature is called Business Data Catalog (=BDC) and is basically a huge XML-file which describes how SharePoint should connect to the external application and how these data entities are associated.

The first action should be the installation of the BDC Definition Editor. If you have the SharePoint SDK installed on your machine, point your explorer at "%programfiles%\2007 Office System Developer Resources\Tools\BDC Definition Editor" and open Setup.exe. For a successful installation you need to run an English Version of Win XP or Server 2003.

At first you need to select "Add LOB System" and provide your webservice Url or your Database credentials. Then you can select the Webservice method or provide sql queries to fetch the data. The editor generates the needed entities for you but you need to create the identifiers and filters on your own.

For basic functionality you need to provide a finder method, which returns a collection of entities. The method can have parameters to filter the results. The second method has to be a specific finder which returns only a single entity based on a given identifier.

This is enough for a basic setup – the next step is to export your configuration into an XML-file. Now you need to import this definition into your SharePoint Server: Open your central administration page, select your SharedServices and select "Import application definition" under the "Business Data Catalog"-section. Follow the dialog!

If you did everything right, you can now add a business data list webpart to a SharePoint page. Choose your created type in the web part options and you have successfully created your own Business Data Catalog Application!

For further information on this topic, I suggest you these links:

• The blogpost series from Sahil Malik
• Business Data Catalog in MOSS 2007
• BDC MetaMan (Better tool but expensive)

---
Unterstütze mich und meinen Blog und kauf dir was Nettes (über diesen Link)