ActiveX Scripting Was Not Able To Initialize The Script Execution Engine
Aug 9, 2005
When I attempt to run my DTS Pkg that contains ActiveX task, I get following error:
"ActiveX Scripting was not able to initialize the script execution engine"
When I run this from another computer, it runs fine.
I have tried reregistrate DTS DLLs:
Regsvr32.exe "C:Program FilesMicrosoft SQL Server80ToolsBinnaxscphst.dll"
Regsvr32.exe "C:Program FilesMicrosoft SQL Server80ToolsBinndtspkg.dll"
Regsvr32.exe "C:Program FilesMicrosoft SQL Server80ToolsBinndtspump.dll"
But it does not help.
I am worried the great site for DTS issues "http://www.sqldts.com " is down :-(
Any ideas ?
My System:
Windows Server 2003 + SP1
MS SQL Srrver 2000 + SP4
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 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"
I'm trying to do some profiling of a mobile application to determine where our performance bottleneck is. We have some conflicting information suggesting that inefficient usage of SqlCE might be the cause - but that code exists in a black-box library so we can't see what it's doing.
Are there any tools or configuration options to get the SqlCE execution engine to reveal what connections/queries it's being asked to perform? A simple list with some timestamps would be sufficient - just so we can map from our high-level data...
how to eliminate a key lookup from the execution plan
SET TRANSACTION ISOLATION LEVEL READ COMMITTED SET NOCOUNT ON SELECT COUNT(ph.lid) AS Total FROM PLB ph WHERE ph.lPhysician = @Physician AND ph.BSF = CAST(0 AS bit)
I have a logon trigger on a SQL Server 2008 R2 Express Advanced production database to prevent remote logons. The trigger works fine. When I need to connect via my local machine, remotely, I connect via a VPN, can connect with SSMS and do whatever I need. However, if I use a linked server on my local machine (still connected via VPN), I receive the logon error
Msg 17892, Level 14, State 1, Line 1 Logon failed for login 'sa' due to trigger execution.
The trigger is below and it logs any failures, except for the linked server.
If I disable the trigger, the linked server connects ok.
CREATE TRIGGER [tr_MasterLogon] ON ALL SERVER WITH EXECUTE AS 'sa' FOR LOGON AS BEGIN DECLARE @ClientAddress varchar(48) = (SELECT client_net_address
I am running a huge SSRS 2008 report and it gets rendered sometimes and sometimes it gives me an error,"The report execution has expired or cannot be found. (rsExecutionNotFound)”.
When I see SQL Server log after this issue comes I see following message there; "A significant part of sql server memory has been paged out. This may result in performance degradation. Duration: 300 seconds. Working set(KB): 97672, memory utilization 42%" .what is the issue and how to fix it.
We know we can use the event lock_deadlock and xml_deadlock_report to capture the deadlock info, however I also want to capture the execution plans for all of the SPIDs in the deadlock graph, how to output the execution plans to the extended events trace results either ? such as if there is an action for execution plan or workaround for it ?If there is no built in action for execution plan , may I know if we can add the customized info to the extended events results file also ? Such as when the deadlock related event happens , then we can run a query to get some info ,then added the info along with other info such as sql_text, dbname etc to the events trace results file either ? The reason is if we also know the execution plans when the deadlock happens, it is useful to turning the query based on the execution plans to reduce deadlock happening .
after moving off VS debugger and into management studio to exercise our SQLCLR sp, we notice that the 2nd execution gets an error suggesting that our static SqlCommand object is getting reused from the 1st execution (of the sp under mgt studio). If this is expected behavior, we have no problem limiting our statics to only completely reusable objects but would first like to know if this is expected? Is the fact that debugger doesnt show this behavior also expected?
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?
Hi I am slowly getting to grips with SQL Server. As a part of this, I have been attempting to work on producing more efficient queries. This post is regarding what appears to be a discrepancy between the SQL Server execution plan and the actual time taken by a query to run. My brief is to produce an attendance system for an education establishment (I presume you know I'm not an A-Level student completing a project :p ). Circa 1.5m rows per annum, testing with ~3m rows currently. College_Year could strictly be inferred from the AttDateTime however it is included as a field because it a part of just about every PK this table is ever likely to be linked to. Indexes are not fully optimised yet. Table:CREATE TABLE [dbo].[AttendanceDets] ([College_Year] [smallint] NOT NULL ,[Group_Code] [char] (12) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL ,[Student_ID] [char] (8) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL ,[Session_Date] [datetime] NOT NULL ,[Start_Time] [datetime] NOT NULL ,[Att_Code] [char] (1) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL ) ON [PRIMARY]GO CREATE CLUSTERED INDEX [IX_AltPK_Clust_AttendanceDets] ON [dbo].[AttendanceDets]([College_Year], [Group_Code], [Student_ID], [Session_Date], [Att_Code]) ON [PRIMARY]GO CREATE INDEX [All] ON [dbo].[AttendanceDets]([College_Year], [Group_Code], [Student_ID], [Session_Date], [Start_Time], [Att_Code]) ON [PRIMARY]GO CREATE INDEX [IX_AttendanceDets] ON [dbo].[AttendanceDets]([Att_Code]) ON [PRIMARY]GOALL inserts are via an overnight sproc - data comes from a third party system. Group_Code is 12 chars (no more no less), student_ID 8 chars (no more no less). I have created a simple sproc. I am using this as a benchmark against which I am testing my options. I appreciate that this sproc is an inefficient jack of all trades - it has been designed as such so I can compare its performance to more specific sprocs and possibly some dynamic SQL. Sproc:CREATE PROCEDURE [dbo].[CAMsp_Att] @College_Year AS SmallInt,@Student_ID AS VarChar(8) = '________', @Group_Code AS VarChar(12) = '____________', @Start_Date AS DateTime = '1950/01/01', @End_Date as DateTime = '2020/01/01', @Att_Code AS VarChar(1) = '_' AS IF @Start_Date = '1950/01/01'SET @Start_Date = CAST(CAST(@College_Year AS Char(4)) + '/08/31' AS DateTime) IF @End_Date = '2020/01/01'SET @End_Date = CAST(CAST(@College_Year +1 AS Char(4)) + '/07/31' AS DateTime) SELECT College_Year, Group_Code, Student_ID, Session_Date, Start_Time, Att_Code FROM dbo.AttendanceDets WHERE College_Year = @College_YearAND Group_Code LIKE @Group_CodeAND Student_ID LIKE @Student_IDAND Session_Date <= @End_DateAND Session_Date >=@Start_DateAND Att_Code LIKE @Att_CodeGOMy confusion lies with running the below script with Show Execution Plan:--SET SHOWPLAN_TEXT ON--Go DECLARE @Time as DateTime Set @Time = GetDate() select College_Year, group_code, Student_ID, Session_Date, Start_Time, Att_Code from attendanceDetswhere College_Year = 2005 AND group_code LIKE '____________' AND Student_ID LIKE '________'AND Session_Date <= '2005-11-16' AND Session_Date >= '2005-11-16' AND Att_Code LIKE '_' Print 'First query took: ' + CAST(DATEDIFF(ms, @Time, GETDATE()) AS VarCHar(5)) + ' milli-Seconds' Set @Time = GetDate() EXEC CAMsp_Att @College_Year = 2005, @Start_Date = '2005-11-16', @End_Date = '2005-11-16' Print 'Second query took: ' + CAST(DATEDIFF(ms, @Time, GETDATE()) AS VarCHar(5)) + ' milli-Seconds'GO --SET SHOWPLAN_TEXT OFF--GOThe execution plan for the first query appears miles more costly than the sproc yet it is effectively the same query with no parameters. However, my understanding is the cached plan substitutes literals for parameters anyway. In any case - the first query cost is listed as 99.52% of the batch, the sproc 0.48% (comparing the IO, cpu costs etc support this). BUT the text output is:(10639 row(s) affected) First query took: 596 milli-Seconds (10639 row(s) affected) Second query took: 2856 milli-SecondsI appreciate that logical and physical performance are not one and the same but can why is there such a huge discrepancy between the two? They are tested on a dedicated test server, and repeated running and switching the order of the queries elicits the same results. Sample data can be provided if requested but I assumed it would not shed much light. BTW - I know that additional indexes can bring the plans and execution time closer together - my question is more about the concept. If you've made it this far - many thanks.If you can enlighten me - infinite thanks.
