in

SharePoint Blogs

The Best Place for SharePoint-related Blogs

Aziz

  • force deactivating and activating the Forms Services feature - MOSS

    i have MOSS enterprise on my company and yet i couldnt use the forms services features

    after  some reasearch i found some post by David Szabo that should me how to force activate and deactivate the Forms Services Features

    PLEASE NOTE: This is provided "AS IS" with no warranties, and confers no rights.

    first log on to the C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN folder, then run the commands from there (SDSADM.EXE lives in this folder)

    Run the following commands to force deactivating and activating the Forms Services feature:

    stsadm -o deactivatefeature -filename IPFSSiteFeatures\feature.xml -force -url %SITE_COLLECTION_URL%

    stsadm -o deactivatefeature -filename IPFSWebFeatures\feature.xml -force -url %SITE_COLLECTION_URL%

    STSADM.EXE -o activatefeature -filename IPFSSiteFeatures\feature.xml -url %Sitecollection_URL% -force

    STSADM.EXE -o activatefeature -filename IPFSWebFeatures\feature.xml -url %sitecollection_URL% -force

    ** NOTE: The "%Sitecollection_URL%" is a place holder that would be replaced with your site collection URL, such as: http://sharepoint/sites/YourSiteCollection

  • The form cannot be displayed because session state is not available.

     another situation and another problem that i found a perfect solution for it googling the error

    originally written by  Mike - H

    InfoPath 2007 - MOSS 2007 - The form cannot be displayed because session state is not available.

    Whether you are working with forms in custom workflows - or simply trying to publish a form to a form library in MOSS so you can collect information from the user, you may encounter this error.

    Initially if you Google the error - you may find comments that state that you need to uncomment the following line in the web.config for the web application:

    <!-- <add name="Session" type="System.Web.SessionState.SessionStateModule"/> -->

    DO NOT uncomment this field. Many do this and the forms may work - and this appears to be the solution - but it is not the best practice and it is not recommended by MSFT.

    You probably have not created a Shared Service Provider and associated the web application in question with the SSP.

    MOSS uses the Shared Service Provider to allow / manage session state for a Farm - and specifically for the associated web applications under that SSP.

    CREATING THE SHARE SERVICE PROVIDER

    When you installed MOSS - the first thing you began to get familiar with is the Central Administration tool. Take a look at the following snapshot:

    Click here for a snapshot

     

    Notice on the left side - under Shared Services Administration, there are 2 SSP's - SSP Administration and SSP Services. These were created after the farm was deployed (a farm is used relatively here - in essence, after MOSS was deployed).

    When you first setup MOSS - there are no SSP's out of the box deployed for you. You must manually create them.

    The first SSP you create will contain the SSP/Admin site - and you will also receive a warning that you should not create things like My Sites or Search services scopes within this SSP. It is a best practice to first create an initial SSP - like the example above - name is SSP Administration - and then create a 2nd or successive SSP's for shared services (like Forms, Search, Excel, My Sites, etc).

    Finally, when creating a SSP - you will notice that the SSP site will default to an existing web application. See the snapshot below:

    Click here for a snapshot 

    Under the Basic Sites in this example, you would click the Create a new Web Application - the objective is to place the SSP in its own web application and not an existing one. Once that web application is provisioned - you will be returned to this screen and you'll be able to select the appropriate web application for the SSP.

    Ping me if you have any questions - hope this is helpful...

  • A checklist for enabling browser forms with Forms Services and SharePoint 2007

    I am kinda newbie to Sharpeoing and Infopath so each time i try to do something i end up with tons of errors and i have to google that errors for hours till i find whats going on and how to fix it Big Smile

     so i thought maybe i should post all the usefull articals that i find so that i can easliy find them agian when i need them and to share it with others too

    here is a great post by David Szabo about how to configure MOSS to run infopath forms as browser enabled

    you can find link to his post here 

    This is a checklist to follow if you are having problems with publishing InfoPath 2007 browser-enabled forms to Microsoft Office SharePoint Server 2007. A typical error message you receive in this case is

    "This form template is browser-compatible, but it cannot be browser-enabled on the selected site"

    ... with an ugly yellow color. Here's what to check before you're going crazy:

    1. Install Microsoft Office Forms Server 2007 (independent product) on the SharePoint box if the Office server suite you use is lower than Enterprise (or if you are using Windows SharePoint Services 3.0). The Forms Services support is included in the Enterprise Office Server suite.
    2. After installed Forms Server, you'll have a InfoPath Forms Services section at the Application Management page. To go here, click on Start -> Administrative Tools -> SharePoint 3.0 Central Administration and choose the Application Management tab on the top of the page. Click on Configure InfoPath Forms Services in the InfoPath Forms Services section and check both "Allow users to browser-enable form templates" and "Render form templates that are browser-enabled by users" checkboxes, then OK this page
    3. Open your SharePoint site, click on Site Actions -> Site Settings, select Site collection features under Site Collection Administration and activate InfoPath Forms Services support
    4. Start designing your form with the InfoPath 2007 client. In InfoPath, click on Tools/Form Options, select the Compatibility category and check the "Design a form template that can be opened in a browser or InfoPath", then click OK. In the case if you miss this one and your form is browser-compatible, you get a warning message while publishing your form saying that "The server is running InfoPath Forms Services, but the compatibility settings for this form template is InfoPath only".
    5. Make sure that your form is browser-compatible. You can use the design checker task pane in the InfoPath 2007 client to perform this task.
    6. Publish your form onto a SharePoint 2007 library. In the wizard, at step 3, check the "Enable this form to be filled out by using a browser" checkbox and finish publishing.
    7. At the end of the publishing wizard, select "Open this document library" and click on Close. This will open the document library in the browser. Click on Settings/Form Library Settings, then click on Advanced Settings and select the "Display as a Web page" option in the Browser-enabled Documents category. If you don't choose this option, the form will be opened in InfoPath if it's installed on the client. Otherwise, it's going to be opened in the browser.

    Hope that helps!


Need SharePoint Training? Attend a SharePoint Bootcamp!

Posts (c) their respective authors. Everything else (c) 2007 SharePoint Experts