I've been seeing this issue with a few of my users ever since disabling SharePoint Drafts. When trying to open a file, specifically an Excel spreadsheet, they'd get a message that the File Conversion in Process and then another that the Converter Failed to Save File. The strange thing is they weren't trying to covert anything or even to open it in Office Web Apps. If they open the file in Read Only mode the file opens fine and then they can click on the Edit Worksheet button and it works fine. But if they click on the drop-down context menu to Edit in Office Excel or if they click on it and choose the Edit radio button, they get this message.
After much searching and seeing posts to make sure this was installed or reinstall that or change this or modify that - all with no success. I ran across a blog post that was so simple and it actually worked. Much thanks to Amol Ghuge's post for saving the day!
- Empty the user's temp folder at %userprofile%\Local Settings\Temp\
- Open Word (or Excel)
- Click the Office button
- Click Word Options (or Excel Options)
- Click Resources
- Click the Diagnose button
- Click through the wizard until it is finished
- Reboot
When you create a new Enterprise Business Intelligence site in SharePoint 2010 and enable PerformancePoint site collection & site features, there is something that is unfortunately missing by default - a Dashboard Library. Where this becomes evident is when you are trying to deploy your first dashboard.
So, you've created your first dashboard and you're all excited to see it in action and see what the new PerformancePoint Services 2010 are really capable of. You right-click on your dashboard in Dashboard Designer and click Deploy to SharePoint. Then the Deploy To box pops us and.....it's empty. Did we do something wrong? Did we miss something? Is it waiting to populate with something? It turns out that the Deploy To box is filtering the list of available libraries in your site that you can deploy your newly made dashboard to. And, since none are created by default and you didn't create one beforehand, nothing shows up in the box.
How do we fix this? Easy! Go back to your site and click:
- Site Actions
- More Options
- Library
- Dashboards Library
Enter a name for your new library and click Create. Now, go back to Dashboard Designer and try to deploy your dashboard. Once the Deploy To box pops up, you'll see your newly created Dashboard Library that you can deploy your dashboard to.
Posted on :
11:38 PM
| By :
Mike Laurencelle
Today I ran into an odd problem when trying to publish an InfoPath form to a site collection in MOSS 2007. When publishing the form, I got a fairly nondescript error that told me to check the logs for more info. Well, off to the logs I go where I am surprised to see "Activation could not be completed because the InfoPath Forms Services support feature is not present."
Huh? How is InfoPath not present? All my other forms are working just fine. No problems anywhere else I can see. And it's not like InfoPath is like Excel Services or Project Server that I can just disable/enable in Services on Server in CA. Well, after some looking around on my favorite search engine, I found a great post by bphillips76 that said they were able to resolve the problem by simply deactivating and reactivating the "Office SharePoint Server Enterprise" features at both the site collection and the site level.
So, having exhausted all other options I could come up with on my own, I decided to give this simple trick a try and was plesantly surprised to see it worked. Moments later, I was able to activate my form and I was back in business.
Thanks for the tip, bphillips76!
http://bphillips76.spaces.live.com/blog/cns!F9B548E4C21D6166!371.entry
I recently completed a deployment of Office Communications Server 2007 R2 and in my search for many technical articles, I stumbled across the ability to create custom presence in Office Communicator 2007 R2. (Microsoft TechNet article here) Obviously, for most people, myself included, there isn't a real business need for this so I kind of tucked it away in my "This would be kinda cool to try out some day" pile.
Well, eventually I was looking for a distraction and turned to the pile, finding this little nugget and gave it a try....to no avail. It didn't work! Oh well, stick it back in the pile.... I revisited this occasionally here and there over the next couple months, never able to get it working, never caring about it enough to invest any real amount of time in it. Well, tonight I ran across this article while looking up some security information for OCS that answered why this wasn't working.
In OCS 2007 R2, High Security SIP is enabled by default. (awesome!) so, it expects all transmissions to be secure. Well, had tried having the presence.xml file out on a network share, on my local hard drive, and in a SharePoint document library. None of which are considered secure transmissions. However, just slap an 's' at the end of the http for my SharePoint document library and voila! My custom presence works!
So, moral of the story is, if you want to use custom presence in OCS 2007 R2 and you haven't disabled secure SIP (and hopefully you haven't....) then you have to store the file in an https enabled location. So, something like, https://server.domain.com/folder/presence.xml
Now, I wonder how long it will take before someone notices that my presence is "out of my mind, be back later"...
I was running into this problem sometimes when doing a P2V conversion in Hyper-V. The conversion would get to exactly 40% and fail. Every time. Well, after a little searching around, it turned out to be a common problem with the VSS writer on the source machine that is getting converted. Thankfully, the fix is simple and doesn't even require a reboot.
Error (13243)
The snapshot creation failed because the VSS writer {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f} on source machine MACHINENAME did not respond within the expeted time interval.
(Internal error code: 0x809933BB)
Recommended Action:
Ensure that VSS writer is functioning properly and then try the operation again. 4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f is the Shadow Copy Optimization Writer
You may also see an event ID 8193 in the Application Event Log on the source machine.
The Fix:
- Open regedit and go to HKLM\Software\Microsoft\Windows NT\CurrentVersion\ProfileList
- Under the ProfileList key, delete any subkey that has ".bak" on the end.
Done! You can now complete your P2V conversion.
0