I tried to restart a remote SQL server (2012 full) and I got this error:
Unable to start service MSSQLSERVER on server (mscorlib)
Every time I try I get this message. How can I fix it?
asked Jul 12, 2013 at 5:58
AndreiAndrei
42.9k35 gold badges154 silver badges218 bronze badges
It looks like the service got setup wrong.
Try The following:
- Run services.msc
- Find the MSSQLSERVER Service.
- Right click and open properties
- Check what service account it is running under (usually NTAUTHORITY\SYSTEM, NTAUTHORITY\LOCAL SERVICE or NTAUTHORITY\NETWORK SERIVICE unless you have it running under a different user account for security purposes).
Also, they might have moved things around in 2012 I’m still on 2008 R2
Avi Turner
10.3k7 gold badges48 silver badges75 bronze badges
answered Jul 12, 2013 at 6:04
MichaelMichael
6846 silver badges4 bronze badges
2
I was getting the same error message for days. I went to my domain controller and changed the password of the sql server agent and updated the password in the configuration manager. And, it connected.
answered Jun 8, 2019 at 4:48
Go to Services and right click on sql server agent. select properties and update password/ confirm password if you not using local system account. Its working for me.
answered Feb 24, 2020 at 7:25
changing password and restarting service works for me
answered Aug 11, 2020 at 13:43
1
When trying to connect to the Azure DW or Azure DB you can experience the following failure, Cannot connect to <servername>.database.windows.net. One or more errors occurred (mscorlib)
SQL Server Management studio allows you to review the detailed exception information and in doing so one is able to obtain the Message, Error Code , Help Link and additional data which could help in troubleshooting the problem.
Select the icon in the SSMS Connection error window
Which will provide the information as example below.
For the exception in our case I was able to obtain the following from the Program Location information where the exception occurred : ADALNativeWrapper.ADALGetAccessToken
It indicated that the login process failed while obtaining an Access Token from the Domain Controller and was not able to complete the Login Process with the Data Warehouse.
The Domain Controller and Authentication process is highly dependent on your AD implementation in this particular scenario a Hybrid Deployment is in place which required the token to be provided by a federated service.
The easiest method to identify where the communication failure is happening is to perform a Netsh trace, especially if you are not familiar with the network and domain topology.
From Admin CMD Prompt run the following which will capture and generate a report and not exceed 1GB in size to a path of your choice.
C:\ Netsh trace start capture=yes report=Yes maxsize=1000 tracefile=c:\<path>\<filename>.etl
Reviewing the output in Message Analyzer and grouping by destination address I could easily determine to which destination my request was failing.
As per the events , sso.<domain>.com which is the Single Sign on Service endpoint was not reachable and therefore prevented the token from being generated. Local firewall rules prevented access to the URL from internal network and once resolve Authentication completed successfully.
When troubleshooting authentication failures ensure that you have an understanding of the Domain Topology and where authentication is occurring which will allow you to confirm that all services are operational and responding as expected.
To obtain a better understanding of AD and Different connection Typologies review the following article.
https://docs.microsoft.com/en-us/azure/active-directory/hybrid/plan-connect-topologies
An alternate solution would be to use Fiddler and perform a fiddler trace which will share the IP details where the connection is failing. In most scenarios we are failing to communicate with the Federated Domain services which are responsible for performing the domain authentication.
- Remove From My Forums
-
Вопрос
-
Hi all! I am having a very strange problem on my SQL Servers. When opening SQL Management Studio and clicking on «New query» (after connecting with one of our SQL Servers which are running SQL Server 2012 or SQL Server 2016), I am getting the error
message «End of stream encounted before parsing was completed (mscorlib)». I am not able to execute any queries. The problem occurs with different SQL Management Studio versions (tested 19.7 and 18.2). Restart of the machines on which SQL Management
Studio is executed did not help. A new installation of the newest SQL Management Studio version did not resolve the problem either.Has anyone experienced this strange error yet as well? I am having no idea what to do next in order to solve the issue ;( .NET Runtime was not updated.
Thanks for any help,
Patrick Wolf
Ответы
-
I found the cause of the mentioned problem: We installed a solution called «Cybereason» on our machine => «The Cybereason solution
combines endpoint prevention, detection, and response all in one lightweight agent.»This software blocked the communication between SQL Management Studio and our server and caused the strange error message. After deinstallation, the problem was gone.
-
Помечено в качестве ответа
12 сентября 2019 г. 9:55
-
Помечено в качестве ответа
«The directory name is invalid.» MSSQL Management Studio
I got an error when trying to modify a stored procedure
Searched for proper solution and found one EXCELLENT solution
Error :
Title — Microsoft Management Studio 2005
«The directory name is invalid.«
(mscorlib)
Solution:
As usual, the only solution to most of the issues in windows : Restarted the machine and error resolved 
By
AlpesH Shah
Database Administrators often need to get involved in code deployments wherein they release new code from one environment to another. As a best practice it is highly recommended to note down issues faced during code deployment and address them before you move with code deployment to higher environments such as Pre-Production or Production.
Learn How to Fix SQL Server Error “Insufficient memory to continue the execution of the program”
One of the most errors faced by DBAs during code deployment is “Cannot execute script. Insufficient memory to continue the execution of the program (mscorlib)“. The reason why you receive the above error is SQL Server Management Studio is when SSMS cannot handle errors in case if the script fails because the script file is very big generally above 30 MB.
How to Fix Insufficient memory to continue the execution of the program (mscorlib) error in SQL Server
Error Message
Cannot execute script. Insufficient memory to continue the execution of the program (mscorlib)Solution: Use SQLCMD to execute Large TSQL Scripts
SQL Server Management Studio (SSMS) is not always the right option to execute larger script files. Hence it is highly recommended to use SQLCMD utility from command prompt to execute larger files.
Related Articles
- Display Line Numbers in SQL Server Management Studio (SSMS)
- How to Enable and Refresh IntelliSense in SQL Server Management Studio (SSMS)
- Performance Dashboard Reports in SQL Server 2012
- How to Use Dedicated Administrator Connection in SQL Server
- How to Migrate Existing Database to Partially Contained Database in SQL Server
- How to Configure Network Drive to be Visible for SSMS to Perform Database Backup and Restore?
How to Start SQLCMD Command Line Utility
1. On the Start menu click Run.
In the Open box type cmd, and
then click OK to open a Command Prompt window.
2. In the command prompt, type SQLCMD.
3. Press ENTER.
You will now have a trusted connection to the default instance of SQL Server that is running on your computer. 1> is the sqlcmd prompt that specifies the line number. Each time you press ENTER, the number increases by one.
4. Finally to end the sqlcmd session, type EXIT at the sqlcmd prompt.
How to Run a Script on Standalone SQL Server Instance Using SQLCMD Command Line Utility
sqlcmd -S DATABASESERVERNAME -i "F:/DeploymentScripts/DataPopulation.sql" How to Run a Script on a Named Instance of SQL Server Using SQLCMD Command Line Utility
sqlcmd -S DATABASESERVERNAME\TESTINSTANCE -i "F:/DeploymentScripts/DataPopulation.sql" Overview of Different SQLCMD Command Line Options in SQL Server
-S Specifies the instance of SQL Server to which to connect
-i Specify the file path of the input script Conclusion
It is highly recommended to use SQLCMD command line utility to execute TSQL scripts which are large in size as SQL Server Management Studio will not be able to handle large file for execution.
Chetna Bhalla
LESS ME MORE WE
Chetna Bhalla, the founder of MyTechMantra.com, believes that by sharing knowledge and building communities, we can make this world a better place to live in. Chetna is a Graduate in Social Sciences and a Masters in Human Resources and International Business. She is an alumnus of Vignana Jyothi Institute of Management, Hyderabad, India. After graduation, Chetna founded this website, which has since then become quite a favorite in the tech world. Her vision is to make this website the favorite place for seeking information on Databases and other Information Technology areas. She believes that companies which can organize and deploy their data to frame strategies are going to have a competitive edge over others. Her interest areas include Microsoft SQL Server and overall Database Management. Apart from her work, Chetna enjoys spending time with her friends, painting, gardening, playing the violin, and spending time with her son.