In
Many Organization while Implementing SharePoint 2010 . the first question
which may arise is What are the account we need to create and what are the
permission levels it should have . I have tried my best to collate the things
together and text it in my Blog .
Here
we go with another new issue and easy resolutions & workarounds
This
time, the issue was with Nintex workflows at the time of activating a site
collection feature. Let me describe the details in step by step so that it will
be easy recognize as well as understand
Problem
Description:
Problem
activating Site Feature. While activating the ‘Nintex workflow 2010’ at the
site collection level, we faced the following error message:
Error
Message:
An
unexpected error has occurred.
Troubleshoot
issues with Microsoft SharePoint Foundation.
Correlation
ID: XXXXX
Troubleshooting
Steps:
1)
Most imp regarding any exceptions: SharePoint logs (\14\logs)-specifically if
we face “unexpected error”
2)
Windows event logs
3)
If we have a correlation id then it’s very easy to find out the exact error
message
After
reviewing the SP logs, this is what I found:
Exception
was thrown while ensuring dependencies met for feature 'NintexWorkflow' (id:
0561d315-d5db-4736-929e-26da142812c5):
Nintex.Workflow.NWFeatureActivatingException:
Nintex.Workflow.NW2007DatabaseConnectionException: Failed to open a connection
to the Nintex Workflow configuration database. --->
System.Data.SqlClient.SqlException: Cannot open database "NW2007WFDB"
requested by the login. The login failed. Login failed for user
'Contoso\Administrator'.
What
we need to target first in such conditions:
1.
What exactly the app pool identity is used by that web application? Does it
have sufficient rights/not?
2.
The Nintex database has a role called WSS_Content_Application_Pools. This is
the group that we need to add the app pool identity to
SQL
SERVER
SharePoint_Config
Security
Users
The
account which is running the app pool of the web application
Right
Click-Properties
General
Database
role membership
Resolution:
I have
added this group named as WSS_Content_Application_Pools to the APP POOL
identity and that it. It worked and issue has been successfully resolved
Problem Description: If the proper filer is not applied in import connections then it can lead to hundreds of unwanted / disabled profile in ssp database. Sometimes due to IT audits we want to get rid of those profiles from SharePoint.
Product Applies: 1. MOSS2007 (Microsoft Office SharePoint Server 2007) 2. WSS3.0 Windows SharePoint Services 3.0)
Error Message: N/A
What exactly I did? How exactly I configured and came to know about the issue? 1. In AD, I have created lots of user and disabled few of them.
2. Configured SSP to import user profile by using the default filter (&(objectCategory=person)(objectClass=user).
3. That’s it-Problem started and found lots of profiles in view user profile.
June 2014 Cumulative Update for SharePoint 2013 has been released. SharePoint Foundation - KB2881063 http - //support.microsoft.com/kb...
Disclaimer
The opinions expressed on this blog are the personal views of Pratik's SharePoint Blog, and do not represent or reflect the viewpoints or policies of any past, present, or future employer, colleague, or customer, or any other entity. The posts on this blog are provided ‘as is’ with no warranties, express or implied, and confer no rights. Use of information contained within this blog, including specific technical steps mentioned herein, is at your own risk. References to specific software products, processes, resources, or companies do not imply any endorsement.