I have weird problem with SharePoint. I've uploaded a file on a document library and everything seems to be in order. but after a few days the file doesn't work properly and when I try to download it a red label appear with cobalt exception message.
it seems your file become corrupted but it doesn't happen it normal situation.
Do you have Blob Stream configuration for your SharePoint?
Related
I am using Microsoft Syntex Content understanding on a specific Document library in Sharepoint (M365).When files are dragged into the library manually, content processing starts as expected and delivers results.
When files are added to the library with a power automate flow, the content processing does not start (not until some other files are added manually again).
Any ideas if this is a config issue?
I tried waiting (files had not been processed on the next day), checked licensing and permissions. The issue stayed, content understanding starts only when triggered by manual file upload.
We opened a case with MS Support and it started working a few days later. Case closed by Engineer without further explanation.
From our side we made sure we had the correct licensing in place, eliminated all complexity from power automate so that only plain pdfs landed in the syntex library.
Windows 8.1 and
Office 2013
If I try to open an invalid spreadsheet XML file in Excel a pop-up notification gives a brief explanation of the problem and a points to a detailed log file in the Content.MSO folder. However, when I open the detailed log file, it is empty. Earlier versions of Excel and/or Windows populated this log file with each issue encountered.
What is preventing this log file from being populated?
I'm not sure of the KB number but a fix for Office 2013 related to this issue was pushed through Windows Update around 12/12/2014. Error logging appears to be working again.
I'm getting a DirectoryNotFound exception when attempting to add my custom web part to a page. It seems pretty straight forward since it's complaining about not being able to find the "feature.xml" file for the web part. What is odd is that the Directory that is showing up in the error message is completely different from the one that the Web Part is installed in. So the file it should be looking in is \12\Template\Features\WebPart1\feature.xml but it is looking in \12\Template\Features\WebPart2\feature.xml.
Can someone explain to me how Sharepoint performs feature activation or point me to a link that is helpful?
Thanks,
Jason
--Edit more information --
I'm using WSPBuilder to create and build the Sharepoint feature. My understanding of how this should work is that WSPBuilder will copy my feature.xml file to the Sharepoint site and my .webpart to the wp folder. When I activate a feature it will look into the feature xml file and reference the .webpart file that will contain the configuration for which webpart class to load. The webpart2 folder that it is currently referencing is an old feature that I uninstalled so it must somehow be confused as far as where the feature folder is but without knowledge on how it determines where to look I'm at a bit of a loss on how to correct it. Does it save the guid in the SP database somewhere? Any information on how this feature activation process works would be helpful.
I'd vote myself down if I could... that error message had nothing to do with the problem. It was an exception that was being thrown but being caught in Sharepoint.
I've spent several hours trying to figure this out; hopefully, it's an easy solution and the difficulty is simply because I'm brand new to Orchard CMS and no where near an expert web developer...
I've created a Products Download page and need to insert hyperlinks to files that exist on the file system.
the path to the file (on disk) is : c:\Orchard CMS\Downloads\ProductOne\File1.zip
in the page editor, I insert a hyperlink reference with the following URL: /Downloads/ProductOne/File1.zip
When I hover over the hyperlink, it looks correct: http://localhost:12345/Downloads/ProductOne/File1.zip
However, when I click the link, I receive the following exception:
HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable. Please review the following URL and make sure that it is spelled correctly.
Any help would be extremely appreciated!
If you don't want to play with source code and web.config files you should use Orchard Media feature. It allows you to upload files into Orchard filesystem and manage those. Links to files uploaded this way look like http://www.myorchardsite.com/Media/[Media folder path]/YourFile.zip
If you are not an experienced developer, I'd strongly advise you to take this approach. The only drawback is that you'd have to reupload those files into Orchard. But this is not as bad as it looks - you can zip them and upload as a single file (Orchard will take care of unpacking the archive if you check the checkbox below upload field).
You need a web.config file that allows the files to be served. You can use one from one of the content directories that can be found in modules or themes.
one of our customers has great problems checking in documents to a SharePoint library form Word 2007. Whenever she check's in a document to the library the meta data as version number and checkin comment are updated but not the document itself.
The library is configured in such a way that versioning is activated and documents have to be checked out before editing.
I think it has to do with some Office 2007 or OS settings as every other of her colleges can check in documents without any problems.
I recently ran into a similar issue. The document may be getting uploaded but some sort of caching or proxy issue is causing an older version to appear when you try to download it.
To isolate the issue I suggest you try uploading a text file a couple of times.
Not sure if you'll have access to the component that is actually causing the problem, but as a workaround renaming the file should help.