| Yuanming님의 프로필我的音乐历程사진블로그리스트 | 도움말 |
我的音乐历程Favourate Music Report |
||||||||||||
|
8월 4일 cnBeta.COM_Windows Vista 新闻主题_ WinSAT - Vista中的又一彩蛋WinSAT是什么? 想必大家都用过Windows Vista中的“Windows体验索引”(现在我都觉得这个名字怪怪的),就是Vista系统中用于硬件评分的那个东东。WinSAT是Windows System Assessment Tool的简称,并作为一个基本工具存在于Vista系统当中。此东东主要用于评估Vista系统性能。 怎样来用WinSAT?其实WinSAT不仅只是个命令行程序,她是Windows Vista为我们开放的一个标准接口。我们可以通过调用她(Win32_WinSAT类)来实现自己的应用。 例如,我就写了一个类似于Windows体验索引的脚本:
WinSAT彩蛋WinSAT可谓Vista中的一个彩蛋,我们通过管理员权限打开cmd命令提示符来执行如入命令便可以看到惊人的特效: winsat aurora
winsat d3d -texshader -totalobj 15
winsat d3d -objs C(20) -texshader -totalobj 50
winsat d3d -totalobj 20 -objs C(20) -totaltex 10 -texpobj C(1) -alushader -noalpha -v -time 10
winsat d3d -totalobj 20 -objs C(20) -totaltex 10 -texpobj C(10) -alushader -v -time 10
7월 6일 The hybrid sleep feature and the hibernation feature in Windows Vista may become unavailable after you use the Disk Cleanup ToolSYMPTOMSAfter you use the Disk Cleanup Tool in Windows Vista, you may experience the following symptoms: •You cannot see the Hibernate option in Power Options. •When you use the sleep feature, the computer does not recover its settings if power is lost. CAUSEThis problem occurs when the Disk Cleanup Tool disables the hibernation file. The hibernation file must be enabled to access the hybrid sleep feature and the hibernation feature in Windows Vista. RESOLUTIONTo resolve this problem in Windows Vista, run the powercfg -h on command at a command prompt to enable the hibernate feature and the hybrid sleep feature. To run this command, follow these steps: 1.Click Start 2.Right-click Command Prompt, and then click Run as administrator. 3.Type powercfg -h on, and then press ENTER. APPLIES TO•Windows Vista Enterprise 64-bit Edition •Windows Vista Home Basic 64-bit Edition •Windows Vista Home Premium 64-bit Edition •Windows Vista Ultimate 64-bit Edition •Windows Vista Business •Windows Vista Business 64-bit Edition •Windows Vista Enterprise •Windows Vista Home Basic •Windows Vista Home Basic Beta •Windows Vista Home Premium •Windows Vista Starter •Windows Vista Ultimate Keywords:kbexpertisebeginner kbtshoot kbprb KB928897 6월 24일 获取SqlServer2005表结构(字段,主键,外键,递增,描述) - 楚旋 - 博客园1.获取表的基本字段属性 --获取SqlServer中表结构 运行效果 --获取SqlServer中表结构 主键,及描述 运行效果 --单独查询表递增字段 运行效果 --获取表主外键约束 运行效果 5월 7일 CSS的十八般技巧 w3cn.org
SQL Server 2005中设置Reporting Services发布web报表的匿名访问 - 志坚苍狼 - 博客园一位朋友提出个问题:集成到SQL Server 2005中的Reporting Services已经将报表模板发布到IIS服务器,客户端通过浏览器访问时,默认会弹出Windows集成身份验证的对话框。如果在IIS配置里面把允许匿名(IUSR_**)访问的选项勾选,客户端再次访问的时候,会提示IUSR_** 访问权限不足。 对于这个问题,除了要设置IIS允许匿名访问外,还需要设置Reporting Services站点的访问权限和SQL Server中数据源的用户访问权限。 下面我将把需要做的步骤列出来,大家注意前提是使用Visual Studio .NET 2005 已经正确的发布了Reporting Services制作的报表模板到IIS服务器。 第一步:在运行IIS的Web服务器的本地访问http://localhost/reports ,这是Reporting Services的管理站点,在Properties(属性)页面下添加一个只有Browser(浏览者)权限的新Role(角色)。注意新角色的用户名称即IUSR_** (匿名用户)。 1、 点击“New Role Assignment”(分配新角色) 2、 弹出的IE窗口中,Group or user name(组或用户名) 文本框输入IUSR_** (匿名用户)。 3、 勾选Browser(浏览者)权限,点OK按钮确定。 4、 返回到http://localhost/reports 页面中会新出现添加的Role(角色)。
在运行SQL Servier 2005 的数据库服务器中,打开Microsoft SQL Server Management Studio。在Object Explorer(对象浏览器)中找到Security(安全)目录下的Logins(登录),在Logins(登录)图标上面单击右键快捷菜单上,选择New Login…(新登录),弹出的对话框中设置。 1、 右键菜单选择New Login…(新登录)。 2、 在Windows authentication 中的Login Name(登录名)文本框,输入IUSR_**(匿名用户)。 3、 在Defaults(默认)的Database(数据库)下拉列表框找到Reporting Services制作的报表模板的数据源数据库。 4、 在Select a page(选择一个页面)列表中点击“Database Access”(数据库访问)。 1、 选择数据库 2、 OK确定
第四步:还是在Microsoft SQL Server Management Studio中,找到Reporting Services的数据源数据库,在“Security”(安全)下的“Users”(用户)下,找到刚才添加的IUSR_**(匿名用户)。设置他对该数据库的访问权限。 1、 在IUSR_**(匿名用户)上右键菜单选Properties(属性)。 2、 弹出的对话框中选择Permissions(许可)。 3、 点击“Add Objects…”(增加对象)。 4、 再次弹出的对话框中选择“Add objects of types”。
还是第四步:弹出的对话框中选Databases(数据库的)。 1、 Select Object Types(选择对象类型)对话框选择“Databases”(数据库的)。 2、 OK确定。
还是第四步:选择IUSR_**(匿名用户)对该数据库许可的操作。 1、 在Permissions for *** 列表中,找到Select,勾选。(注:你会看到Connect后面是默认勾选的,因为前面设置的默认登录到数据库就是该数据库) 2、 OK确定。
第五步:打开IIS管理器,设置ReportServer虚拟目录为匿名访问。 1、 打开IIS管理器,在ReportServer虚拟目录上单击邮件选择“Properties”(属性)。 2、 在“目录安全性”页面,找到“身份验证和访问控制”,点击“编辑...”。 3、 在弹出的“身份验证方法”对话框,勾选“启用匿名访问”。 4、 在“用户访问需经过身份验证”的位置,默认是选中“集成Windows身份验证”。在这儿可以不用修改它。如果去掉了“集成Windows身份验证”前面的勾选,则本机(IIS服务器所在机器)对Reporting Services Web站点的访问也成了匿名访问。 5、 OK确定。
第六步:再通过其他的客户端机器访问Reporting Services Web站点,则不再出现Windows用户登录窗口。对Reporting Services Web站点的访问已经更改为匿名用户的访问。
但是注意,有个问题会同时出现。我们再次访问http://localhost/reports 时发现,将不能对Reporting Services的权限分配。打开http://localhost/reports 能够看到的是只有Contents(内容)一个分类页面的选项,“Properties”(属性)选项则不会出现了。这该是Reporting Services产品刻意设计的,因为所有的用户都可以匿名访问Web站点了,权限如果放开了随便改肯定不行。
再一想,http://localhost/reports 和 http://localhost/reportserver 这两个虚拟目录对应的物理目录是不同的。一个http://localhost/reports 对应的是C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportManager ;而http://localhost/reportserver 对应的是C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer。刚才对\reportserver的匿名访问权限的修改又怎么影响到\reports 了呢?? 如果再需要修改\reports的“Properties”(属性),唯一能做的就是重新打开IIS的管理器,去掉\reportserver中的“匿名访问”选项,再来修改。修改后,再将\reportserver改为“匿名访问”。 SQL Server 2005中设置Reporting Services发布web报表的匿名访问 - 志坚苍狼 - 博客园 On a computer that has Microsoft Data Access Components 2.8 installed, an application receives an incorrect value for the identity column from a SQL Server 2005 databaseSYMPTOMSConsider the following scenario. You create a table that has an identity column in a Microsoft SQL Server 2005 database. You configure a merge replication on the table. An application uses Microsoft ActiveX Data Objects (ADO) to insert a row in the table. Then, the application retrieves the inserted row. However, an incorrect value is returned for the identity column. • • • This problem does not occur in a Microsoft SQL Server 2000 database. CAUSEThe replication process creates insert triggers in the table. When data is inserted in the table, the insert triggers use the @@IDENTITY variable instead of the SCOPE_IDENTITY function. Therefore, the @@IDENTITY variable may return an identity value that is not in the current table. RESOLUTIONHotfix informationWindows XPA supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Windows XP service pack that contains this hotfix.To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site: http://go.microsoft.com/?linkid=6294451 (http://go.microsoft.com/?linkid=6294451) Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site: http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support) PrerequisitesTo apply this hotfix, you must have Windows XP Service Pack 2 installed on the computer. For more information, click the following article number to view the article in the Microsoft Knowledge Base:322389 (http://support.microsoft.com/kb/322389/) How to obtain the latest Windows XP service pack Restart requirementYou must restart the computer after you apply this hotfix.Hotfix replacement informationThis hotfix does not replace any other hotfixes.File informationThe English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.File name Msadce.dll Windows Server 2003A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Windows Server 2003 service pack that contains this hotfix.To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site: http://go.microsoft.com/?linkid=6294451 (http://go.microsoft.com/?linkid=6294451) Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site: http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support) PrerequisitesTo apply this hotfix, you must have Windows Server 2003 Service Pack 1 or Windows Server 2003 Service Pack 2 installed on the computer. For more information, click the following article number to view the article in the Microsoft Knowledge Base:889100 (http://support.microsoft.com/kb/889100/) How to obtain the latest service pack for Windows Server 2003 Restart requirementYou must restart the computer after you apply this hotfix.Hotfix replacement informationThis hotfix does not replace any other hotfixes.File informationThe English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.Windows Server 2003 with Service Pack 1, x86-based versions File name Msadce.dll Windows Server 2003 with Service Pack 2, x86-based versions File name Msadce.dll Windows Server 2003 with Service Pack 1, Itanium-based versions File name Msadce.dll Wmsadce.dll Windows Server 2003 with Service Pack 2, Itanium-based versions File name Msadce.dll Wmsadce.dll Windows Server 2003, x64-based versions File name Msadce.dll Wmsadce.dll Windows Server 2003 with Service Pack 2, x64-based versions File name Msadce.dll Wmsadce.dll Microsoft Data Access Components 2.8A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next MDAC 2.8 service pack that contains this hotfix.To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site: http://go.microsoft.com/?linkid=6294451 (http://go.microsoft.com/?linkid=6294451) Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site: http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support) PrerequisitesTo apply this hotfix, you must have MDAC 2.8 Service Pack 1 installed on the computer.Restart requirementYou must restart the computer after you apply this hotfix.Hotfix replacement informationThis hotfix does not replace any other hotfixes.File informationThe English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.File name Msadce.dll Msadco.dll Msado15.dll Msadomd.dll Msadox.dll Msdasql.dll Msjro.dll Odbcbcp.dll Oledb32.dll Sqloledb.dll Sqlsrv32.dll STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. MORE INFORMATIONThe SCOPE_IDENTITY function and the @@IDENTITY variable return the last identity values that are generated in any table in the current session. However, the SCOPE_IDENTITY function returns values that are inserted only within the current scope. The @@IDENTITY variable does not limit the insertion to a specific scope. • • In this scenario, the @@IDENTITY variable and the SCOPE_IDENTITY function return different values when a row is inserted in Table1. The @@IDENTITY variable returns the last identity column value that is inserted across any scopes in the current session. In this case, the @@IDENTITY variable returns the identity value that is inserted in Table2. However, the SCOPE_IDENTITY function returns the identity value that is inserted in Table1, because the SCOPE_IDENTITY function returns the value that is last inserted in the same scope. The SCOPE_IDENTITY function returns the NULL value if the function is invoked before any INSERT statements that are made to an identity column occur in the scope. 824684 (http://support.microsoft.com/kb/824684/LN/) Description of the standard terminology that is used to describe Microsoft software updates ASP.NET Debugging : ASP.NET Tips: What to gather to troubleshoot – part 3 – CrashDefining an IIS CrashA Crash in IIS occurs when an IIS process (INETINFO.EXE, DLLHOST.EXE, W3WP.EXE) terminates unexpectedly. A Crash typically happens when there is an Unhandled Exception caused by an Access Violation, Stack Overflow, etc. In these situations, the operating system catches the exception and terminates the process. Dr. Watson is the default debugger to monitor for process failures in Windows. It can generate a Dump File and a Log File to document a failure in a process. Run drwtsn32 from Start -> Run to view the settings and file location. You can then look at the drwtsn32.log and user.dmp files. To troubleshoot, we attach a debugger to the process and catch the exception before the operating system. Troubleshooting Steps1. Install the Debug Diagnostic tool http://www.iis.net/downloads/default.aspx?tabid=34&g=6&i=1286 The default install path is C:\Program Files\DebugDiag and can be changed during the installation. 2. Check Leave Running When Idle (IIS5, IIS5.1) with the following steps:
3. Uncheck Debug Exception Catching (IIS5 and IIS5.1) with the following steps:
4. Disable Health Monitoring (IIS6) with the following steps:
5. Restart IIS 6. Create a Crash Rule with the following steps: IIS5
IIS6
Notice the Status is Active. The Userdump Count will increase each time a dump file is created. 7. Analyze the Dump by selecting the Advanced Analysis tab and clicking Add Data Files. When the .dmp is added, select the Crash/Hang Analyzers script and click Start Analysis. When finished, a report (.mht) will be created in C:\Program Files\DebugDiag\Reports and displayed in Internet Explorer with the results and recommendations. If using custom DLL’s, the Symbol path (Tools menu -> Options and Settings -> Symbol Search Path) to the custom PDB files can be added. 8. Compress the Data using DebugDiag (Tools menu -> Create Increment Cabinet File) and analyze this file. ASP.NET Debugging : ASP.NET Tips: What to gather to troubleshoot – part 3 – Crash |
|
||||||||||
|
|