FluentMigrator & Lock request timeout period exceeded - sql-server

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?

Related

MS Access on Windows 10 drops connection to SQL Server randomly

We have a MS Access 2010 app, using SQL Server 2008 R2 as its database. All workstations were running on Windows 7 with no problems.
Our customer started to upgrade the workstations to Windows 10, and now we see connection to the server drops at a random occasions. Not related to any specific action, query, report or form.
The application is using ODBC connection to access the tables.
When this happens, all connections to all tables are dropped, and the app is unusable.
To resolve this, we need to restart the application and everything is working fine again, until the next time.
We opened up a table when this error occurs and see all the records showing #Name as the data.
Please help
Tested the network connection - no problems or errors
Upgraded SQL Server Service Pack to the latest (thought it might related to TLS version)

SQL Server 2014 - Windows could not start SQL server on local computer

I have an AWS instance, on which SQL Server 2014 has been running for more than 3 years.
But a few days ago, suddenly the SQL Server stopped running.
I checked the server and tried to start SQL Server service from services, from SQL Server Configuration Manager etc. but I'm not able to start the server and got following error:
So I checked event viewer entries and I found these two errors:
I started some research work over web to overcome on this issue and I found that I can start SQL service using below command using T902:
net start MSSQL$REVCORD /T902
And SQL Server service started successfully.
But I want to make SQL Server / services back to normal as before so I can start / stop services normally.
I found on web that this cause is due to corruption in master SQL Server database, I don't have backup of master SQL Server database so I cannot restore it back.
I checked multiple threads over web and tried multiple things to overcome this issue but no luck.
So finally I decided to reinstall/recover SQL Server 2014, but I am getting another error while reinstalling:
Based on finding over web, all threads showing that I have to uninstall and reinstall SQL Server to make it normal again.
Please help! It's a live server with multiple calls continously so I cannot uninstall/reinstall SQL Server there due to possible data loss.
The first thing:
select * from sys.sysmessages where error = 5833
The message:
The affinity mask specified is greater than the number of CPUs supported or licensed on this edition of SQL Server.
Check your edition, and fix the affinity mask so that the number of CPUs satisfy the number which is supported by your edition.
You can fix it in SSMS on the Processors tab in your server properties, or using sp_configure

SQL Server reporting services scheduler loops, running amok

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

Microsoft Data Quality Services Refresh of client view table error

I am trying to run SQL Server Data Quality Services on SQL Server 2014 with 32GB of RAM, plenty of disk space, and the latest updates (Microsoft SQL Server 2014 (SP2-CU2) (KB3188778) - 12.0.5522.0 (X64) Developer Edition (64-bit) on Windows NT 6.3 (Build 9600: ) (Hypervisor))
The data resides on the same server, separate database.
Knowledge base is created and published with three domains over about a million records table. And that where it stops working: creating data quality project fails after displaying cheerful message "Analysis of data source has been completed successfully" - clicking "Next" button leads to message #1, and, after restarting the application (and the server - just in case), the message #2
SQL Server Data Quality Services server has stopped working
Refresh of client view table for user [domain\user] failed.
These are fairly consistent.
Examining both the server and the client logs reveals nothing (besides a full stack dump for the error), and the only suggestion from Microsoft forums is “to apply latest service pack”; the latest service pack has been applied but still no cigar.
Any insights/suggestions would be highly appreciated!
thank you,
-al
P.S. Excerpt from the client log:
2/13/2017 9:19:26 AM|[]|1|ERROR|CLIENT|Microsoft.Ssdqs.Studio.ViewModels.Utilities.UIHelper|An error has occurred.
Microsoft.Ssdqs.Infra.Exceptions.EntryPointException: Refresh of client view table for user [domain\user] failed.;
at Microsoft.Ssdqs.Proxy.Database.DBAccessClient.Exec();
After poking around I have found a question similar to my on MSDN blog: a user complained that his DQS installation has STOPPED working after applying CU2 to his SQL Server 2014 instance... So, I downgraded mine from [(SP2-CU2) (KB3188778)] to [(SP2) (KB3171021)], and - drums rolling - everything started working!
This is not a solution but an acceptable workaround, and I can continue analyzing my data until I upgrade to SQL Server 2016, and the fun begins anew!

How to enable SQL Server Agent in SQL Server 2012 Express

When I try to start SQL Server Agent from SQL Server Configuration Manager
I get this error
the request failed or the service did not respond in a timely fashion.Consult the error log or other applicable error log for details
So how can I solve it?
Have you checked if your sqlServerAgent is running in windows admin tools / services? If it is stopped,just right click it and start it. Set also start type to automatic in next column.
The agent service is not included in the express editions of SQL Server, so it can't be enabled at all. Even though the error messages are misleading, the actual error is a licensing one. To get the agent you need to upgrade to any other edition. For just developing and testing the developer edition is the best choice.
Other than that, you can try to emulate such functionality by using the Windows task scheduler to run the SQL command line tools.

Resources