Hopefully this is a simple question, but it's vexing me. When I use the Export Settings wizard in SQL Server Management Studio (v18.4) it presents options that I don't recognize from the Tools|Options window. These are numeric options, like, #3600, #2018, #2001, etc.
If I don't uncheck all of them before I export, I get a slew of errors.
Your settings were exported, but there were some errors.
Error 1: Failed to export settings for '#20116' [code 6714]
Error 2: Failed to export settings for '#100' [code 6714]
Error 3: Failed to export settings for '#1010' [code 6714]
Error 4: Failed to export settings for '#1001' [code 6714]
Error 5: Failed to export settings for 'Start Page' [code 922]
Error 6: Failed to export settings for '#20133' [code 844]
Error 7: Failed to export settings for '1050' [code 844]
Error 8: Failed to export settings for '#3600' [code 844]
Error 9: Failed to export settings for '2015' [code 844]
Error 10: Failed to export settings for '2001' [code 844]
Error 11: Failed to export settings for '2011' [code 844]
Error 12: Failed to export settings for '2012' [code 844]
Error 13: Failed to export settings for '2013' [code 844]
But, the first line implies that, maybe I'm ok. But, if I try to import the file just I just exported, I get...
Your settings were imported, but there were some errors.
Error 1: An error occurred while importing settings for 'Start Page' [code 5302].
Error 2: An error occurred while importing settings for '#20116' [code 5297].
Error 3: An error occurred while importing settings for '#100' [code 5297].
Error 4: An error occurred while importing settings for '#1010' [code 5297].
Error 5: An error occurred while importing settings for '#1001' [code 5297].
More importantly, some of the keyboard shortcuts present when I exported, are not reloaded with the import.
SSMS Export Wizard Snapshot
My question is two-part.
1) What are these options?
2) Is there an easy/easier way for me to bypass/remove them?
Thanks in advance!
It looks like these errors could be due to settings left over from an older version of SSMS.
Reseting your settings might resolve the errors. See this for more info.
Related
I am not able to access the file open dialog in Selenium IDE 2.9.1 (Firefox 48.0, Win 10). File > Open results in this error message:
There was an unexpected error. Msg: NS_ERROR_FILE_UNRECOGNIZED_PATH: Component returned failure code: 0x80520001 (NS_ERROR_FILE_UNRECOGNIZED_PATH) [nsILocalFile.initWithPath]
Url: chrome://selenium-ide/content/file-utils.js, line: 32
FileUtils.getFile#chrome://selenium-ide/content/file-utils.js:32:5
showFilePicker#chrome://selenium-ide/content/tools.js:102:31
Application.prototype.loadTestCaseWithNewSuite#chrome://selenium-ide/content/application.js:259:20
Editor.prototype.loadRecentTestCase#chrome://selenium-ide/content/editor.js:489:5
Editor.controller.doCommand#chrome://selenium-ide/content/editor.js:366:9
goDoCommand#chrome://global/content/globalOverlay.js:100:7
oncommand#chrome://selenium-ide/content/selenium-ide.xul:1:1
File > Open Test Suite results in a shorter error:
error loading test suite: [Exception... "Component returned failure code: 0x80520001 (NS_ERROR_FILE_UNRECOGNIZED_PATH) [nsILocalFile.initWithPath]" nsresult: "0x80520001 (NS_ERROR_FILE_UNRECOGNIZED_PATH)" location: "JS frame :: chrome://selenium-ide/content/file-utils.js :: FileUtils.getFile :: line 32" data: no]
Does anyone have a clue what's wrong here?
In a new Firefox Tab type in about:config, and once in there search for: extensions.selenium-ide.testCaseDirectory and extensions.selenium-ide.testSuiteDirectory Check the file path there and make sure it is a valid one. They control the default location you start at when opening files, could be an issue with that.
I'm installing SSMS 2014 but while installing I'm getting below error:-
"There is a problem with this Windows Installer package. A DLL required
for this installation to complete could not be run. Contact your
support personnel or package vendor."
Can anyone tell me what is the problem?
Here is the error log:
Detailed results:
Feature: Management Tools - Complete
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: SQL Server Native Client Access Component
Component error code: 1723
Component log file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150528_153228\sqlncli_Cpu64_1.log
Error description: There is a problem with this Windows Installer package. A DLL required for this installation to complete could not be run. Contact your support personnel or package vendor.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=sqlncli.msi%40RollbackCleanup%401723
Feature: Client Tools Connectivity
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: SQL Server Common Files
Component error code: 2331
Component log file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150528_153228\sql_common_core_Cpu64_1.log
Error description: The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2331.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=sql_common_core.msi%40Do_LogInstallStart_64%402331
Feature: Client Tools SDK
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: SQL Server Native Client Access Component
Component error code: 1723
Component log file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150528_153228\sqlncli_Cpu64_1.log
Error description: There is a problem with this Windows Installer package. A DLL required for this installation to complete could not be run. Contact your support personnel or package vendor.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=sqlncli.msi%40RollbackCleanup%401723
Feature: Client Tools Backwards Compatibility
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: SQL Server Common Files
Component error code: 2331
Component log file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150528_153228\sql_common_core_Cpu64_1.log
Error description: The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2331.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=sql_common_core.msi%40Do_LogInstallStart_64%402331
Feature: Management Tools - Basic
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: SQL Server Native Client Access Component
Component error code: 1723
Component log file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150528_153228\sqlncli_Cpu64_1.log
Error description: There is a problem with this Windows Installer package. A DLL required for this installation to complete could not be run. Contact your support personnel or package vendor.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=sqlncli.msi%40RollbackCleanup%401723
Feature: SQL Client Connectivity
Status: Failed: see logs for details
Reason for failure: An error occurred during the setup process of the feature.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: SQL Server Native Client Access Component
Component error code: 1723
Component log file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150528_153228\sqlncli_Cpu64_1.log
Error description: There is a problem with this Windows Installer package. A DLL required for this installation to complete could not be run. Contact your support personnel or package vendor.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=sqlncli.msi%40RollbackCleanup%401723
Feature: SQL Client Connectivity SDK
Status: Failed: see logs for details
Reason for failure: An error occurred during the setup process of the feature.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: SQL Server Native Client Access Component
Component error code: 1723
Component log file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150528_153228\sqlncli_Cpu64_1.log
Error description: There is a problem with this Windows Installer package. A DLL required for this installation to complete could not be run. Contact your support personnel or package vendor.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=sqlncli.msi%40RollbackCleanup%401723
I solved this problem by NOT putting in a DEFAULT target server URL when prompted. It is an optional field, so leave it blank, click next, and the installation completes without issue. You can add that link later once the application installs.
Try installing it as administrator. Right click on setup.exe file and click run as administrator.
Command line:
"C:\Program Files (x86)\Microsoft Fxcop 10.0\FxCopCmd.exe" /file:XXX.exe /out:fxcop-report.xml /outxsl:none /forceoutput /searchgac /assemblyCompareMode:StrongNameIgnoringVersion /verbose
Error from report:
<Type>Microsoft.FxCop.Common.AssemblyLoadException</Type>
<ExceptionMessage>Could not load XXX.</ExceptionMessage>
<InnerType>Microsoft.FxCop.Sdk.InvalidMetadataException</InnerType>
<InnerExceptionMessage>The following error was encountered while reading module 'XXX': Security attribute type does not have a default constructor: System.Security.Permissions.SecurityPermission.</InnerExceptionMessage>
Anyone any ideas?
I keep running into the following exception
Description: An error occurred during the compilation of a resource
required to service this request. Please review the following specific
error details and modify your source code appropriately.
Compiler Error Message: CS0234: The type or namespace name
'WebViewPage' does not exist in the namespace 'System.Web.Mvc' (are
you missing an assembly reference?)
Source Error:
Line 27: Line 28: Line 29: public class
_Page_Views_Content_Index_cshtml : System.Web.Mvc.WebViewPage { Line 30: Line 31: #line hidden
Source File: c:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary
ASP.NET
Files\root\8df93262\ed60a52a\App_Web_index.cshtml.eba9863.jffbohqj.0.cs
Line: 29
So far doing a clean and a rebuild normally fixes the problem. The Dev Environment is using IIS, it seems like something is going wrong when IIS caches the binaries. From some trial and error it seems like the issue happens if a request is made to the site at the same time as the site is being built.
Does anyone have any idea what might be causing the problem? It seems to be a configuration issue as other developers with the same setup do not have the issue.
It turned out to be the references in the project were falling back to a different version of MVC.
Just trying out the sample for the MVC4 Single Page Application. The BigShelf project is here
But when I try to run this, I get the following error after logging in. I'm not sure what is wrong.
Compilation Error Description: An error occurred during the
compilation of a resource required to service this request. Please
review the following specific error details and modify your source
code appropriately.
Compiler Error Message: CS0012: The type
'System.Data.Entity.DbContext' is defined in an assembly that is not
referenced. You must add a reference to assembly 'EntityFramework,
Version=4.1.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'.
Source Error:
Line 22: Line 23: $(function () { Line 24:
upshot.metadata(#(Html.Metadata()));
Line 25: Line 26: ko.applyBindings(new
BigShelf.CatalogViewModel({
Source File: d:\Visual Studio Projects\ASP.NET Single Page Application
(SPA) BigShelf\C#\BigShelf\Views\Home\Index.cshtml Line: 24
Removing the EntityFramework reference and referencing the latest (4.3.1) solved the problem for me.