You’re trying to create a Data Connection Library in a SharePoint site and you find that the template isn’t available. Note that the Data Connection list template is only available in MOSS 2007.
The Data Connection list template feature (feature id: 00BFEA71-DBD7-4F72-B8CB-DA7AC0440130) isn’t actiavted against all site definitions, and if you are using a custom site definition, you may not have activated it in your WebFeatures section. The Data Connection list template feature is stapled (feature stapler feature id: CDFA39C6-6413-4508-BCCF-BF30368472B3) to the following site definitions;
- STS#0
- STS#1
- STS#2
- MPS#0
- MPS#1
- MPS#2
- MPS#3
- MPS#4
- WIKI#0
- BLOG#0
- BDR#0
- OFFILE#0
- SPS#0
- SPSPERS#0
- SPSMSITE#0
- SPSNEWS#0
- SPSNHOME#0
- SPSSITES#0
- SPSREPORTCENTER#0
- SPSPORTAL#0
- SRCHCEN#0
- PROFILES#0
- CMSPUBLISHING#0
The good news is that you can just activate the feature manually using STSADM, as shown below;
stsadm -o activatefeature -name DataConnectionLibrary -url {site url}
Alternatively, if you’re using a custom site definition, you can just add the feature to your WebFeatures section;
<WebFeatures>
<!-- Activate the Data Connection List Template -->
<Feature ID="00BFEA71-DBD7-4F72-B8CB-DA7AC0440130"/>
</WebFeatures>
platinumdogs.me 
Hi
I need to do this. Do I need create a feature receiver first. then add the following to each site definition:
If so do you have the source for the feature receiver?
Cheers
Daniel
Daniel, you don’t need a feature receiver, if you’re writing a custom site def you just need to add the feature to the WebFeatures section of your onet.xml file (as shown in the code segment).
If you’re writing just a feature, you could make the Data Connection List Template feature an activation dependency of your own feature (as it’s a hidden feature it should activate silently when your feature is activated)
Phil
This is exactly what I did. I didn’t need to create the Data con lib automatically but at least the option is there in the Site Actions Create. Thanks once again.
No worries
Also – another way that worked for me – was to activate the “site level” feature >> SharePoint Server Enterprise Site features