Hallo NG, habe das Problem in meiner Testumgebung das keine automatischen Kontakte im AD angelegt werden trotz Durcharbeitung mehrer Anleitungen. In unserem Produktivnetz mit Exchg 2003 funktioniert es. Testumgebung: v-dev-DC1 -> W2k3 Ent. x32, DC,DNS,CA v-dev-Exchg1 -> W2k3 Ent. x64, Exhchg 2007 v-dev-Apps1 -> W2k3 Ent. x32, SqlServer 2005, MOSS 2007 (alle updates) Habe mal die Protokollierung
Hier die genaue Fehlermeldung: Sicherheitsausnahme Beschreibung: Die Anwendung hat versucht, einen Vorgang auszuführen, der von der Sicherheitsrichtlinie nicht zugelassen ist. Um der Anwendung die erforderliche Berechtigung zu erteilen, wenden Sie sich an den Systemadministrator oder ändern Sie die Vertrauensebene für die Anwendung in der Konfigurationsdatei. Ausnahmedetails: System
In my CLM enviroment, I am able to hit the site go to manage my information, request new set of certificates, select the profile, Enrollment Request Initiation, then: There is no such object on the server. Technical Details Type: System.DirectoryServices.DirectoryServicesCOMException Source: System.DirectoryServices Stack Trace: at System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail
When I exported a working and not working entity I found a difference in the InvariantName's of the options at the entities StateCode. I have found an issue about this field: http://support.microsoft.com/kb/923258 It seems a roll up killed the bug in 3.0 (by supporting the differences?), but they have recreated the bug in the 4.0 version. The rollup doesn't seem to fix old problems
During the hunt for a dispose warning in my code, I changed som logging settings in Central Admin. I was given a warning about a non-disposed object for microsoft code. Following is the stack trace: An SPRequest object was not disposed before the end of this thread. To avoid wasting system resources, dispose of this object or its parent (such as an SPSite or SPWeb) as soon as you are
