Sp_browsereplcmds Causes Failed To Initialize The Common Language Runtime...
Feb 1, 2007
When executing
exec distribution..sp_browsereplcmds
SQL Server 2005 Standard SP1 says:
Msg 6513, Level 16, State 27, Procedure sp_browsereplcmds, Line 110Failed to initialize the Common Language Runtime (CLR) v2.0.50727 due to memory pressure. Please restart SQL server in Address Windowing Extensions (AWE) mode to use CLR integration features.I have two (nearly) identically machines (test has 2, prod has 4 CPUs), both 3071MB RAM, Win 2k3 Server SP1, both have no AWE running.
On test-machine the procedure works fine, on production in doesn't.
I checked performance. Test machine has about 180MB available memory, production about 160MB (nearly constant). Thread count for process sqlservr is constant and similar at about 65.
Any idea why it runs on test but not on production machine?
Failed to initialize Distributed COM (CoInitializeEx returned 80010119). Heterogeneous queries and remote procedure calls are disabled. Check the DCOM configuration using Component Services in Control Panel.
Any ideas as to how to troubleshoot or solve this?
I'm receiving this error message when trying to install SQL Server 2005 Express Edition on Windows Vista Home Premium:
Product: Microsoft SQL Server 2005 Express Edition -- Error 29521. SQL Server Setup failed to execute a command for server configuration. The error was [Microsoft][SQL Native Client][SQL Server]The server could not load DCOM.. Refer to the server error logs and Setup logs for detailed error information.
In the ERRORLOG file, the error is:
Failed to initialize Distributed COM (CoInitializeEx returned 80010119). Heterogeneous queries and remote procedure calls are disabled. Check the DCOM configuration using Component Services in Control Panel.
There is no Component Services in the Control Panel. Do they just mean Services? If so, how do you configure DCOM in the Services?
Thanks in advance for your help!
Below is the complete ERRORLOG:
2007-12-06 11:16:09.69 Server Microsoft SQL Server 2005 - 9.00.3042.00 (Intel X86) Feb 9 2007 22:47:07 Copyright (c) 1988-2005 Microsoft Corporation Express Edition on Windows NT 6.0 (Build 6000: ) 2007-12-06 11:16:09.72 Server (c) 2005 Microsoft Corporation. 2007-12-06 11:16:09.72 Server All rights reserved. 2007-12-06 11:16:09.72 Server Server process ID is 5672. 2007-12-06 11:16:09.72 Server Authentication mode is MIXED. 2007-12-06 11:16:09.72 Server Logging SQL Server messages in file 'c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLLOGERRORLOG'. 2007-12-06 11:16:10.31 Server Registry startup parameters: 2007-12-06 11:16:10.31 Server -d c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLDATAmaster.mdf 2007-12-06 11:16:10.31 Server -e c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLLOGERRORLOG 2007-12-06 11:16:10.31 Server -l c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLDATAmastlog.ldf 2007-12-06 11:16:10.31 Server Command Line Startup Parameters: 2007-12-06 11:16:10.31 Server -m SqlSetup 2007-12-06 11:16:10.31 Server SqlSetup 2007-12-06 11:16:10.31 Server -Q 2007-12-06 11:16:10.31 Server -q SQL_Latin1_General_CP1_CI_AS 2007-12-06 11:16:10.31 Server -T 4022 2007-12-06 11:16:10.31 Server -T 3659 2007-12-06 11:16:10.31 Server -T 3610 2007-12-06 11:16:10.31 Server -T 4010 2007-12-06 11:16:10.38 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required. 2007-12-06 11:16:10.38 Server Detected 2 CPUs. This is an informational message; no user action is required. 2007-12-06 11:16:10.53 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required. 2007-12-06 11:16:10.67 Server The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs. 2007-12-06 11:16:10.71 Server Database Mirroring Transport is disabled in the endpoint configuration. 2007-12-06 11:16:10.73 spid4s Warning ****************** 2007-12-06 11:16:10.73 spid4s SQL Server started in single-user mode. This an informational message only. No user action is required. 2007-12-06 11:16:10.73 spid4s Starting up database 'master'. 2007-12-06 11:16:10.91 spid4s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required. 2007-12-06 11:16:11.02 spid4s SQL Trace ID 1 was started by login "sa". 2007-12-06 11:16:11.07 spid4s Starting up database 'mssqlsystemresource'. 2007-12-06 11:16:11.09 spid4s The resource database build version is 9.00.3042. This is an informational message only. No user action is required. 2007-12-06 11:16:11.69 spid4s Password policy update was successful. 2007-12-06 11:16:11.71 spid7s Starting up database 'model'. 2007-12-06 11:16:11.71 spid4s Server name is 'FRANK-LAPTOP-PCSQLEXPRESS'. This is an informational message only. No user action is required. 2007-12-06 11:16:11.71 spid4s Starting up database 'msdb'. 2007-12-06 11:16:12.48 spid7s Clearing tempdb database. 2007-12-06 11:16:12.59 Server A self-generated certificate was successfully loaded for encryption. 2007-12-06 11:16:12.60 Server Server local connection provider is ready to accept connection on [ \.pipeSQLLocalSQLEXPRESS ]. 2007-12-06 11:16:12.60 Server Dedicated administrator connection support was not started because it is not available on this edition of SQL Server. This is an informational message only. No user action is required. 2007-12-06 11:16:12.62 Server SQL Server is now ready for client connections. This is an informational message; no user action is required. 2007-12-06 11:16:13.15 spid7s Starting up database 'tempdb'. 2007-12-06 11:16:13.31 spid4s Recovery is complete. This is an informational message only. No user action is required. 2007-12-06 11:16:17.13 spid51 Setting database option RECOVERY to SIMPLE for database model. 2007-12-06 11:16:17.46 spid51 Configuration option 'show advanced options' changed from 0 to 1. Run the RECONFIGURE statement to install. 2007-12-06 11:16:17.53 spid51 Configuration option 'default language' changed from 0 to 0. Run the RECONFIGURE statement to install. 2007-12-06 11:16:17.53 spid51 Configuration option 'default full-text language' changed from 1033 to 1033. Run the RECONFIGURE statement to install. 2007-12-06 11:16:17.55 spid51 Configuration option 'show advanced options' changed from 1 to 0. Run the RECONFIGURE statement to install. 2007-12-06 11:16:18.28 spid51 Setting database option NEW_BROKER to ON for database tempdb. 2007-12-06 11:16:18.37 spid51 Setting database option NEW_BROKER to ON for database msdb. 2007-12-06 11:16:18.65 spid51 Configuration option 'show advanced options' changed from 0 to 1. Run the RECONFIGURE statement to install. 2007-12-06 11:16:18.66 spid51 Configuration option 'user instances enabled' changed from 1 to 1. Run the RECONFIGURE statement to install. 2007-12-06 11:16:18.68 spid51 Configuration option 'show advanced options' changed from 1 to 0. Run the RECONFIGURE statement to install. 2007-12-06 11:16:21.64 Server Error: 17102, Severity: 16, State: 1. 2007-12-06 11:16:21.64 Server Failed to initialize Distributed COM (CoInitializeEx returned 80010119). Heterogeneous queries and remote procedure calls are disabled. Check the DCOM configuration using Component Services in Control Panel. 2007-12-06 11:20:10.69 Server CPU time stamp frequency has changed from 52964 to 1017280 ticks per millisecond. The new frequency will be used. 2007-12-06 11:24:10.70 Server CPU time stamp frequency has changed from 1017280 to 1144761 ticks per millisecond. The new frequency will be used. 2007-12-06 11:32:10.70 Server CPU time stamp frequency has changed from 1144761 to 1030017 ticks per millisecond. The new frequency will be used. 2007-12-06 12:05:17.64 spid4s SQL Server is terminating in response to a 'stop' request from Service Control Manager. This is an informational message only. No user action is required. 2007-12-06 12:05:17.64 spid4s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
When I boot my computer (Windows Home Premium 64bit) there is a pop up that says "Configuration System failed to initialize" and I don't know what might cause this..
I have a procedure that works fine from SSMS but sometimes fails when running via SQL Agent. The SP sends emails..Here is the error message "Failed to initialize sqlcmd library with error number -2147467259"
have SQL Server 2005 std edition SP1 installed on Windows 2003 Std edition .Configured Transactional (single Publisher and no clustered environment.) Replication past two months working fine, Now 1.Distrib.exe application err is coming.
Due to which my job is failing (Distributor to Subscriber). Iam attaching thw file. Thanks Sandeep
I am having a Data flow task in For each loop which will gets 100 sourcetable names and 100 target table names...
am having a simpleData flow task which trasferes from OLEDBSource to OLEDBDestination. I am repeating the Dataflow task which transfers from sourcetablename extracted from for loop to a destination table var.
The problem am gettting is for the first table it is able to transfer correcly because I did mapping for those tables at design time...but for the next coming sourcetable-desttable (which r having different no of cols,datatypes) its giving Validation failed...and...needs to refresh metadata....
is there any way to refresh the metadata of Data flow task (I set the property of OLEDBSource validate external meta to false then also same error is coming)
i am using a control that i downloaded from the control gallery It has a line for a connection string.
which i put on in there: data source=server;initial catalog=database;user id=blahblah;password=557896 and i get an error:
Exception Details: System.InvalidOperationException: The ConnectionString property has not been initialized.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[InvalidOperationException: The ConnectionString property has not been initialized.] System.Data.SqlClient.SqlConnection.Open() +433 Microsoft.Vote.VoteButtonClick(Object sender, EventArgs e) +289 System.Web.UI.WebControls.Button.OnClick(EventArgs e) +108 System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument) +57 System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) +18 System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) +33 System.Web.UI.Page.ProcessRequestMain() +1277
I have installed Reportin Services 2005 , X64. I selected install but do not configure.
Afterwards i applied Service Pack 1 and ran all the hotfixes for sql components as per KB 918222.
The i launch the RS configuration manager i succesffuly setup Report Server/Manager Virtual DIrectory and servcie identity.
I then setup the database, i create a new database to the local 2005 instance i just installed with RS, the databse is created successfully.
Basically i have green ticks all the way, however Initialize is greyed out i cannot take the option to initialize the server ???
When i try to restart the RS service it says that the service failed to repond in a timely fashion, when i check the even log the servcie only started 10 minutes later, and there are no errors ?
WHen i go back to RS config manager , initialize is till greyed out , this is the last step i ahve to do but i cannot take the option ???
Hence you have a database which huge tables and a transactional replication (push subscriptions).
Now my question:
1. if I have to initialize a snapshot but I would like to do it without the snapshot agent, what methods are available?
2. Usually the distribution agent will request an initialize snapshot. How can I tell him, that I would like to use an alternative method and that the distribution agent should NOT request a snapshot?
3. Any suggestions about a good practive for materializing huge and big tables wihtout using the disitrbution agent (e.g. "switch off" replication, bcp table out of the primary site and bcp it into the target site, "start" distribution agent so that it doesn't request a snapshot).
I have just completed a fresh install of SSRS 2005. Now, when I try to initialize it, it fails. I then try to delete any encrypted content and get the following error:
Code Snippet ReportServicesConfigUI.WMIProvider.WMIProviderException: The encrypted value for the "LogonCred" configuration setting cannot be decrypted. (rsFailedToDecryptConfigInformation) at ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.ThrowOnError(ManagementBaseObject mo) at ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.DeleteEncryptedInformation()
From what I know, Reporting Services has never been installed on the machine in question. And if so, then haow can I get around this encrypted key issue?
I have a For Loop container where each iteration a Master record is inserted. I also have a number of package variables capturing rowcounts from the dataflow task. I later update the master record with the rowcounts. How do I initialize the package variables containing the rowcounts because currently, some of the rowcounts are being populated with rowcounts from another file.
SELECT [CustomerName], [AccountCode], [ProductCode], [Description1], [Description2], [MaterialType], [Brand], [PGroup], [Type], [GSM], [Colour], [Size1], [Size2], [Microns], [PriceQuantity], [PriceUnit], [Packed], [Price], [MinQuantity], [TonnePrice], [LeadTime], [WebURL] FROM OPENROWSET('Microsoft.Jet.OLEDB.4.0', ' Text;Database=D:ApplicationsxxxxxxxxxAppRootxxxxxxxxxSQLCatalogues;HDR=YES', 'SELECT * FROM [product_test.csv]') AS ImportFile WHERE [ImportFile].[MaterialType] IN (1, 2, 3, 4)
Error message Server: Msg 7399, Level 16, State 1, Line 5 OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error. [OLE/DB provider returned message: Unspecified error] OLE DB error trace [OLE/DB Provider 'Microsoft.Jet.OLEDB.4.0' IDBInitialize::Initialize returned 0x80004005: ].
This is being run on Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) Windows 2003, build 3790.srv03_gdr.070301-2306
Have checked a number of knowledge base articles C:Windowssystem32msjet40.dll version 4.0.8618.0
REGEDT32: HKEY_LOCAL_MACHINESOFTWAREODBC, Administrator/everyone full access
D:ApplicationsxxxxxxxxxAppRootxxxxxxxxxSQLCatalogues has full permissions for Administrator/everyone groups
Can anyone suggest the next step to identifying a possible cause to this issue.
I am developing a system using SQL Server replication between SQL Server EXPRESS 2005 clients and SQL Server 2005 servers. I initialize the replica databases with a script, then I do not want to initilize the subscriber with the snapshot; I configure each subscriber to "not initilize", but when I run the first synchronization the snapshot copy process is always is executed.
Maybe am I forgetting something? Can I use this SQL Server EXPRESS - SQL Server replication scheme without initialize the subscribers with the snapshot? Thaks for reading!
I am experiencing some replication problems. I have a test server with a test database which has been working just fine with some simple Merge Replication. That old server is now been targeted for decommissioning. I have moved the test database to another test server and have set everything conceivable up the same as it was on the prior server but I am experiencing errors that I have not been able to resolve. I am using the same Domain User account with the same privileges on both systems...
The first error I receive in my SQL Server error logs is:
Message Error: 14151, Severity: 18, State: 1.
Rapidly followed by the following error message:
Message Replication-Replication Merge Subsystem: agent SOURCE-DATABASE-MERGE-DESTINATION-16 failed. The merge process could not initialize the subscription. Ensure that the subscription registration exists at the publisher, and reregister the subscription if necessary.
From within the Replication Monitor I look into the subscription and I can see the following error message:
Command attempted:
{call sys.sp_MSmergesubscribedb ('true', 0) }
Error messages:
The merge process could not initialize the subscription. Ensure that the subscription registration exists at the publisher, and reregister the subscription if necessary. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201011) Get help: http://help/MSSQL_REPL-2147201011
INSERT failed because the following SET options have incorrect settings: 'ANSI_PADDING'. Verify that SET options are correct for use with indexed views and/or indexes on computed columns and/or query notifications and/or xml data type methods. (Source: MSSQLServer, Error number: 1934) Get help: http://help/1934
I have looked into the help links from above, researched codes and also browsed this forum and others to no avail so far. Any help or suggestions would be greatly appreciated! THANKS!
I met some problems in merge replication with sql server 2005 (sp2).
one user who is using the PDA (SQL Mobile 2005) try to sync with server, the error info is coming.
the error in replication monitor is shown as following: Error messages: The merge process could not initialize the subscription. Ensure that the subscription registration exists at the publisher, and reregister the subscription if necessary. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201011) Get help: http://help/MSSQL_REPL-2147201011 The subscription could not be found. (Source: MSSQLServer, Error number: 20021) Get help: http://help/20021 The subscription has expired. Mark the subscription for reinitialization and restart the Merge Agent to reinitialize the subscription. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147200980) Get help: http://help/MSSQL_REPL-2147200980
I am unable to get my snapshot agent to initialize. When I start the "View Snapshot Agent Status" and press the Start button, it appears that the snapshot agent attempts to starts and then it doesn't.
I have configured the a distribution server and need to push a replication to another database, both can connect, etc.
I used the wizard to configure the distributon server and subscription server. I am using AdventureWorks, and am attempting to replicate a single small table.
I'm trying to initialize a subscriber from a backup for a pull subscription. The publisher was started before the full backup was made. I followed the instructions @ Books Online topic "Initializing a Transactional Subscription Without a Snapshot" http://msdn2.microsoft.com/en-us/library/ms151705.aspx and How to: Initialize a Transactional Subscriber from a Backup (Replication Transact-SQL Programming) http://msdn2.microsoft.com/it-it/library/ms147834.aspx . I initialized the subscriber by restoring the db before I run the create subscriber scripts. All agents run successfully except for the following:
The network setup is that the publisher and the subscriber are in 2 different domains with the distribution database at the publisher. The subscriber agent is able to connect and run however the error on the subscriber side is:
"Agent message code 14080. The remote server "subscriber" does not exist, or has not been designated as a valid Publisher, or you may not have permission to see available Publishers."
The warning on the publisher side is in the Replication Monitor where in the status it says Uninitialized Subscription.
Any ideas on why it says it isn't initialized? Is there a StoredProc that I have to execute to initialize from backup?
Newbie strikes again.. I'm attempting to connect to a SQL Server database (using VS 2005). My code generated no errors in the build but when I tried to access the database, I got the following message:"The ConnectionString property has not been initialized."My connection string is stored in my web.config file. My code goes as follows:Dim strSQL As String = "SQL string stored here"Dim objConnection as SqlConnection = New SQLConnection(ConfigurationManager.AppSettings("name of connection string is here"))Dim objCommand as SQLCommand = New SqlCommand(strSQL, objConnection)objConnection.Open()Then I go on to open my reader and such. Where should I be initializing the ConnectionString property?TIA,Lesley
Quick question- how much disk space is required on the subscriber to initialize a subscription (transactional replication) – does it have to copy the snapshot files (e.g. the bcp files etc) from the distributor, and then initialize the subscriber from this, or does it do this over the network?
Does it differ depending on whether it is push or pull?
Say I have a 10 GB snapshot on the distributor with a push subscription to the subscriber. Do I need 20 GB free on the subscriber? E.g. 10 GB to receive the snapshot files + 10 GB for the subscriber DB? Or just 10 GB for the subscriber DB which is initialized from the snapshot files over the network?
I've been trying to connect to my local SQL Server instance (SQL Server 2005) using the SQLNCLI interface from c++ without success. I consistently receive an 'Invalid authorization specification' error (SQL state 28000 and SQL error number 0) when I call IDBInitialize::Initialize to connect to the database. I was hoping someone here could shed some light on this and help me out.
The strange thing is that I get no error if I leave the user blank (L"" in vValue.bstrVal) and try to connect. Also, IDBProperties::SetProperties returns 0 when the user is blank but 40eda when the user is set. This seems to be a message from the pipeline facility but I haven't found the description of the code (0xeda).
The user in the database is configured with no password and I can successfully connect to the server and open the database using that user through Management Studio.
I've also tried using the SQLOLEDB provider with the same results.
Suspecting that I'm setting the properties wrong I include a code snippet below showing how I'm setting the properties:
for (int i = 0; i < sizeof(dbprop) / sizeof(dbprop[0]); i++) VariantInit(&dbprop[ i ].vValue);
// Server name dbprop[0].dwPropertyID = DBPROP_INIT_DATASOURCE; dbprop[0].vValue.vt = VT_BSTR; dbprop[0].vValue.bstrVal = SysAllocString(L"localhost"); dbprop[0].dwOptions = DBPROPOPTIONS_REQUIRED; dbprop[0].colid = DB_NULLID;
I have been trying to set up transactional replication between an OLTP SQL Server 2005 Standard edition server and a BI SQL Server 2005 Enterprise edition server. I am using a pull subscription. I was able to establish the replication from the developement server to the BI server however when I tried setting up the replication between the production environment and the BI server, using the same configuration settings, I ran into a problem. The production server had been renamed after it was initially set up. I used the sp_dropserver and sp_addserver to solve this issue and was able to run the replication wizard. However once the wizard finishes the snapshot agent doesn't initialize the publication. When I look at the replication monitor it has a status of "never run". I try to run it manually and it appears to run for a few seconds then stops and still has the status of "never run". I don't get any error messages and can't find anything in the log. I am wondering if this is related to the server rename? I am hoping to find a soultion that doesn't involve uninstalling SQL Server and reinstalling since this is a production environment.
I was using the DTS Import/Export wizard and I went to edit the vbscript that does the transformation. When I run the package I get an error message --
ActiveX Scripting Transform 'AxScriptXform' was not able to initialize the script execution engine. Help appreciated.
I have a pretty big (350 gb) OLTP database that I want to replicate in its entirety. I'm concerned about the impact of taking a snapshot of it (it is processing at some level pretty much 24x7). I know on SQL2005 there is the option to initialize from backup, but unfortunately we won't be on 2005 in time.
I'm thinking of doing something like this:
Set up the distributor, publication, and subscription Turn off distribution agent Set the publisher to "sync with backup" Backup the publisher, full then log Truncate tables MSrepl_transactions and MSrepl_commands in the distribution db (I don't have any other replication going on) Turn off "sync with backup" Restore the full and tran log backups to new subscriber db Create subscriber stored procs in subscriber Start up distribution agent
I'm looking for opinions on whether it's worth going this route to avoid taking the snapshot. Data integrity is the number one priority -- if I have to do a snapshot to ensure that, I will do it.
