While importing customization from development to staging server we were receiving the error.
It was giving the error on a particular relationship “opportunity_new_dataaudit”.
What we did was to comment the entire EntityRelationShip tag for that particular relationship along with it’s corresponding EntityMap entry in the customization.xml
<Description description=”Unique identifier for Opportunity associated with Data Audit.” languagecode=”1033″ />
<field name=”new_opportunityid” requiredlevel=”none” imemode=”auto” lookupstyle=”single” lookupbrowse=”0″>
<displayname description=”Opportunity” languagecode=”1033″ />
And than we tried importing it and it worked for us.
And there was another way we were able to resolve this error, quite interestingly when we changed the name of EntityRelationship from
i.e simply appending new_ to relationship name in the customization.xml it imported successfully !
To specify connection string with user id and password we need to have the following things in the application defination file (.xml)
<LobSystem xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance“ xmlns:schemaLocation=“http://schemas.microsoft.com/office/2006/03/BusinessDataCatalog BDCMetadata.XSD“ Type=“Database“ Version=“184.108.40.206“ Name=“NorthwindLOBSystem“ xmlns=“http://schemas.microsoft.com/office/2006/03/BusinessDataCatalog“>
<Property Name=“WildcardCharacter“ Type=“System.String“>%</Property>
<Property Name=“DatabaseAccessProvider“ Type=“System.String“>SqlServer</Property>
<Property Name=“AuthenticationMode“ Type=“System.String“>PassThrough</Property>
<Property Name=“RdbConnection Data Source“ Type=“System.String“>d-2926</Property>
<Property Name=“RdbConnection Integrated Security“ Type=“System.String“ />
<Property Name=“RdbConnection Initial Catalog“ Type=“System.String“>Northwind</Property>
<Property Name=“RdbConnection User ID“ Type=“System.String“>sa</Property>
<Property Name=“RdbConnection Password“ Type=“System.String“>sa</Property>
<Property Name=“RdbConnection Pooling“ Type=“System.String“>false</Property>
We need not to specify any value for Integrated Security as we are using sql authentication
And can specify user id and password with RdbConnection User ID and Password Property.
- Back Up and Restore the content database to a new Sql server
- In Central Administration page
- Go to Application Management and Click on Create or extend web application.
- Therein Create a new web application. Once application is created don’t create Site Collection.
- Now again go back to Application Management.
- Therein click Content Databases
- Change the web application to point to web application you just created.
- Remove the default content database created while creating the web application.
- Then click on Add a content database
- Specify the Database Server where the content database was restored and in database name specify the name of the content database.
- The site should get restored properly.
Check out this good information
After running the Sharepoint products and technologies configuration wizard successfully, the central administration site page opens up.
( We were installing MOSS 2007 on 64 bit machine)
But in my case it was giving the following error
Checking into event log gave the following information
Could not load all ISAPI filters for site/service. Therefore startup aborted.
ISAPI Filter ‘C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_filter.dll’ could not be loaded due to a configuration problem. The current configuration only supports loading images built for a AMD64 processor architecture. The data field contains the error number. To learn more about this issue, including how to troubleshooting this kind of processor architecture mismatch error, see http://go.microsoft.com/fwlink/?LinkId=29349.
Searching for it the solution that I found was the following
// Disabling the 32bit mode for your web site.
cscript C:\inetpub\adminscripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 0
and then the following
// Registering ASP.NET 2.0 as the default framework for that web site
This resolved the issue for us!!
Got this issues while running the set up for MOSS 2007 on 64-bit edition of Windows server 2003.
The resolution i found for this was following
1) Open the command prompt
2) Navigate to the following directory
3) Type the following command
adsutil.vbs set w3svc/AppPools/Enable32bitAppOnWin64 0
4) And finally IISRESET.
Last week I took this exam and passed with a score of 98. For preparation I used the following training material.
Course 8912: Customization and Configuration in Microsoft Dynamics CRM 4.0 and Working with Microsoft Dynamics CRM 4.0 (Microsoft Press).
I felt the course 8912 training material is more than enough for passing the exam.
(Chapter 11: Introduction to Advanced Customizations :- There weren’t any questions from this chapter it’s just there for our own understanding).
When we create ASP.NET web service from visual studio and run the web service a test page opens up in which we can test our web service.
We can easily customize that web service test page. The name of the page is DefaultWsdlHelpGenerator.aspx we can found it in the following directory
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\CONFIG\ for ASP.NET 2.0.
Open the page in Visual Studio
First and foremost we would find the following things that could be configured
// set this to true if you want to see a POST test form instead of a GET test form
bool showPost = true;
// set this to true if you want to see the raw XML as outputted from the XmlWriter (useful for debugging)
bool dontFilterXml = false;
// set this higher or lower to adjust the depth into your object graph of the sample messages
int maxObjectGraphDepth = 4;
// set this higher or lower to adjust the number of array items in sample messages
int maxArraySize = 2;
// set this to true to see debug output in sample messages
bool debug = false;
To customize the UI good information is provided over here
Customizing Web Service Test Page’s UI Design
By Default the web service can be tested using Http Get (default) and Http Post, but if we want to test using the SOAP we can make use of the information provided in the following link
Testing Web Service with SOAP
Hi I got this error when i was taking the backup of the farm
stsadm.exe -o backup -directory \\d-4526\MossFarmBackup -backupmethod full
The solution for this is to
Go to Central Administration Page.
Click on your Shared Service
Then on Search Settings there Reset all crawled content
This should solve the problem
To create a new web application which will use an existing content database we need to do the following.
Open Sql Server Management Studio
To take back up of the database in my case it was ‘WSS_Content_fa5cc7a0686e424bbe4fc128b4a48cf4’
Right click the database — select tasks —select Offline—then select Detach.
Get the mdf and ldf file for the database.
Attach the files and create a new database.
Now to Central Administration Site — Application Management — Create a new web application
Let the name of the database as default.
Now go to Content Database within Application Management — Select the web application just created.
Click on the Database Name — Select Database Status as Offline and Check Remove Content database check box.
Now click on Add Content Database— In the Database Name specify the name of the new restored database.
This is the point we can get this error “A SharePoint database named ‘….. ‘already exists. You must supply another name for the new database”
The solution for this is to go to
SharePoint_Config database —There run this query
delete from Objects where name=’name of restored db’;
We upgraded from CRM 3 to CRM 4, and certain users got this error while trying to access the CRM.
We realized that the users receiving this error had our own custom security role assigned to them. i.e System Primer.
When we assigned them any of the existing default security role there was no problem in accessing the CRM.
So the way we resolved was to assign a default security role and our own custom role to the user, so that he could access the system for the first time without any issues and
after the user has accessed it once than we removed the default security role.
This approach worked for us!!!!
Or another thing that worked was if we are assigning any custom role to users, we gave the write permission for user settings in that custom role.
the kb article for this error are