DTS:Property" with error 0x8009000B

最新推荐文章于 2023-02-24 13:43:58 发布
转载 最新推荐文章于 2023-02-24 13:43:58 发布 · 197 阅读 · 0

本文讨论了一个关于XML节点DTS:Property解密失败的问题，错误代码为0x8009000B，提示密钥状态不正确。通过对错误信息的分析，尝试找出可能的原因及解决方法。
cuixie2370
关注
设备树学习（二、设备树dts/dtsi格式）
To_run_away的博客
02-14 2万+
说明：后续的博文参考自韦东山老师的设备树视屏，老师用的是2440的开发板，我用的是s5pv210的开发板。原理一样 一、前言 简单的说，如果要使用Device Tree，首先用户要了解自己的硬件配置和系统运行参数，并把这些信息组织成Device Tree source file。通过DTC（Device Tree Compiler），可以将这些适合人类阅读的Device Tree sou...
protected XML node "DTS:Password" with error 0x8009000B "
cuixie2370的博客
06-02 166
Juarez PCE OTS 10.13.8.96Server Name : MXOSV-OTSDB02Job Name : TO_OTSJob Status : FailedDateTime : 20100601 10:43:...
Description: Failed to decrypt protected XML node "DTS:Password" with error 0x8009000B "Key not valid for use in specified state
记录那些曾今的迷茫
06-14 3483
用vs运行时正常，但是用sql server job运行时出现如下的错误，只要按图设置package属性即可 
SQL SERVER MaintanencePlan 失败 无法解密受保护的 XML 节点“DTS:Password”，错误为 0x8009000B解决
sherrysy720的专栏
08-31 5260
使用工具生成的备份JOB，运行很多个月都是正常，出差回来却被另一个数据库人员告知有段时间没有运行了，所以停用了。奇怪查看历史日志如下：   错误提示里有密钥等等，但是我没有生成过密钥什么的，想来错误原因是由于包指定的保护级别有问题。 解决办法： 1.登陆服务器，点
Failed to decrypt protected XML node "DTS:Property" with error 0x8009000B 错误的解决
weixin_30786617的博客
12-13 432
在部署执行SSIS包的时候出现这个错误Failed to decrypt protected XML node "DTS:Property" with error 0x8009000B "Key not valid for use in specified state.". You may not be authorized to access this information. This err...
SSIS 無法將保護的 XML 節點 "DTS:Password" 解密，錯誤為 0x8009000B "機碼用在特定狀態時無效...
aynbxl8574的博客
03-25 958
发现之前部署的SSIS，执行失败，查看日志 來源: 描述: 無法將保護的 XML 節點 "DTS:Password" 解密，錯誤為 0x8009000B "機碼用在特定狀態時無效。"。您可能沒有存取這項資訊的權限。當發生密碼編譯錯誤時，就會發生這個錯誤。請確認有正確的金鑰。 錯誤結束 錯誤: 2016-03-25 07:08:05.39 代碼: 0xC...
root@RK356x-Tronlong:~# dmesg | grep dwmac [ 0.698022] rk_gmac-dwmac fe2a0000.ethernet: Looking up phy-supply from device tree [ 0.698042] rk_gmac-dwmac fe2a0000.ethernet: Looking up phy-supply property in node /ethernet@fe2a0000 failed [ 0.698065] rk_gmac-dwmac fe2a0000.ethernet: no regulator found [ 0.698095] rk_gmac-dwmac fe2a0000.ethernet: clock input or output? (input). [ 0.698113] rk_gmac-dwmac fe2a0000.ethernet: TX delay(0x3c). [ 0.698128] rk_gmac-dwmac fe2a0000.ethernet: RX delay(0x2f). [ 0.698146] rk_gmac-dwmac fe2a0000.ethernet: integrated PHY? (no). [ 0.698190] rk_gmac-dwmac fe2a0000.ethernet: cannot get clock clk_mac_ref [ 0.698216] rk_gmac-dwmac fe2a0000.ethernet: clock input from PHY [ 0.698464] rk_gmac-dwmac fe2a0000.ethernet: init for RMII [ 0.698710] rk_gmac-dwmac fe2a0000.ethernet: User ID: 0x30, Synopsys ID: 0x51 [ 0.698729] rk_gmac-dwmac fe2a0000.ethernet: DWMAC4/5 [ 0.698747] rk_gmac-dwmac fe2a0000.ethernet: DMA HW capability register supported [ 0.698756] rk_gmac-dwmac fe2a0000.ethernet: RX Checksum Offload Engine supported [ 0.698770] rk_gmac-dwmac fe2a0000.ethernet: TX Checksum insertion supported [ 0.698783] rk_gmac-dwmac fe2a0000.ethernet: Wake-Up On Lan supported [ 0.698821] rk_gmac-dwmac fe2a0000.ethernet: TSO supported [ 0.698836] rk_gmac-dwmac fe2a0000.ethernet: Enable RX Mitigation via HW Watchdog Timer [ 0.698851] rk_gmac-dwmac fe2a0000.ethernet: TSO feature enabled [ 2.970597] rk_gmac-dwmac fe2a0000.ethernet eth0: Could not attach to PHY [ 2.970618] rk_gmac-dwmac fe2a0000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19)
08-08
在 Rockchip RK356x 平台上，`rk_gmac-dwmac fe2a0000.ethernet eth0: Could not attach to PHY (error: -19)` 错误通常表示以太网控制器无法正确检测到 PHY 设备。错误代码 `-19` 对应的是 `ENODEV`，意味着没有...
root@RK356x-Tronlong:~# dmesg | grep -i gmac [ 0.699601] rk_gmac-dwmac fe2a0000.ethernet: Looking up phy-supply from device tree [ 0.699620] rk_gmac-dwmac fe2a0000.ethernet: Looking up phy-supply property in node /ethernet@fe2a0000 failed [ 0.699642] rk_gmac-dwmac fe2a0000.ethernet: no regulator found [ 0.699677] rk_gmac-dwmac fe2a0000.ethernet: clock input or output? (input). [ 0.699694] rk_gmac-dwmac fe2a0000.ethernet: TX delay(0x3c). [ 0.699709] rk_gmac-dwmac fe2a0000.ethernet: RX delay(0x2f). [ 0.699728] rk_gmac-dwmac fe2a0000.ethernet: integrated PHY? (no). [ 0.699777] rk_gmac-dwmac fe2a0000.ethernet: cannot get clock clk_mac_ref [ 0.699803] rk_gmac-dwmac fe2a0000.ethernet: clock input from PHY [ 0.700048] rk_gmac-dwmac fe2a0000.ethernet: init for RMII [ 0.700312] rk_gmac-dwmac fe2a0000.ethernet: User ID: 0x30, Synopsys ID: 0x51 [ 0.700332] rk_gmac-dwmac fe2a0000.ethernet: DWMAC4/5 [ 0.700350] rk_gmac-dwmac fe2a0000.ethernet: DMA HW capability register supported [ 0.700363] rk_gmac-dwmac fe2a0000.ethernet: RX Checksum Offload Engine supported [ 0.700377] rk_gmac-dwmac fe2a0000.ethernet: TX Checksum insertion supported [ 0.700389] rk_gmac-dwmac fe2a0000.ethernet: Wake-Up On Lan supported [ 0.700432] rk_gmac-dwmac fe2a0000.ethernet: TSO supported [ 0.700448] rk_gmac-dwmac fe2a0000.ethernet: Enable RX Mitigation via HW Watchdog Timer [ 0.700463] rk_gmac-dwmac fe2a0000.ethernet: TSO feature enabled [ 2.982096] rk_gmac-dwmac fe2a0000.ethernet eth0: Could not attach to PHY [ 2.982111] rk_gmac-dwmac fe2a0000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19) root@RK356x-Tronlong:~# dmesg | grep -i mdio [ 0.858603] mdio_bus stmmac-0: MDIO device at address 0 is missing.
08-08
reg = <0x1>; reset-gpios = ; reset-delay-us = ; }; }; ``` 如果复位引脚未正确配置或时序不符合 PHY 数据手册要求，也会导致“**Cannot attach to PHY**”的问题。 ### 3.3 检查 MDIO 总线通信状态 驱动在...
ERROR: (0)[1.697289][ADSP]: mt_scp_audio_dram_subregion invalid param dram id:4 off:0x0 sz:0 ERROR: (6)[7.214830][AUDIO]: audio_smc_handler, Wrong request_ops, request_ops = 7, init_done = 0 ERROR: (6)[7.214841][AUDIO]: audio_smc_handler, Wrong request_ops, request_ops = 3, init_done = 0 ERROR: (6)[7.219911][AUDIO]: audio_smc_handler, Wrong request_ops, request_ops = 4, init_done = 0 ERROR: (2)K:[51.394155][gps_kernel_handler] unknown request_ops=0 ERROR: (2)K:[51.395095][gps_kernel_handler] unknown request_ops=3 NOTICE: (3)K:[171.761777]GDL[E:0] [gps_dl_hw_get_dsp_ms_counter:213]: abnormal, p_tcxo_low = dead0001, p_tcxo_high = dead0001 ERROR: (6)K:[217.756759][gps_kernel_handler] unknown request_ops=0 ERROR: (1)K:[217.757574][gps_kernel_handler] unknown request_ops=3 NOTICE: (1)K:[338.131491]GDL[E:0] [gps_dl_hw_get_dsp_ms_counter:213]: abnormal, p_tcxo_low = dead0001, p_tcxo_high = dead0001 ERROR: (7)K:[343.122493][gps_kernel_handler] unknown request_ops=0 ERROR: (7)K:[343.123253][gps_kernel_handler] unknown request_ops=3 NOTICE: (4)K:[363.198458]GDL[E:0] [gps_dl_hw_get_dsp_ms_counter:213]: abnormal, p_tcxo_low = dead0001, p_tcxo_high = dead0001 NOTICE: (0)K:[371.726393][SYSTIMER][SYST0] INTS:0x040687 NOTICE: (0)K:[371.726402][SYSTIMER]CON0:0x1 NOTICE: (0)K:[371.726408][SYSTIMER]VAL0:0x0 NOTICE: (0)K:[371.726414][SYSTIMER][SYST0] CNTCR:0x4490d NOTICE: (0)K:[371.726420][SYSTIMER][SYST0] CNTSR:0x101 NOTICE: (0)K:[371.726426][SYSTIMER][SYST0] ENT0:0x1236bcf08 NOTICE: (0)K:[371.726433][SYSTIMER][SYST0] AST0:0x1236c9cc9 NOTICE: (0)K:[371.726439][SYSTIMER][SYST0] ENT1:0x1236bce12 NOTICE: (0)K:[371.726446][SYSTIMER][SYST0] AST1:0x1236bca1d NOTICE: (0)K:[371.726453][SYSTIMER][SYST0] ENT2:0x12366dfc4 NOTICE: (0)K:[371.726460][SYSTIMER][SYST0] AST2:0x12366db7d NOTICE: (0)K:[371.726466][SYSTIMER][SYST0] DIST:0x0 NOTICE: (0)K:[371.726472][SYSTIMER][SYST0] CNTBUF:0x125480213 NOTICE: (0)K:[371.726479][SYSTIMER][SYST0] CNTCV:0x125480263 NOTICE: (0)K:[371.726511][RGU]MODE:0x25 NOTICE: (0)K:[371.726517][RGU]LENGTH:0xf000 NOTICE: (0)K:[371.726524][RGU]STATUS:0x0 NOTICE: (0)K:[371.726530][RGU]INTERVAL:0xfff NOTICE: (0)K:[371.726536][RGU]NONRST_REG:0x0 NOTICE: (0)K:[371.726542][RGU]NONRST_REG2:0x6c002000 NOTICE: (0)K:[371.726549][RGU]REQ_MODE:0x7500e7 NOTICE: (0)K:[371.726555][RGU]REQ_IRQ_EN:0x750065 NOTICE: (0)K:[371.726562][RGU]EXT_REQ_CON:0x41 NOTICE: (0)K:[371.726568][RGU]DEBUG_CTL:0x0 NOTICE: (0)K:[371.726574][RGU]LATCH_CTL:0xf21e79 NOTICE: (0)K:[371.726581][RGU]LATCH_CTL2:0x2f NOTICE: (0)K:[371.726587][RGU]DEBUG_CTL2:0x0 NOTICE: (0)K:[371.726593][RGU]COUNTER:0xf01fe
最新发布
11-15
ERROR: (0)[1.697289][ADSP]: mt_scp_audio_dram_subregion invalid param dram id:4 off:0x0 sz:0 ERROR: (6)[7.214830][AUDIO]: audio_smc_handler, Wrong request_ops, request_ops = 7, init_done = 0 ... ``` -...
[ 11.923431] cjc8988 3-001a: ASoC: error at snd_soc_dai_set_sysclk on cjc8988.3-001a: -22 [ 11.923435] cjc8988 3-001a: simple-card: set_sysclk error [ 11.923439] fe470000.i2s-cjc8988-hifi: ASoC: error at snd_soc_link_init on fe470000.i2s-cjc8988-hifi: -22 [ 11.923527] asoc-simple-card: probe of i2s0-sound failed with error -22
07-04
[ 11.923527] asoc-simple-card: probe of i2s0-sound failed with error -22 ``` - **错误链**： 1. `cjc8988` 编解码器驱动调用 `snd_soc_dai_set_sysclk` 失败（`-EINVAL`）。 2. `simple-card` 机器驱动因编...
Failed to decrypt protected XML node "DTS:Password" with error 0x8009000B "Key not valid for use in ...
weixin_30725315的博客
02-16 293
解决办法： 使用配置文件，将密码等信息放入配置文件中，运行package时从配置文件读取（配置文件最好存储在一个安全的地方） 将Package的ProtectionLevel改为EncryptSensitiveWithPassword并设置密码，部署后打开CommandLines，会提示输入密码，输入后，运行Package成功。 部署后进入DataSource，勾选需要的DataSour...
【VS】部署出现连接问题
m0_64056100的博客
02-24 468
visual studio部署时的网络服务器连接问题
《BI项目笔记》无法解密受保护的 XML 节点“DTS:Password” 解决办法
weixin_30569153的博客
11-17 522
说明: 无法解密受保护的 XML 节点“DTS:Password”，错误为 0x8009000B“该项不适于在指定状态下使用。”。可能您无权访问此信息。当发生加密错误时会出现此错误。请确保提供正确的密钥。 解决办法：1.在Integration Services中找到要执行的包，右键选择导出包，在导出包属性框中选好导出的路径，保护级别选项上选择“不保存敏感数据”，如下：2.在Integratio...
CryptAcquireContext返回NTE_BAD_KEY_STATE
u014023993的专栏
05-25 3970
我们知道，通过rand函数产生的随机数安全性不高，为了保证随机数的安全性，我们一般会选择一个随机数种子，通过该种子增加破解随机数的难度。C/C++下是如下代码： #include <stdlib.h> #include <time.h> int main() { srand((unsigned)time(NULL)); printf("%d\n",ran...
无法解密受保护的XML节点“DTS:Password”
weixin_30457465的博客
12-27 587
1.sql server 的job执行 ssis的包的时候，报错： 日期,源,严重性,步骤 ID,服务器,作业名称,步骤名称,通知,消息,持续时间,SQL 严重性,SQL 消息 ID,已通过电子邮件通知的操作员,已通过网络发送通知的操作员,已通过寻呼通知的操作员,重试次数12/27/2010 13:04:00,test2712,错误,0,EMMY,test2712,(作业结果),,该作...
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符  | 博主筛选后可见
 
红包 添加红包
表情包 插入表情
表情包 代码片
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值