无法配置XML配置存储 [英] Cannot configure XML config store

查看:91
本文介绍了无法配置XML配置存储的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

嗨 -


我们正在尝试迁移到XML配置存储,因为SQL存储在数据库故障转移事件中不能很好地工作。我们认为这很容易,但我根本无法工作!我见过几个

个线程
,讨论使用XML配置存储时的问题。似乎有一个共识,sysprepping一个新的SID可能会工作,但这对我来说似乎是疯狂的:-)我得到的堆栈跟踪是在
缓存中配置第一个节点时的最后一步,它说: / p>

 System.Management.Automation.CmdletInvocationException:ErrorCode< PermissionsError> ;:SubStatus< ES0001> ;:无法在配置存储上设置权限: ErrorCode< UnspecifiedErrorCode> ;:SubStatus< ES0001>:在网络共享上配置权限时出错:访问被拒绝。有关手动配置存储权限的信息,请参阅产品文档。 ---> Microsoft.ApplicationServer.Caching.DataCacheException:ErrorCode< PermissionsError> ;:SubStatus< ES0001>:无法在配置存储上设置权限:ErrorCode< UnspecifiedErrorCode> ;:SubStatus< ES0001>:在网络共享上配置权限时出错:访问被拒绝。有关手动配置存储权限的信息,请参阅产品文档。 ---> Microsoft.ApplicationServer.Caching.DataCacheException:ErrorCode< UnspecifiedErrorCode> ;:SubStatus< ES0001>:在网络共享上配置权限时出错:访问被拒绝---> System.ComponentModel.Win32Exception:Microsoft.ApplicationServer.Caching.Configuration.NetworkShareManagement.NetworkShare.GetAccessControl(String server,String shareName)
at Microsoft.ApplicationServer.Caching.Configuration.Commands.RegisterCacheHostCommand,拒绝访问
.SetNetworkSharePermissions(String serverName,String shareName,IdentityReference [] ids)
---内部异常堆栈跟踪结束---
at Microsoft.ApplicationServer.Caching.Configuration.Commands.RegisterCacheHostCommand.SetNetworkSharePermissions(String serverName,String shareName,IdentityReference [] ids)
at Microsoft.ApplicationServer.Caching.Configuration.Commands.RegisterCacheHostCommand.SetNetworkSharePermissions(String velocityConfigPath,String account,String serviceHost)
at Microsoft.ApplicationServer.Caching.Configuration .Commands.RegisterCacheHostCommand.BeginProcessing()
---内部异常堆栈跟踪结束--- System.Management.A上的
utomation.MshCommandRuntime.ThrowTerminatingError(ErrorRecord errorRecord)
---内部异常堆栈跟踪结束---
在System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)
at System.Management.Automation.Runspaces.Pipeline.Invoke()
at System.Management.Automation.PowerShell.Worker.ConstructPipelineAndDoWork(Runspace rs,Boolean performSyncInvoke)
at System.Management.Automation.PowerShell.Worker .CreateRunspaceIfNeededAndDoWork(Runspace rsToUse,Boolean isSync)
在System.Management.Automation.PowerShell.CoreInvoke [TOutput](IEnumerable input,PSDataCollection`1输出,PSInvocationSettings设置)
在System.Management.Automation.PowerShell .Invoke(IEnumerable输入,PSInvocationSettings设置)
at System.Management.Automation.PowerShell.Invoke()
at Microsoft.ApplicationServer.Configuration.DistributedCacheProxy.RegisterCacheHost(DistributedCacheSettings settings)
at Microsoft。应用licationServer.Configuration.DistributedCacheNodePage.backgroundWorker_DoWork(Object sender,DoWorkEventArgs e)


服务器正在运行2008 R2数据中心。他们都在一个领域。由于权限异常,我尝试将以下所有用户添加到共享中,但这些用户都没有更改抛出的异常。



  • 每个人
  • 匿名登录
  • 网络服务
  • AD机器名称本身(domain \machineName $)

还有什么我可以尝试sysprepping机器?我们目前正在我们的暂存环境中运行它,但我们也希望在某些时候在我们的实时环境中运行它,这似乎是非常极端的唯一修复。


非常感谢。


 

解决方案

好的,我们能够解决这个问题。相当迂回的方式。


我们首先注意到虽然它抛出了错误,但实际上是在文件共享上正确创建了ClusterConfig.xml。它只是不会完成配置向导。


所以我们创建了一个新的集群,并为该集群添加了两台机器。这三个中的每一个都正确地将它们的详细信息添加到ClusterConfig文件中,但是无法启动。然后我做了一个Export-CacheClusterConfig,并手动添加了< hosts>元素到
< dataCache>元件。我发明了随机的"hostid"。数字,似乎没有任何不良影响。然后我将Import-CacheClusterConfig单独配置文件到每个主机。


这似乎使它工作。多奇怪。希望这将在1.1版本中修复。


 


 


Hi -

We're trying to move to an XML config store, because the SQL store doesn't work very well the event of a database failover. We thought it would be easy, but I can't get it to work at all! I've seen a few threads that talk about problems when using the XML configuration store. There seemed to be a consensus that sysprepping a new SID might work, but this seems bonkers to me :-) The stacktrace I get is on the final step when configuring the first node in the cache, and it says:

System.Management.Automation.CmdletInvocationException: ErrorCode<PermissionsError>:SubStatus<ES0001>:Could not set permissions on configuration store : ErrorCode<UnspecifiedErrorCode>:SubStatus<ES0001>:Error occurred while configuring permissions on network share: Access is denied. Refer to the product documentation for manually configuring the store permissions. ---> Microsoft.ApplicationServer.Caching.DataCacheException: ErrorCode<PermissionsError>:SubStatus<ES0001>:Could not set permissions on configuration store : ErrorCode<UnspecifiedErrorCode>:SubStatus<ES0001>:Error occurred while configuring permissions on network share: Access is denied. Refer to the product documentation for manually configuring the store permissions. ---> Microsoft.ApplicationServer.Caching.DataCacheException: ErrorCode<UnspecifiedErrorCode>:SubStatus<ES0001>:Error occurred while configuring permissions on network share: Access is denied ---> System.ComponentModel.Win32Exception: Access is denied
   at Microsoft.ApplicationServer.Caching.Configuration.NetworkShareManagement.NetworkShare.GetAccessControl(String server, String shareName)
   at Microsoft.ApplicationServer.Caching.Configuration.Commands.RegisterCacheHostCommand.SetNetworkSharePermissions(String serverName, String shareName, IdentityReference[] ids)
   --- End of inner exception stack trace ---
   at Microsoft.ApplicationServer.Caching.Configuration.Commands.RegisterCacheHostCommand.SetNetworkSharePermissions(String serverName, String shareName, IdentityReference[] ids)
   at Microsoft.ApplicationServer.Caching.Configuration.Commands.RegisterCacheHostCommand.SetNetworkSharePermissions(String velocityConfigPath, String account, String serviceHost)
   at Microsoft.ApplicationServer.Caching.Configuration.Commands.RegisterCacheHostCommand.BeginProcessing()
   --- End of inner exception stack trace ---
   at System.Management.Automation.MshCommandRuntime.ThrowTerminatingError(ErrorRecord errorRecord)
   --- End of inner exception stack trace ---
   at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)
   at System.Management.Automation.Runspaces.Pipeline.Invoke()
   at System.Management.Automation.PowerShell.Worker.ConstructPipelineAndDoWork(Runspace rs, Boolean performSyncInvoke)
   at System.Management.Automation.PowerShell.Worker.CreateRunspaceIfNeededAndDoWork(Runspace rsToUse, Boolean isSync)
   at System.Management.Automation.PowerShell.CoreInvoke[TOutput](IEnumerable input, PSDataCollection`1 output, PSInvocationSettings settings)
   at System.Management.Automation.PowerShell.Invoke(IEnumerable input, PSInvocationSettings settings)
   at System.Management.Automation.PowerShell.Invoke()
   at Microsoft.ApplicationServer.Configuration.DistributedCacheProxy.RegisterCacheHost(DistributedCacheSettings settings)
   at Microsoft.ApplicationServer.Configuration.DistributedCacheNodePage.backgroundWorker_DoWork(Object sender, DoWorkEventArgs e)

The servers are running 2008 R2 datacenter. They're all in a domain. Because of the permission exception, I have tried adding all the following users to the share, but none of these have changed the exception being thrown.

  • Everyone
  • Anonymous logon
  • Network service
  • The AD machine name itself (domain\machineName$)

What else can I try short of sysprepping the machine? We're running this currently in our staging environment, but we will want to do it in our live environment too at some point, and this seems to be pretty extreme as the only fix.

Many thanks.

 

解决方案

OK, we were able to fix this in a rather roundabout way.

We first noticed that although it was throwing the error, it was actually creating the ClusterConfig.xml on the fileshare correctly. It just wouldn't finish the configuration wizard.

So we created a new cluster, and added two machines to that cluster. Each of these 3 correctly added their details to the ClusterConfig file, but wouldn't start. I then did an Export-CacheClusterConfig, and manually added the <hosts> element to the <dataCache> element. I invented random "hostid" numbers, which doesn't seem to have had any ill effects. And I then Import-CacheClusterConfig that config file to each host individually.

That seems to have made it work. How bizarre. Hopefully this will get fixed in the 1.1 release.

 

 


这篇关于无法配置XML配置存储的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆