Quest Security Explorer for SharePoint – Invalid Pointer
I found a bug today in the Quest Security Explorer 7.0.0 for SharePoint 2007. If you create a document library with a forward slash in the name, the application will prompt for a logon and after several unsuccessful tries, it will return a message box stating “Error: Invalid Pointer.” At this point, you will need to click on the root site and hit F5 to refresh the perms.
You will also have difficulty if you attempt to backup permissions of any site that has a document library, or probably any securable object, that has a forward slash in the path. The backup will proceed normally until it hits the errent object. It will then ask you for authentication and finally give up the ghost with the error:
“[-2146233088] Exception of type ‘ScriptLogic.Common.SharePointAccess.Node
+AuthenticationException’ was thrown.”
So, if you use the Quest product for permissions management, don’t create document libraries that contain a forward slash “/” with names like “My Docs/Under Review.”
I’m going to open a tickect with Quest / ScriptLogic later this week. I’ll post any additional info I receive from them.
UPDATE:
Apparently Quest is aware of this issue and they have created a tech note in their support database. Their workaround is to remove all forward slashes from document libraries and lists. However, if you really want to use the forward slash in your system, it is possible to continue to use the forward slash in your navigation links.
- Create your document library using a forward slash.
- Navigate to your document library and open your library’s settings page.
- Select “Title, Description and Navigation.”
- Remove the forward slash from the “Name” field and save.
- Open your “Site Settings” page and select “Navigation” under the “Look and Feel” section.
- Find your site link and add the slash back into the “Title” field.
- Click “OK” and close the “Navigation” page.
Your document library link will now contain the forward slash as before and Security Explorer will be able to parse the object properly.
No comments
No comments yet. Be the first.
Leave a reply


