The Breakdown https://docs.microsoft.com/archive/blogs/cjjohn/feed.xml CJ [MSFT] Wed, 17 Apr 2019 03:39:49 GMT en-US hourly 1 File is invalid. It may refer to a nonexistent file or folder, or refer to a valid file or folder that is not the current Web. https://docs.microsoft.com/archive/blogs/cjjohn/file-is-invalid-it-may-refer-to-a-nonexistent-file-or-folder-or-refer-to-a-valid-file-or-folder-that-is-not-the-current-web Thu, 08 Sep 2016 12:54:08 GMT https://blogs.msdn.microsoft.com/cjjohn/?p=605 I received the above error when I attempting to upload files to the Site Assets document library in my SharePoint 2013 site collection. My customer wanted to upload some files from another project into this folder. I thought, "This should be easy". And then this happened... I first noticed this after I was able to copy a full folder of files but once I refreshed the folder, all of the files were no longer present. The document library was completely empty as if I had never uploaded anything. The size of the file didn't seem to matter. I decided to filter on errors while uploading the files to see what my SharePoint ULS logs had to say. It appears my database is full. The Breakdown: If you are not able to upload files to a document library and receive the error that "It may refer to a nonexistent file or folder, or refer to a valid file or folder that is not in the web". You may also see the files that you upload disappear regardless the size of the file. We should check the SharePoint ULS logs to determine if our database is full. We should then check the disk space on the SQL server and clear the SQL log files. ]]> Adding a banner to your site collection https://docs.microsoft.com/archive/blogs/cjjohn/adding-a-banner-to-your-site-collection Wed, 31 Aug 2016 14:18:15 GMT https://blogs.msdn.microsoft.com/cjjohn/?p=555 Today on, "This should be really easy but it's really not!!!But it really is". We are attempting to add a banner image to the far left hand corner of site collection in SharePoint 2013. Now it's fairly easy to change the title of your SharePoint 2013 site collection using the below PowerShell command:
Add-PSSnapin Microsoft.SharePoint.PowerShell #Get your site $webapp = Get-SPWebApplication "https://myservernamehere" #Add Text $webapp.SuiteBarBrandingElementHtml = '<div class="ms-core-brandingText">What's Our New Site Title</div>' #Update Site $webapp.Update()
It's also very easy to change the site logo using the below PowerShell command:
Add-PSSnapin Microsoft.SharePoint.PowerShell #Get your site $webapp = Get-SPWebApplication "https://myservernamehere" #Add Logo $webapp.SuiteBarBrandingElementHtml = '<div class="ms-core-brandingText"><a href="https://myservernamehere"><img src="/SiteCollectionImages/logo.png" /></a></div>' #Update Site $webapp.Update()
After doing a little research, I have found that it's just as easy to add that left banner to the site collection using the below PowerShell command:
Add-PSSnapin Microsoft.SharePoint.PowerShell #Get your site $webapp = Get-SPWebApplication "https://myservernamehere" #Add Banner $webapp.SuiteBarBrandingElementHtml = '<div class="ms-verticalAlignMiddle"><a href="https://myservernamehere"><img src="/SiteCollectionImages/banner.png" /></a></div>' #Update Site $webapp.Update()
The Breakdown: To align a banner or graphic to the far left (with no spacing), we need use the ms-verticalAlignMiddle div class.  ]]> Waatah…Enter The Script Editor. Hiding the Page Title in SharePoint 2013 using the SEWP (Script Editor Web Part) https://docs.microsoft.com/archive/blogs/cjjohn/375 Mon, 25 Jul 2016 10:19:40 GMT https://blogs.msdn.microsoft.com/cjjohn/?p=375 One of my customers asked me if there is a way to remove some of the items that exist by default on a SharePoint Team site. Now as you may know, digging through any type of code can be like Bruce Lee fighting his way up the levels of the temple in the movie the Game of Death. Enter the Script Editor Web Part, document.getElementById() and Internet Explorer Developer Tools (F12).

What is document.getElementById()?

document.getElementById() returns a reference to the element by its ID. The ID is a string that can be used to identify the element; it can be provided using the id attribute from HTML id or script.

What is the Script Editor Web Part?

The Script Editor Web Part is a SharePoint 2013 out of the box webpart, that allows users to add scripts directly to the page without the need to edit the HTML or aspx files directly.

First, we need to find the where the title is located in the source code.

  • Open Internet Explorer.
  • Click F12 button on your keyboard to bring up Internet Explorers Developer Tools.
  • Click the Select Element (Ctrl+B)
  • Now let's click on the Title we want to remove.
  • We now see that the title "Root Site" is associated with the span id DeltaPlaceHolderPageTitleInTitleArea
  • We can then test by adding display:none in the Inline style.
  • We will also see that the Inline style has been added to the span id DeltaPlaceHolderPageTitleInTitleArea
  • And now our Title has been removed.
    From the above test, we have found the DeltaPlaceHolderPageTitleinTitleArea is the area we want to remove. We also found that adding the inline style display:none removes the title. Now let's remove the title permanently using the Script Editor Web Part.
  • From the SharePoint 2013 page. Click Page>Edit
  • Click Insert>Web Parts
  • Click Media and Content>Click Script Editor>Click Add
  • Click the drop down arrow to the far right inside of the Script Editor box>Click Edit Web Part
  • Click EDIT SNIPPET
  • And then paste in
<script type="text/javascript"> document.getElementById('DeltaPlaceHolderPageTitleInTitleArea').style.display = 'none'; </script>
  • Click Insert after pasting in the above script.
  • Click Apply and Ok
  • Click Save
  • Now the Title is gone for good.
The Break Down: In the first section, I explain how to grab the document.getElementById() using the Internet Explorer Developers Tools. In the second section, I explain now to add the Script Editor Web Part to a page and add the necessary script to remove HTML parts by their ID. Using the SharePoint 2013 Script Editor Web Part and document.getElementById(), I am able to remove all aspects of a SharePoint site as long as I can find the ID. Note: I have also removed the search bar in the upper right corner using the same method. Before: After: I was able to stack the script in the Script Editor Web Part right below the script I used to remove the title. To remove the search bar, I used this ID "ct100_PlaceHolderSearchArea_SmallSearchInputBox_csr_sboxdiv"]]> Something Went Wrong with my site collection!??! FIPS, SharePoint 2013 and Windows 2012R2 https://docs.microsoft.com/archive/blogs/cjjohn/something-went-wrong-with-sharepoint-2013-and-windows-2012r2 Thu, 14 Jul 2016 21:01:58 GMT https://blogs.msdn.microsoft.com/cjjohn/?p=145 Have you ever worked on a secure environment? Have you ever worked with an image that has STIG requirements? In a few cases, I have run into instances where things just aren't working in SharePoint the way I am use to them working with an out of the box install. I have found that the images that I work on have been locked down pretty tight. For example, some are locked down so tight, you can't even change the background image on the desktop without Administrator's rights. Since, I have bumped my head on this issue a few times, I figured I'd give you the break down on it. So…

What is FIPS?

FIPS is the Federal Information Processing Standard created by the United States Federal Government for hardware, software and devices. This standard is a cryptographic module inside a security system created to protect the confidentially and integrity of information within that module. Federal agencies and departments can validate that the module in use is covered by the FIPS 140-1 or FIPS 140-2 certification. FIPS being in enabled, in most cases, is a Security Technical Implementation Guide (STIG) requirement.

What is a STIG?

A STIG is a Security Technical Implementation Guide is a cybersecurity method to standardize security protocols with a network, servers, computers, and logical design to enhance security.

The Issue:

When attempting to create a new site collection in SharePoint 2013, you may receive the error "Sorry, something went wrong".

Things that I notice:

  1. The Central Administration site was running perfectly fine.
  2. Event ID 8306 indicating failed Claims Authentication in the Event Viewer.
  3. In the SharePoint 2013, these errors are synonymous with not being able to access the new created site collection and the above Claims Authentication error:

This appears to be most commonly caused by the FIPS (Federal Information Processing Standard) algorithm being enabled on a Windows operating system.

Disable the FIPS Local System Policy:

System Cryptography: Use FIPS complaint algorithms for encryption, hashing and signing.

  1. Click Administrative Tools > Local Security Policy.
  2. Click and expand Local Policies> Click Security Options > Click System Cryptograph: Use FIPS complaint algorithms for encryption, hashing and signing.
  3. Click Disable > Click Ok
  4. Restart the affected application. Close and reopen Internet Explorer.
        Alternative Method 1 to Disable FIPS via Registry:

HKLM\System\CurrentControlSet\Control\Lsa\FIPSAlgorithmPolicy set Enabled to 0

Alternative Method 2 to Disable FIPS via ASPNET.config:

  1. Edit the following files:
    C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Aspnet.config C:\Windows\Microsoft.NET\Framework64\v2.0.50727\Aspnet.config
  2. Then add the following line:
    <enforceFIPSPolicy enabled="false"/>.

For more information about how FIPS affects the Windows operating system:

https://technet.microsoft.com/en-us/library/cc263215(v=office.14).aspx

The Break Down:

In a nutshell, FIPS being enabled prevents users from accessing a newly created site collection and needs to be disabled to do so. The main reason that we see the above error is that SharePoint uses MD5, an encryption algorithm that doesn't comply with FIPS 140-2 certification.

]]>