• SP 2010: How to redirect InfoPath form to a custom Thank You page

    Posted over 2 years ago
    by DHX}

    Problem: Although Info path gives you the ability to create a custom message after submission, lots of users have requested more than that. They haven’t been happy with the way the form just leaves you sitting there in the List, it can be confusing. So we have a way in which you can make an InfoPath form function like a traditional web form wherein you fill out the form and upon clicking the ‘Submit’ button, the user is taken to a Thank You page

    Resolution:

    1. Create a Thank You page and save it somewhere on your site. We recommend using any editor, like Notepad or SharePoint Designer to create an html page with a message of your choosing such as “Thank You for your submission”

    2. Click on that Thank You page and record the URL I.E., it will look something like this: http://mydomain.com/sites/YourSite/YourDocLibrary/ThankYou.html

    3. Now you need to figure out the URL to your InfoPath form. Either click on it and record the URL or if you have attached the InfoPath form to a SharePoint List, then you will need to alter the URL like this: http://mydomain.com/sites/YourSite/YourList/NewForm.aspx, as you can see we just added the NewForm.aspx to the end of it.

    4. Take the URL you recorded in step 3 and add the following: ?Source=http://mydomain.com/sites/YourSite/YourDocLibrary/ThankYou.html, So the URL should look like this: http://mydomain.com/sites/YourSite/YourList/NewForm.aspx?Source=http://mydomain.com/sites/YourSite/YourDocLibrary/ThankYou.html << this is the link you will send to your users in order to fill out your form. When your users click on this new link, it will tell SharePoint to automatically redirect them to your Thank You page after they submit.

    On that Thank you page you can add a link to go to another page or you can get real fancy and add a Meta refresh tag to automatically take redirect your users, for example, to the home page of your site. How do you do that? Simple. Add this line: <meta http-equiv="refresh" content="2;url=http://mydomain.com/sites/yourSite/"> in between the <head></head> tags of your HTML page. Just to explain a little more about that line, the number 2 in this case represents 2 seconds. So you can modify that to keep the user on that page longer or shorter by replacing that number with a different one. The url would be the url of your home page or any other site you want to redirect the user to.

    Fight Comparison:

    Tyson vs. Spinks…this one was easy.

  • MOSS 2007: An update conflict has occurred, and you must re-try this action. The Object SPWebApplication….SPUpdatedConcurrencyException

    Posted over 2 years ago
    by DHX}

    Problem: User could not create a new web application in MOSS 2007. When creating user would receive the following error in both their test and production environments:

    The following was found in the ULS logs:

    Microsoft.SharePoint.Administration.SPUpdatedConcurrencyException: An update conflict has occurred, and you must re-try this action. The object SPWebApplication Name=MyServer.net was updated by domain\account, in the w3wp (7936) process, on machine MACHINE_NAME.  View the tracing log for more information about the conflict.  
    at Microsoft.SharePoint.Administration.SPConfigurationDatabase.StoreObject(SPPersistedObject obj, Boolean storeClassIfNecessary, Boolean ensure)   at Microsoft.SharePoint.Administration.SPConfigurationDatabase.Microsoft.SharePoint.Administration.ISPPersistedStoreProvider.PutObject(SPPersistedObject persistedObject, Boolean ensure)   

    Resolution:

    Researched and talked to some colleagues about a similar error to: SPUpdatedConcurrencyException: An update conflict has occurred, and you must re-try this action. They mentioned finding a similar error in the Event logs and problem was something to do with a 3rd party workflow causing a conflict upon creation of the Web Application. I had the user do the following:

    · Reproduce the problem in a test environment

    · Record the time of the error

    · Look for the error in the Events log around the same time as the reproduced error: SPUpdatedConcurrencyException: An update conflict has occurred, and you must re-try this action

    · There should be a feature/solution listed that is probably the culprit

    · User retracted suspect solution

    · Successfully created a web app

    Fight Comparison:

    Tyson vs. Douglas. I was terrified, first few months on the job, had never seen this error before AND it was going to possibly delay the user’s go live date. Not being able to create a new web application is pretty limiting to say the least. Douglas must have been terrified too, facing the baddest man on the planet, the seemingly invincible Mike Tyson. But he persevered, almost got knocked out and pulled through in the end.

  • SP 2010: List does not exist

    Posted over 2 years ago
    by DHX}

    Problem: When a Site Owner tries to access ‘Manage Content and Structure’ link they receive the following error:

    image

    Resolution:

    Although there are probably many causes for this error, we fixed it by enabling Publishing Features on this site

    Fight Comparison:
    Rahman vs Lewis I, lucky knockout for Rahman, just like I got lucky on this one, I was hoping turning on these features would work and it did, lights out.

  • MOSS 2007: User cannot check-in or check-out documents. Receive ‘Cannot perform this operation. The file is no longer checked out or has been deleted.’

    Posted over 2 years ago
    by DHX}

    Problem: When checking in a document user receives the following error and is not able to check-in the document:
    1

    Additional details:

    · Farms in separate domains.

    · Able to authenticate to and view sites but we cannot open sites using SharePoint Designer.

    · Prompted for authentication and are shown the initial site structure but when we click open, it throws several errors.

    · Can duplicate this problem on multiple workstations.

    · They are connecting to SharePoint via an IP address with port number

    · Also happens when working on SP Designer on the actual Sharepoint server

    · Customer able to browse to the problem list identified in the Fiddler output either by hitting the URL or by IP Address and port number in IE

    · The one that works is in the same domain

    · Test servers for Document center are Cross domain

    · User is able to check in same exact files through the browser GUI just fine

    · Web App is claims based authentication

    · Customer was able to reproduce the error on an additional test farm with the exact AAM settings as the other test farm and in production

    · If using FQDN in SPD, it prompts for authentication over and over again on author.dll…401 Challenge on proxy level, not applying URL rewrite does not even go to SharePoint

    Resolution: Remove WEBDAV Publishing component from IIS 7.0 Windows 2008 R2.

    The WEBDAV component has also been known to cause the following issues

    · Office Clients not uploading/saving to SharePoint Sites.

    · Explorer View not working on Document Libraries and Lists (Saw this while troubleshooting during live meeting)

    · Using UNC paths to access SharePoint lists or libraries does not work.

    · Syncing with OneNote to SharePoint Libraries does not work.

    · Office Documents opening in Read only mode.

    · The following KB articles covers a few of the above listed issues

    http://support.microsoft.com/kb/2018958

    http://support.microsoft.com/kb/2171959/

    The reason is that SharePoint has it’s own WebDAV and the IIS7 WebDAV publishing interferes with it. Unless the WebDAV publishing Role has been added to the Server for a specific reason, SharePoint should not need it. Note that removing WebDAV does require the server to be rebooted afterwards.  If you do a network trace between the client and the SharePoint server you will most likely see 405 events coming back when Office fails to save the documents to the SharePoint site.

    Fight Comparison:
    Definitely a team effort, I was scratching my head on this one. I’d have to say Leonard vs. Hearns I. Once Leonard figured out the Hitman’s game, he took him out in the 14th.

  • SP 2010: User cannot import spreadsheet or export list to spreadsheet

    Posted over 2 years ago
    by DHX}

    Problem: Site owner receives the following error when trying to use the ‘Import Spreadsheet’ option to create a list from Excel within SharePoint. Same error when trying to export existing list to Excel.

    Resolution:
    Note: although this worked in this specific scenario, it may not work in others. There are a lot of variables that I did not have time to drill down into, but lucky for me, the issue was resolve

    - Verified user was using Excel 2010 32bit

    - User was on a 64-bit machine

    - Had the user download and install 2007 Office Data Connectivity Components: http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=23734

    - Problem was still happening

    - Had the user to an Office Detect & Repair and that solved the problem

    Fight Comparison:

    Morales Vs. Barrera III, both got the best of each other, but Barrera finally figured him out and turned it up in the last round.