SPConfigStore Forum Rss Feed

New Post: ECMA Script Library for ConfigStore

brunobertechini — Wed, 21 Nov 2012 15:20:53 GMT

Chris, first of all, congratulations for the great work...

Do you have any plans to add an ECMA script library for same features you have from code (C#) ?

That would be very appreciated!

Cheers

Bruno Bertechini

New Post: SP 2010?

pwalke — Thu, 30 Aug 2012 15:56:14 GMT

Hi Rob,

I don't have a test SP environment handy to repro your steps. You can debug the ArgumentNullException by setting the deployment configuration to "No Activation" (project properties > SharePoint > Active Deployment Configuration). You can then debug the wsp through visual studio. Set a breakpoint at COB.SharePoint.Utilities.Features.ConfigStore.ConfigStoreEventReceiver.FeatureActivated, activate the feature through site settings and try to see what argument is null.

...Peter

FeatureActivated FeatureActivated

New Post: SP 2010?

hussell — Thu, 30 Aug 2012 15:41:00 GMT

Interestingly this time I deployed the solution through stsadm and it worked, I then tried to activate the feature and got these error fromt he logs...

Medium	Name=Request (POST:http://test.it:80/_layouts/ManageFeatures.aspx?Scope=Site)
Medium	Site=/
Medium	Feature Activation: Activating Feature 'COB.SharePoint.Utilities.ConfigStore_ConfigStore' (ID: 'ca9d918f-2845-4421-b005-65625aef5cb5') at URL http://test.it.
Medium	Caching global content types for LCID 0.
Medium	Caching global fields.
Medium	The configuration database was queried for a non-existent object with the id 69828593-5a05-4d29-bfc6-bc55c2739067. Most commonly, this is caused by removing an SPFeatureDefinition without writing upgrade code to remove references to the feature from each site.
High	Failed to determine the setup path of the list schema for feature {69828593-5A05-4D29-BFC6-BC55C2739067}, list template 10100.
High	The element of type 'ListInstance' for feature 'COB.SharePoint.Utilities.ConfigStore_ConfigStore' (id: ca9d918f-2845-4421-b005-65625aef5cb5) threw an exception during activation: Feature '69828593-5a05-4d29-bfc6-bc55c2739067' for list template '10100' is not installed in this farm. The operation could not be completed.
High	Feature Activation: Threw an exception, attempting to roll back. Feature 'COB.SharePoint.Utilities.ConfigStore_ConfigStore' (ID: 'ca9d918f-2845-4421-b005-65625aef5cb5'). Exception: System.ArgumentException: Feature '69828593-5a05-4d29-bfc6-bc55c2739067' for list template '10100' is not installed in this farm. The operation could not be completed. at Microsoft.SharePoint.SPFeatureManager.<>c__DisplayClass19.<GetFeatureRootAndListSchemaPaths>b__18() at Microsoft.SharePoint.SPSecurity.RunAsUser(SPUserToken userToken, Boolean bResetContext, WaitCallback code, Object param) at Microsoft.SharePoint.SPFeatureManager.GetFeatureRootAndListSchemaPaths(Byte[]& userToken, Guid& tranLockerId, Int32 nZone, Guid databaseid, Guid siteid, Guid webid, Guid featid, Int32 ltid, String& sPathToF...
High	...eatureRoot, String& sPathToSchemaXml) at Microsoft.SharePoint.Administration.SPElementDefinitionCollection.ProvisionListInstances(SPFeaturePropertyCollection props, SPSite site, SPWeb web, Boolean fForce) at Microsoft.SharePoint.Administration.SPElementDefinitionCollection.ProvisionElements(SPFeaturePropertyCollection props, SPWebApplication webapp, SPSite site, SPWeb web, Boolean fForce) at Microsoft.SharePoint.SPFeature.Activate(SPSite siteParent, SPWeb webParent, SPFeaturePropertyCollection props, Boolean fForce)
High	Leaving Monitored Scope (Feature Activation: Activating Feature 'COB.SharePoint.Utilities.ConfigStore_ConfigStore' (ID: 'ca9d918f-2845-4421-b005-65625aef5cb5') at URL http://test.it.). Execution Time=2169.01170400149
Unexpected	System.ArgumentException: Feature '69828593-5a05-4d29-bfc6-bc55c2739067' for list template '10100' is not installed in this farm. The operation could not be completed. at Microsoft.SharePoint.SPFeatureManager.<>c__DisplayClass19.<GetFeatureRootAndListSchemaPaths>b__18() at Microsoft.SharePoint.SPSecurity.RunAsUser(SPUserToken userToken, Boolean bResetContext, WaitCallback code, Object param) at Microsoft.SharePoint.SPFeatureManager.GetFeatureRootAndListSchemaPaths(Byte[]& userToken, Guid& tranLockerId, Int32 nZone, Guid databaseid, Guid siteid, Guid webid, Guid featid, Int32 ltid, String& sPathToFeatureRoot, String& sPathToSchemaXml) at Microsoft.SharePoint.Administration.SPElementDefinitionCollection.ProvisionListInstances(SPFeaturePropertyCollection props, SPSite site, SP...
Unexpected	...Web web, Boolean fForce) at Microsoft.SharePoint.Administration.SPElementDefinitionCollection.ProvisionElements(SPFeaturePropertyCollection props, SPWebApplication webapp, SPSite site, SPWeb web, Boolean fForce) at Microsoft.SharePoint.SPFeature.Activate(SPSite siteParent, SPWeb webParent, SPFeaturePropertyCollection props, Boolean fForce) at Microsoft.SharePoint.SPFeatureCollection.AddInternal(SPFeatureDefinition featdef, Version version, SPFeaturePropertyCollection properties, Boolean force, Boolean fMarkOnly) at Microsoft.SharePoint.SPFeatureCollection.AddInternalWithName(Guid featureId, String featureName, Version version, SPFeaturePropertyCollection properties, Boolean force, Boolean fMarkOnly, SPFeatureDefinitionScope featdefScope) at Microsoft.SharePoint.SPFeatur...
Unexpected	...eCollection.Add(Guid featureId, Boolean force, SPFeatureDefinitionScope featdefScope) at Microsoft.SharePoint.WebControls.FeatureActivator.ActivateFeature(Guid featid, SPFeatureDefinitionScope featdefScope) at Microsoft.SharePoint.WebControls.FeatureActivatorItem.BtnActivateFeature_Click(Object objSender, EventArgs evtargs) at System.Web.UI.WebControls.Button.OnClick(EventArgs e) at System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument) at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
Medium	Leaving Monitored Scope (Request (POST:http://test.it:80/_layouts/ManageFeatures.aspx?Scope=Site)). Execution Time=2353.96426082086

New Post: SP 2010?

hussell — Thu, 30 Aug 2012 15:27:15 GMT

Thanks for replying :)

I added the soultion but when I tried to deploy I received this error...

Failed to create receiver object from assembly "COB.SharePoint.Utilities.ConfigStore, Version=1.0.0.0, Culture=neutral, PublicKeyToken=23afbf06fd91fa64", class "COB.SharePoint.Utilities.Features.ConfigStore.ConfigStoreEventReceiver" for feature "COB.SharePoint.Utilities.ConfigStore_ConfigStore" (ID: ca9d918f-2845-4421-b005-65625aef5cb5).: System.ArgumentNullException: Value cannot be null.
Parameter name: type
at System.Activator.CreateInstance(Type type, Boolean nonPublic)
at Microsoft.SharePoint.Administration.SPFeatureDefinition.get_ReceiverObject()

New Post: SP 2010?

pwalke — Thu, 30 Aug 2012 14:41:15 GMT

Hi Rob,

I am sorry, I uploaded the wrong patch before. Please get my latest patch and let me know if that works for you.

Thanks,

Peter

New Post: SP 2010?

hussell — Thu, 30 Aug 2012 14:04:15 GMT

Hi pwalke

I tried your patched version for SP2010 but get the error Failed to find the XML file at location 14\Template\Features\config\feature.xml

when I try to activate the feature; I can definitly see the feature.xml file in that location

Have you come across this problem?

Thanks
Rob

New Post: Unable to use ConfigStore in an FeatureEventReceiver class

fmorriso — Mon, 07 May 2012 14:54:36 GMT

During feature activation, the only "config" being used is stsadm.exe.config, so if you don't put the same <appSettings> in stsadm.exe.config that you have in your web.config, any attempt to use Config Store (or anything else that uses <appSettings> values for that matter) during feature activation/deactivation, will fail.

On my Windows 2003 R2 (64-bit) MOSS 2007 SP2 (64-bit) server, stsadm.exe.config can be found here:

C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN\stsadm.exe.config

Yours may be somewhere else.

We also put certain <appSettings> into owstimer.exe.config as well, since some of our custom SharePoint Timer Jobs need environment-specific <appSetting> values and those jobs only read from owstimer.exe.config, not web.config.

New Post: Master Page

Myanta — Thu, 22 Dec 2011 23:11:23 GMT

I just found this and was able to install it. I can add items to the config so that part is working. What I would like to do now is to access this information from a master page. In other words I have a new item in the config called SiteName that I want plastered on the top of every page no matter which sub-site the user is on.

How can I access this information from the master file?

Thanks

Darrell Norton

New Post: SP 2010?

pwalke — Wed, 24 Aug 2011 14:48:14 GMT

The as-is version isn't a SP2010 Solution. I upgraded the project to SP 2010 and am using it regularly. You can download my patch here: http://spconfigstore.codeplex.com/SourceControl/list/patches

New Post: SP 2010?

jparra — Tue, 23 Aug 2011 01:57:22 GMT

Hi Chris!

Thanks for sharing this solution. Do you know if the current version will support SP 2010?

Thanks

Jose D. Parra

New Post: Config Store doesn't work for me.

chrisobrien — Wed, 29 Jun 2011 22:16:41 GMT

@vmichael,

This is happening because you're running in the context of a unit test, which is not within the scope of IIS/the web.config file. Add the Config Store entries to either the .exe.config file for your unit test framework, or to machine.config if this is a dev machine.

HTH,

Chris.

New Post: Config Store doesn't work for me.

vmichael — Wed, 29 Jun 2011 21:50:24 GMT

Chris,

I keeping getting this error but I have The key 'ConfigStoreCacheDependencyFile' defined in web.config - any ideas?

I Test method ReminderNoticeJobTest.UnitTest1.GetProperties threw exception:
System.TypeInitializationException: The type initializer for 'COB.SharePoint.Utilities.ConfigStore' threw an exception. ---> System.InvalidOperationException: The key 'ConfigStoreCacheDependencyFile' does not exist in the appSettings configuration section.

System.Configuration.AppSettingsReader.GetValue(String key, Type type)
COB.SharePoint.Utilities.ConfigStore..cctor()
COB.SharePoint.Utilities.ConfigStore.GetValue(String Category, String Key)
ReminderNoticeJobTest.UnitTest1.GetProperties() in D:\Development\mvasquez\ReminderTimerJob\ReminderNoticeJobTest\UnitTest1.cs: line 300

I am running windows server 2003 x64

Michael

New Post: SP 2010 support!

pwalke — Fri, 13 May 2011 18:20:37 GMT

I've upgraded 2.1.0.2 to SharePoint 2010. I imported the wsp to start, and the swapped out the assembly deployment creating the assembly by code. I then re-wired the feature receiver. The item receiver should probably be wired up via the SP2010 tooling, but I left it in the feature receiver as it currently is. You can feel free to download the patch from here:

http://www.codeplex.com/Project/Download/FileDownload.aspx?ProjectName=spconfigstore&DownloadId=239010

New Post: Cache issue

ramana16 — Tue, 01 Feb 2011 06:30:47 GMT

Dear Chris,

When the issue was first noticed I tried using Debug view on the front end server where this was happening and that is when I noticed that local config store value was not in cache and that the value was picked only from global config store. We recycled app pool (blank entry in web.config) to sort it out. As this is a production environment we dont have much time to troubleshoot.

you can reach me at ramana_16@hotmail.com

Thanks a lot for taking your time to help me out.

Regards,

Ramana

New Post: Cache issue

chrisobrien — Fri, 28 Jan 2011 15:14:33 GMT

@Ramana,

I haven't seen this behaviour, but would like to investigate this further with you to determine if there is a bug.

Have you tried enabling logging (or debugging) to see if there are any exceptions happening?

Thanks,

Chris.

P.S. Is there some way I can contact you directly? Perhaps send me a direct message through Codeplex, then we can exchange e-mail addresses.

New Post: Cache issue

ramana16 — Fri, 28 Jan 2011 07:49:10 GMT

Dear Chris,

We are using config store on our prod farm and we have a config store at root site collection level and also at every site collection level.

The root site collection contains default key values which may be overridden at site collection level.

For some cases we notice that the values in the config store at the site collection level are being overlooked and the value from root site collection is taken even though there exists value for the same key at site collection level. Have you noticed a problem like this before? the value seems to come from global cache and not local cache.

The app pools are recycled every night. Can it be an issue with cache? Please do provide your valuable inputs.

Regards,

Ramana

New Post: SP 2010 support!

mel2506 — Tue, 14 Dec 2010 16:48:23 GMT

Hi,

I've been using config store in 2007 already and now want to use it in 2010 as well.

Before I convert it myself like Mats (was that successful?) I'd like to know if there's already a version for 2010 available?

Thx, Mel

New Post: Encrypted Values

TubaTech — Fri, 24 Sep 2010 14:39:05 GMT

I implemented something similar in a past project, so I have a suggestion for your project.

Add another column called "Encrypted" as a boolean field. From there, you can have an event handler encrypt (Base64 atleast) the value of the configuration entry upon creation. And then just have the API decrypt the value.

That way, you could possibly store passwords and other sensitive material in the list.

New Post: Not using local 'Config Store' list when browsing with a "Reader"

pealmasa — Tue, 25 May 2010 10:46:49 GMT

Hi,

I think I found the problem with readers unable to read even with RunWithElevatedPrivileges. It is an anonymous permissions conflict.

The anonymouspermmask and anonymouspermmask64 had mask instead an empty mask. On configstore list settings the anonymous is disabled yet the list had perm mask. To solve this set anonymous, say for view, then hit ok. Then remove anonymous again. It should work.

Regards

New Post: Hierarchical Model Config Store

chrisobrien — Sun, 16 May 2010 21:54:12 GMT

Sure.

The idea is basically that the Config Store Feature is activated in every site collection where you might want to use it - this will provision the list etc. so entries can be added in each site, to suit the configuration required in each area. Then, when a value is requested, if an entry exists in the current site it will be returned, otherwise the entry is returned from the 'master' site (from a URL defined in web.config) - this is the 'hierarchical' aspect. It should also be possible to use the Config Store across multiple web applications in this way.

One thing to look out for is web.config entries being provisioned each time the Feature is activated. There's a Feature property which controls this (this is mentioned in the readme), which you might need to switch to 'False' (and rebuild the WSP/deploy) if it isn't already - I changed my mind on the best default between releases.

Feel free to come back here if you need further help.

Thanks,

Chris.

P.S. Note that the same code also works fine with just a single Config Store instance.