8. June 2010 14:29
When using a new product a day never goes by when you don’t learn something new and today was no exception. I’ve been working on 3 new forms and today I was making tweaks to a couple of the forms and after publishing one of them I ran into the below errors when trying to submit a new form to a form library. The error messages that I was receiving were really vague to for the actual problem.
InfoPath cannot submit the form.
An error occurred while the form was being submitted.
The form cannot be submitted to the following location: form library url
The site may be offline, read-only, or otherwise unavailable.
The thread is already in background processing mode.
Naturally after getting the error the troubleshooting hat went on and I started searching the internet for a solution but unfortunately couldn’t find one. Then reviewed the changes that were made before it broke and couldn’t find anything wrong. Started to look at the error messages again and when I scrolled over to the right to view full URL a light bulb turned on because I noticed something that a previous client had a problem with. My filename ended with a . (period) and that’s a big no no with InfoPath forms. The naming convention for the filename is “event name - company name” and for this instance the company name ended with a period. Once I removed the period from the end of company name everything worked like a charm.
For my client we had to use a rule to search the filename for illegal characters before the form was submitted and replacing them with a _ (underscore) or just removing it all together. The approach was used because we couldn’t rely on the users to remember not to add illegal characters to the end of the filename.
Until next time.
8. June 2010 02:10
When using InfoPath 2010 I’ve always found myself coming back to the “File” tab to do something and each time I come back I’m finding new things to talk about. In my last post I mentioned the “Design Checker” section being tinted in red when the form had a error.
Today when editing an existing form to fix a layout issue I noticed that the “Publish your form” and “Design Checker” sections were tinted in a yellowish color advising me that my current changes weren’t published and form status was “Not checked”.
When creating a new form the “Submit Options” was a yellowish color because a submit option hadn’t been specified yet. I’m finding out that InfoPath 2010 is a lot more informative when something is wrong or not everything has been wired correctly.
There is just so many cool simple little features in InfoPath 2010 that has made my life easier and make me want to share it with others. This year is now starting to shape up to be a good one. Now all I need to do is find some InfoPath 2010 projects besides my own to push my knowledge of InfoPath 2010 and SharePoint 2010.
6. June 2010 14:54
The InfoPath Design Checker isn’t new but it’s now located in a different area and I discovered some unexpected functionality. Let’s first talk about the new location and then will get to the unexpected functionality.
When building one of my new InfoPath forms for SharePoint Saturday I accidently created it as a browser based form and when publishing it the typical error box appeared asking if I wanted to Review Errors or Publish Anyway. This box only appears if the Designer Checker has already been told to verify the form on the server before publishing.
If this setting hasn’t been set then the form will publish and you’ll receive a warning box staying the form publishing status and error message. By clicking the OK button the Designer Checker task pane will open and the Verify on Server check box will automatically get checked. In my opinion this warning should have appeared before the form was published so the error could be resolved before publishing the form.
Clicking the Review Errors button the Design Checker task pane appears and allows for view of the errors, Refresh button (check for errors again), Verify on server check box and Change Settings link. If you’ve never used InfoPath 2010 or 2007 the error message in task pane is clickable and a more detailed error message is given. For this instance the error tells me it’s not convertible because I’m running a older version of Form Services and that’s not a 100% correct either because I’m using InfoPath with BPOS.
If you ever want to run the Design Checker before publishing it can be done from the File page by clicking the Design Checker button. If the form has an existing error then the Design Checker will be highlighted in red. When going to this page for something else the red highlight was immediately noticeable and it was a great nonintrusive way to show the form still had a error.
To fix this particular error the form type had to be changed and the dropdown box to do this is located on the Compatibility screen on the Form Options pop-up. The Form Options pop-up is accessible by clicking the Form Options button from the File page or Change settings link from the Design Checker task pane. The Change settings link takes you directly to the screen. By changing the value to InfoPath Filler Form or InfoPath 2007 Filler Form and clicking the OK button the error goes away immediately.
Ok now for the unexpected functionality. If you click on the red x to close the dialog box it doesn’t cancel publishing of the form but instead publishes it. To be honest this functionality really surprised me because I was expecting it to cancel the publishing and show me the error message in the Designer Checker task pane. This is definitely one of those situations that gets written in OneNote as unexpected behavior for InfoPath.
1. June 2010 16:27
One of the best times and sometimes frustrating times is when a new version of a product is released and you get to learning all the new features of it or learn where all the old options have been moved to. When I started using InfoPath 2010 I had to figure out where the option “Create labels for controls automatically” check box was located so I could turn it off. Luckily this was a easy one and it took me only about 5 minutes to figure out. Below are instructions on how to turn it off/on.
- From your InfoPath design view click File
- From the File page click “Options” in left vertical menu
- From the InfoPath Options dialog click the “More Options” button
- From the Options dialog click the “Design” tab and uncheck the “Create labels for controls automatically”
- Click OK twice to accept the change.
Hope this helps.
28. May 2010 13:11
Recently I’ve been working in InfoPath 2010 building out a bunch of new forms for SharePoint Saturday and I discovered a new feature that prevents controls automatically being added to the design page with the default field naming convention. In InfoPath 2007 this default functionality drove me nuts because I didn’t have any control of the default field names if I wanted to design the form visually first.
Example: field2, field3
Now in InfoPath 2010 you can prevent this by happening by unchecking the “Automatically create data source” check box located at the bottom of the Controls task pane.
If you are sitting there scratching your head saying how do I get the Controls task pane to display don’t feel alone because it took me about 10 times playing with InfoPath 2010 to find it. From the Controls section on the ribbon click the diagonal down pointing arrow and that will display the Controls task pane.
Now look at the bottom of the Controls task pane and you’ll find the magical check box. By unchecking this check box you will now be shown the binding dialog every time you add a new control to the design area.
For all my new forms for the next couple of months I’ll be leaving the check box unchecked and designing my forms visually to see if this is a better approach for me than my traditional method.
21. February 2010 14:08
Today I got around building another SharePoint 2010 environment because I wanted to enter in the Use InfoPath 2010 with SharePoint 2010 Beta and Win an XBox360 Elite!and need a clean environment and I ran into a interesting error when trying to edit a SharePoint List with InfoPath. When I created the new application and site collection I just used server name. When accessing it from the server the URL worked just fine as http://servername but when accessing it from my Windows 7 VM I had to use the fully qualified server name. No big deal with SharePoint because everything worked as expected. When I tried to edit my custom SharePoint List with InfoPath then I got the below error.
“InfoPath cannot generate a form template for the SharePoint list.”
“The SOAP response indicates that an error occurred on the server:”
“Server was unable to process request. ---> The Web application at http://url/_vti_bin/FormServices.asmx could not be found. Verify that you have typed the URL correctly. If the URL should be serving existing content, the system administrator may need to add a new request URL mapping to the intended application.
After reading the error message I tried the FormServices.asmx url in the browser and it worked without a hitch. Then I thought about it a little more and the last part of the error message. I’m using the fully qualified URL because I’m running from my VM but the fully qualified URL is not part of Alternate Access Mapping so I just went to Central Admin and AAM page and added the URL as Intranet and tried it again and everything worked without a hitch.
18. July 2009 01:20
If you haven’t heard the InfoPath Team Blog has 3 new entries about InfoPath 2010 and the latest entry has video’s. Once you go out and see you’ll notice that the InfoPath Designer has had a face lift and now has a ribbon. The ribbon has brought a lot of easy of use for the product and it is making things so much easier to do now and publishing has became as easy as one click. That’s right one click and your form can be published. For all the details check out the InfoPath Team blog. http://blogs.msdn.com/infopath/default.aspx
6. June 2009 16:59
The last blog entry I had was getting out of New York and since then I’ve been heads down with SharePoint Saturday, Triangle SharePoint User Group, getting ready for a baby girl and plenty of SharePoint and InfoPath work and speaking. My winter and spring has been busier than ever and I am now really excited that I’m starting to have extra time to write again and I have plenty to write about, trust me. :) I know I’m not the best writer but I really had a good time doing it and I’m ready to get back into.
If you haven’t heard yet, there is a new community event out there called SharePoint Saturday and if you haven’t checked it out you should because one might be happening close to you. http://www.sharepointsaturday.org SharePoint Saturday is one of the major reason why I’ve been absent from this blog and who knew it would take so much work to get something like this running on it’s own legs. I had some great help from Susan Lennon, Kevin Israel and Dux Raymond Sy.
If your local to the Raleigh area then check out the new SharePoint user group that was restarted by Josh Carlisle and myself. You can check out the new site at http://www.trispug.com
If you have any questions about either event please fill free to drop me a comment or email.
20. December 2008 15:31
Everybody who knows me, knows that I’ve been working in New York for the past 11 months and commuting back and for from NC. At first when I started working in New York I had a lot of problems because I was always scared that something horrible was going to happen to me and after the months off getting used to living there and people making fun of me because I was so paranoid, I slowly started to get used to all the people everywhere. I even started riding the subway during the daylight hours but never that far and I always stayed in Manhattan. I’m still paranoid about riding it at night or off the island and still won’t do it unless somebody else is with me most of the time. I’m just not a big city person but I’m getting there slowly.
Now that you have the basic understanding of me in New York let’s get to why I’m writing this post. Yesterday December 19th, 2008 was the last day of work for me in New York until January and unfortunately Mother Nature didn’t want me to leave easily because she decided to create this nasty snow and sleet storm all day on Friday. All day I would look out the window and see either heavy snow or hear sleet hitting the window. The longer it went on the more I understood that getting out of the city was going to be really painful unless I took the subway and Airtrain to JFK airport. A taxi or private car was out of the question at this point because of the sleet and the traffic out of the city would be horrible and very unpredictable. So I hoped onto the internet and went out to www.hopstop.com
and looked up how and how long it was going to take to get to JFK. When the results game back it was very simple but it was going to take an hour to get there (which is really good time to be honest) but that meant riding on the subway for 30 minutes (people touching me) and into uncharted territory. I was really having second thoughts about doing this and thinking that I could just spend the night and catch another flight the next day. After battling with this for a while I decided to do it. I went back to the apartment and packed everything I could into one bag and took my 3 laptops and started making my way to the subway station. The walk to the subway station was pretty rough because there was 2 inches of snow, slush and water for 5 blocks. When I finally got there I made it through the turn styles with my luggage and down to the train platform. When the train came it was jammed pack with people and only 2 or 3 people got off at my door but I was able to push my way in and off we went. There was nowhere for me to hang on but it didn’t make a difference because we were body to body and nobody was moving anywhere. It stayed packed for about 15 minutes until train was under the river and onto Long Island and then people started getting off. Finally got to Jamaican station and hopped off and walked over to Airtrain station and then hopped on the next train. Traveled on that for about 15 minutes then I was at the airport. Over all it took about an hour but it was really draining on me from all the walking, pushing, shoving and people just bumping into me. It was probably the only way to go but definitely not something I would do in the future unless I had to again.
When I tell people this story in the future nobody will believe me because they would say I would never be able to do it because of people touching me, germs, people touching me and people touching me. But I did do it because I really wanted to get home that night and not get stuck in NYC because the weather could get worse overnight or next day. I got on the plane as schedule then deiced and left for NC and was only an hour late. All is good now because I’m home and getting ready for Christmas.
Hope everyone has a great holiday.
19. December 2008 14:39
This week has been one crazy week for me because Christmas is next week and I’m technically on vacation now for the next 3 weeks. Just like almost everyone else I've been scrambling to get as much work finished before leaving and I had several projects at once pushing for everything to be released by today (Friday). This unfortunately caused for some oversight on my part and caused a lot of little interesting problems to pop-up. One problem that I had was with InfoPath and Data Connections. During the course of my current project the SharePoint Site Collection where the forms were being deployed and Data Connection files being published changed because of Information Architecture had been modified to include "Forms Centeral" and yesterday I ran into this nice error.
“Relative links to Data Connection Libraries located in different SharePoint site collections are not supported”
It didn’t take me long to figure out what the problem was but it was the first time I ran into it and I wanted to mention it. The error message was dead on and I was getting this because I was referencing 2 site collection data connection libraries. I had 2 data connections pointing to the old site collection and one to the new one. After changing the reference everything started working again with no errors. Since I’m publishing all my InfoPath forms into a single Site Collection I decided to keep all my Data Connection files local to that site collection and not publish them to IPFS data connection library in central admin and when I switched site collections I didn’t update the forms data connection references.. You might be saying that this should have broken right away and in normal circumstances it probably would have but I had the “Allow cross-domain data access for user form templates that use connection settings in a data connection file” option selected on IPFS "Configure InfoPath Forms Services" page and this allows for cross site collection Data Connection and Form Library usage.. It’s turned off now that way I don’t have any more problems like this in the future.
If you’re interested in learning more about submitting InfoPath forms across site collections or even web applications you should come out to the spring SharePoint Connections in Orlando because I’ll be doing a session on this very subject. This is will be my first time speaking at SharePoint connections and I really excited about it.
Well it's that time of the year again and I hope that everybody is all ready for the holidays and if not you still have a couple days left. I’m heading back home from New York to get ready myself and then we are spending Christmas with my folks. I’m looking forward to it because I’ll be getting a really good home cooked meal and see everybody in the family. My brother Mark, who just got back from Iraq on Thanksgiving Day, will be there to. It’ll be the first time I’ve seen him since he shipped out in early spring. This Christmas is shaping up to be a good one for me and I hope everyone else a great one to.