Comments for Nerfed Tech

Comment on stsadm -o import results in a error by Folly

Folly — Tue, 14 Oct 2008 20:25:29 +0000

Hi,

It’s not really doing it again, but rather, granting the person running the imports and exports the correct rights.

I can not definitively off the top of my head tell you exactly the rights you need, but I would start with at least site collection admin for the identity running the stsadm commands for both the source and destination site collections.

If thats not enough, you may need actual DB rights, which could be a problem with your DBAs. In that case, grant them site collection rights, local admin rights, and let them run the command.

A couple hundred stsadm commands later and they may reconsider their policy on DB access for SharePoint admins.

Comment on DCOM Errors by Malcolm Gin’s SharePoint and .NET Tips » Blog Archive » DCOM 10016 errors

Tue, 14 Oct 2008 18:52:14 +0000

[...] is something an old colleague and I found out in October of last year, found on a blog entry from Søren Nielsen from April of last [...]

Comment on stsadm -o import results in a error by Tray Harrison

Tray Harrison — Mon, 13 Oct 2008 19:56:27 +0000

Hey, I just came across this post as I’m investigating a failed SharePoint migration that we attempted this weekend. We are trying both imports and exports using stsadm. The exports went just fine, but when we attempted to import, every single site generated the Error: Access is denied. (Exception from HRESULT: 0×80070005 (E_ACCESSDENIED)). What I attempted to do was recreate the site collection and the re-import, but I continued to receive the same ACCESSDENIED error. Are you saying that I need to try both the export and import again? As I said, the exports appeared to go through without error. Thanks for any assistance you can provide.

Comment on The document could not be opened for editing. by Folly

Folly — Wed, 08 Oct 2008 14:40:48 +0000

As far as I know, I havent seen a fix. I believe the problem exists in the Office Client software. I have patched them to the latest update, and still see the problem.

/shrug

Comment on The document could not be opened for editing. by Angel

Angel — Wed, 08 Oct 2008 00:29:57 +0000

I have the same problem with Office 2007 and MOSS 2007 with long URLs.
Any idea if this has been fixed?

Comment on The document could not be opened for editing. by Michael Griffin

Michael Griffin — Mon, 07 Apr 2008 18:46:53 +0000

Yup, same problem on my side. Once the file was renamed it fixed the problem. No special characters were in the file name just spaces and letters. Do you know if this has been fixed or will be fixed by Microsoft in SharePoint?

Comment on sysfader.exe is freaking evil… by Folly

Folly — Wed, 22 Aug 2007 20:19:30 +0000

Reposting a comment that offers an additional solution if that one doesnt work..

Anonymous said…

Sorry, but that method doesn’t really work, I’m still having less then 10 crashes in 8 hours of IE7 use. My system’s “Visual Effects” were already off and I’m running Win XP Pro with SP2.

However, I fixed the problem and am obliged to share it with all who have the same problem (if all else fails with the above mentioned troubleshoot), but it requires a little bit of your technical knowledge:

Go to: START >> CONTROL PANEL >> INTERNET OPTIONS.
On the Internet Options (Internet Properties), click on the PROGRAMS tab and click the MANAGE ADD-ONS button near the bottom (I’m on Internet Explorer 7).

I don’t know which add-on I disabled/removed that made the problem go away, but it was something to do with third-party add-ons. Disable any add-ons you think you don’t recognise, or don’t need/use those add-ons on IE7 browser. Leave Microsoft’s Add-ons enabled, unless necessary to disable.

It is possible that there were add-ons clashing with others, thus causing SysFader.exe error, I have some add-ons removed as they were not a proper files (not same icons), or were cookies that were not deleted when you scanned for spyware/adware. It’s been 2 days since I disabled/removed those IE add-ons, no crash so far.

Hope this method works for you, if not, I do hope Microsoft will rectify this problem for you soon.

Regards,
Dominic Marshall