Archive for June, 2012
When I was installing the Application Definition Designer, I have got the following wired error message! 😦
The text format of this error message is:
Unexpected Error has occurred. Error is 'SetParent failed for Database 'AR633564737049916886'.' --> SetParent failed for Database '<em>AR633564737049916886'.' --> Failed to connect to server. \BDC. --> An error has occurred while establishing a connection to the server. When connecting to SQL Server..
This is not even a brief message to understand no? After spending few minutes, I have found the possible causes for this error.
1. Not enough permissions to configure BDC (Business Data Catalog) instance
2. There is no BDC instance on our SQL Server, this means the installation expects the BDC instance to continue.
In my case, I have adequate permissions for BDC, so the problem is 2nd one. If we run the BDCStudioSetup.msi file directly, Instead of running the setup.exe on the “BDC Definition Editor” directory then we get this error! 😦
You can see the complete installation and configuration of Application Definition Designer here.
Happy configuring..! Thanks. R./
Everyone knows about the usage of Application Definition Designer, this is a Microsoft tool that comes with the SharePoint Server SDK. You can see the overview and the system requirements here. While installing this tool I have faced few problems, so I just wanted to keep the steps in my bolg.
Step 1: Download the tool and double click the “OfficeServerSDK.exe”, You will be getting this screen.
Step 2: Click Next 😦
Step 3: The Office SharePoint Server 2007 SDK has been successfully installed. Great!
Step 4: Navigate to SDK installation path\Tools\BDC Definition Editor\. The default installation path for the MOSS SDK is <%Program Files%>\2007 Office System Developer Resources\. For me this is the path..
C:\Program Files \2007 Office System Developer Resources\Tools\BDC Definition Editor
Step 5: In this directory, double click the setup.exe
Please Note: If you double click the BDCStudioSetup.msi file directly, Instead of clicking setup.exe then you will get this error. This happened to me when I installed! 🙂
Step 6: Click Accept and continue, this will configure the SQL client.
Step 7: Click Next and close! 🙂
Step 8: That’s all, you can run the “ApplicationDefinitionDesigner.exe” in the “All Programs”
Step 9: We are ready to create the ADF (Application Definition File) to configure the BDC (Business Data Catalog) now.
I was working on BDC (Business Data Catalog), to display the user profile data from SQL Server in SharePoint 2007. I was using “Application Definition Designer” (A Microsoft tool that comes with the SharePoint Server SDK, you can see the installation and configuration here) to generate the ADF (Application Definition File). I tried to access the Business Data Types on the SharePoint page and then I have got the following wired error message. 🙂
BDC is not a really new stuff, so I tried to find the solution on the web but I didn’t get any direct solution immediately. Most of them are suggested to check the permission but I have adequate permission for BDC. Finally I have got the solution form this thread. Actually this is a bug in the Application Definition Designer and I don’t really know why it’s still there!
There might be two reasons to getting this error.
1. Not having enough permission to access the BDC
2. The “Finder” method is not generating properly in the “MethodInstanceType” property.
In my case I had adequate permisioion for the BDC, so the “Finder” method was my problem.
You can see the “MethodInstanceType” property has “IdEnumerator” method instead of the “Finder”. So just click the drop down list and select the Finder method.
Then just export the ADF again, the Business Data Type Picker is showing the entries now huh? 🙂
Deploying a web part solution to the SharePoint using STSADM is an easy task, everyone knows about it. But while developing a web part, sometimes we need to re-deploy the solution again and again. In this case we cannot simply re-deploy the solutions and we have to follow some additional steps to redeploy again.
There are several ways to create the solution file, but I have used the WSPBuilder to create this web part solution. You can see this in my previous post.
There are 2 steps to deploy a solution using stsadm.
- Add solution – Add a solution file to the solution store. See more details here.
- Syntax: stsadm -o addsolution -filename <solution file name>
- Deploy solution – Deploys files related to a solution from the configuration database to individual front-end Web servers in the farm. See more details here.
- Syntax: stsadm -o deploysolution -name <solution name> -immediate -allowgacdeployment -force –allcontenturls
- We need one more command to Executes all administrative timer jobs immediately instead of waiting for the timer job to run. See more details here.
- Syntax:stsadm -o execadmsvcjobs
Ok, we will see the steps here:
Step 1: Open the cmd prompt and change the directory (cd) to stsadm.exe location, I am using SharePoint 2007 so this is the path: “cd c:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\bin”
Step 2: Adding the solution, my solution file is in the C:\Temp\
stsadm -o addsolution -filename C:\Temp\WSPBuilderStepBiStep.wsp
Step 3: Deploying the solution
stsadm -o deploysolution -name WSPBuilderStepBiStep.wsp -immediate -allowGacDeployment -force -allcontenturls
Step 4: Executing the timer jobs
stsadm -o execadmsvcjobs
Please note: The name and filename in the above commands, if it is filename we have to use full file path.
When we deploy the solution package without retract and delete then we will get the following error message:
There are many ways to do this (Using UI, WSPBuilder and so…) but here are the steps which I normally used (Specially in the production servers):
- Retract solution: Retracts the specified solution’s deployment which removes files from the front-end Web server. This is actually reversing the deployment. See more details here.
- Syntax: stsadm -o retractsolution -name <solution name> [-immediate] [-allcontenturls]
- Delete solution:Removes a solution file (package) from the solution store. See more details here.
- Syntax: stsadm -o deletesolution -name <name> [-override]
Here are the steps:
Step 1: Retracting the solution
stsadm -o retractsolution -name WSPBuilderStepBiStep.wsp -immediate –allcontenturls
Step 2: Executing the timer jobs
stsadm -o execadmsvcjobs
Step 3: Deleting the solution
stsadm -o deletesolution -name WSPBuilderStepBiStep.wsp –override
Step 4: Re-deploy the solution again, for this follow the steps 1 to 3 in the Deploy!
That’s all, Happy deploying..! 🙂