We switched from a SQL server 2017 to a newer SQL server 2019. We deployed all our SSIS-packages in the same way to the newer server. Since then we have often the same error on processing-tasks like cube-processing or dimension-processing on the newer server:
Error: Trace: The Subscription identifier is invalid; it must be unique when subscribing and the identifier of a registerd subscription when unsubscribing.
So our jobs are failing. Some jobs are scheduled every ten minutes. They don't fail always, but sometimes within a day.
I changed our SSIS-package with SSAS-tasks from a projecttype of sql server 2017 to the projecttype of sql server 2019, but this didn't solve this problem. I have no clue what is wrong.
Related
On our production server SSIS packages failing from 24th Jan. They used to run fine (in default runtime) until 23rd Jan 2022.
Some reason they execute and validate fine if I run in 32 bit runtime but fails in default runtime.
Environment - SQL Server 2016 Standard Edition.
When a package executes first it fails and reports the following execution status in SQL Agent Job history.
Executed as user: . Microsoft (R) SQL Server Execute Package Utility Version 13.0.5888.11 for 64-bit Copyright (C) 2016 Microsoft. All rights reserved. Started: 11:41:23 Package execution on IS Server failed. Execution ID: 197521, Execution Status:5. To view the details for the execution, right-click on the Integration Services Catalog, and open the [All Executions] report Started: 11:41:23 Finished: 11:41:26 Elapsed: 2.235 seconds. The package execution failed. The step failed.
In SSISDB Catalog execution report there are no details of the issue reported but the status is set to Pending Execution.
When validating the package in SSISDB catalog the following error message is displayed.
A .NET Framework error occurred during execution of user-defined routine or aggregate "validate_package_internal":
System.ComponentModel.Win32Exception: Access is denied
System.ComponentModel.Win32Exception:
at Microsoft.SqlServer.IntegrationServices.Server.ISServerProcess.StartProcess(Boolean bSuspendThread)
at Microsoft.SqlServer.IntegrationServices.Server.ServerApi.ValidatePackageInternal(SqlInt64 projectId, SqlInt64 package_id, SqlInt64 versionId, SqlInt64 validationId, SqlString targetEnvironment, SqlInt16 use32BitRuntime)
. (.Net SqlClient Data Provider)
We have performed the following troubleshooting steps to resolve the issue but no luck.
Restarted the server
Applied Windows updates
Applied additional group policy permissions to the user accounts that are running SQL Server, Integration Service and SQL Agent services as per the Microsoft documentation.
Uninstalled and reinstalled SQL Server 2016 with Integration Services
Deleted and recreated SSISDB catalog
I cannot see anything online related this therefore its proving to be hard to find the problem. Can you please shed some light on this.
This phrase jumps out from the error message generated after validating the package in the SSISDB catalog.
Access is denied
Security changes appear to be needed to enable the required access.
I had TFS 2015.3 with SQL Server 2014 Express, after upgrading the SQL Server to 2017, TFS stopped working and could not be started.
I removed SQL Server 2014 and installed SQL Server 2017 with same instance name (.\SQLEXPRESS) and attached all databases from files in the DATA folder of SQL Server 2014. Then tried to start TFS, but I did not succeed.
Then I upgraded TFS to 2018.3. After installation completed, I used upgrade wizard and now I have some collection which failed. When I click on start collection (in Team Foundation Server Admin. Console), this error happens:
TF400783: The Host 'MyCollection1' cannot be started. The host is in the
process of being serviced. The servicing may have failed and needs to be restarted and completed before the host can be started.
In the status of collection, in the "most recent servicing activity", I have this
AppltPatch, Failed, 3/8/2019
What can I do to get my collection work again?
What can I do to get my collection work again?
First of all, it's highly possible that you will need to restore the last good consistent set of tfs backups to get your TFS environment to a working state again. Or even contact MS support if no such backup is available.
But before doing that try to figure out what is an exact reason of the failure, perhaps it is fixable and the upgrade process will be eventually finished successfully:
USE Tfs_Configuration
-- get job id that was failed
SELECT TOP 10 *
FROM tbl_ServicingJobDetail
ORDER BY StartTime desc
-- query information for that job id
SELECT * FROM vw_ServicingStepDetail
WHERE jobid = 'BA3E49D5-EA30-4CB6-93DD-31D5D1C0FB93'
Also, have you already tried to open a Status tab of the collection, select that job that was failed and click on Rerun Job?
We have a Windows Server 2008 R2, Service Pack 1 with an SQL Server 2008 R2 (Microsoft SQL Server Standard Edition (64-bit), version 10.50.4042.0) for creating scheduled reports in SSRS. The Report Server services didn't start up after a server restart a while ago and when I noticed that after several days, I started the service. Then it began to loop thru all reports constantly, as if the server not was aware of that it had already done that report.
When I look in the table [ReportServer].[dbo].[ExecutionLogStorage] I can see that new reports are created constantly as fast as the previous report is ready. It looks to loop thru all reports.
I found two errors in Windows application log which maybe are connected to the problem, or not.
Failed to unload app domain DefaultDomain. The following exception occurred: Error while unloading appdomain. (Exception from HRESULT: 0x80131015).
ProcessName: ReportingServicesService
ProcessId: 4308
Failed to trace event: System.AppDomainUnloadedException: Attempted to access an unloaded AppDomain.
I really don't understand what to do. The server has been running for several years, doing the scheduled jobs without any problem. I have restarted SQL Server Agent, Reporting Services as well as the whole server and it doesn't make any difference.
I am thankful for any help.
Lage
I got help from MS Developer Network, so want to share it here if someone get similar problems.
https://social.msdn.microsoft.com/Forums/en-US/1cd9f753-02b2-4dea-a77a-0fa33fe80c7a/sql-server-reporting-services-scheduler-in-infinite-loop-spamming-reports?forum=sqlreportingservices
Best regards
Lage
I am replicating a SQL 2008 R2 database to a SQL 2016 database.
When I connect to the SQL 2016 database using SSMS, and in Object Explorer
select Replication->Local Subscription->MySubscription then right click and select Properties I get the error "Cannot apply value ‘null’ to property ServerInstance: Value cannot be null.".
What does it mean and how can I fix it? I am logged in using my Windows domain user which is a sysadmin on both systems.
Starting SQL 2016, change has been introduced to support memory-optimized subscribers for Tran Replication. This bug in SSMS is a regression from that change.
In the subscription properties form, a new entry has been added to show whether it is memory-optimized subscription or not. This information is fetched from Distributor server.
So, for a push subscription, if the subscriber is SQL 2016 or above, if you try to look at the subscription properties from the subscriber server, the distributor server is returned as NULL since it can not access/connect to distributor server. This is the reason why you get this error.
Until this is fixed, you can view the subscription properties from the publisher side.
I just had the same issue, my replication publisher and distributor is on SQL Server 2014 and my subscriber is SQL Server 2016. When I tried using SSMS 2016 I had the same issue but when I use SSMS 2014 everything worked fine, so this is very likely to be because of the version of SSMS. Try using the SSMS Version that the publisher(source) is using.
I have had this issue when all servers were on the same version of SQL. I read somewhere that Replication won't work if there are more than three versions of SQL between the distributor and publisher (and subscriber depending on the type of replication), but I worked around this by using a lower compatibility level for the databases.
In my current setup everything is SQL 2016. I had this same issue and fixed it by creating a linked server for the distributor and publisher on the subscriber. These should be creating during set-up so I'm not sure why they weren't.
From the distributor I scripted the linked server repl_distributor and also the linked server for the publisher and then ran these scripts on the subscriber. This then fixed the issue.
I hope this works for you too (although your question was ages ago so you're probably alright now!).
Check the linked server "Server Options" Tab. Here you speicify distributor, Publisher and Subscriber. Ensure these are set to true where appropriate for the setup you have. If these options are all set to false as was the case for me using all SQL 2016 you can get this error as it fails to connect to the distributor.
According to the change log for SSMS 17.4 (released 14th December 2017), this error has now been fixed for PULL subscriptions.
From This Connect item,Workaround seems to be..
1.Add the user as local admin on windows box
2.Run SSMS as admin..
I am shifting my development platform to a virtual machine (using VirtualBox), and have installed Win7, VS2010 and SQL Server Express 2008 R2. I have a project that uses FluentMigrator to look after the database.
When I (try to) run the initial migration, all console messages come back from FluentMigrator reporting success, but when I look at the database, no changes have been made. Also, if I try to refresh the schema in SQL Server Management Studio Express within a couple minutes of running the migration, I get a "Lock request timeout period exceeded" message.
Unfortunately SQL Server Express does not come with SQL Profiler. Is there a way I can look at the queries hitting the database without this?
Any other ideas on why FluentMigrator would be reporting success when there is no success to be found?