We just started noticing this. It used to work, and now it doesn't. The crash happens on all of our computers. We right click on a database, select Script Database..., choose to script the entire database and SSMS crashes. No information in the Event Logs. We've found that if we script all tables, it works. If we also script all stored procedures and functions, it crashes. All of our databases are in Azure. Haven't tried local DBs. Any ideas how to troubleshoot?
Thank you,
Mike
It might be a bit late to answer but it might help someone;
I had the same issue recently, upgraded to the latest version 18.12.1 and it now works fine;
Check Download SSMS 18.12.1
Click on "Free Download for SQL Server Management Studio (SSMS) 18.12.1"
and run the installed file "SSMS-Setup-ENU.exe" as an administrator and follow the wizard.
Related
We have a task where we need to automatically convert an excel file to a csv to prep it for loading into a SQL database. The developers built this process into a SSIS package. For the conversion, they initially tried to have a task in the SSIS package execute a VBscript to convert the file. When they were running this on there local machines, this worked correctly. When they ran the package manually through VS on the server, it ran correctly. When they ran the package manually via the Integration Catalog it ran correctly. We did this both as our accounts and as the service account and got the same results. However, when we scheduled it as a job it would hang on the part of the process that executed the VBScript. No errors, it would just hang until you killed the job.
The job was executing as the service account which has full admin access on the server, explicit full access to the share where the files are stored and converted (which is on the same server) and full admin access to SQL. The job owner is set to sa which uses the service account. And all the job does is execute the package from the integration catalog which works if you run it independently of a job. When we compared the ssisdb execution report for the manual run in the integration catalog using the service account to the job run they looked the same except the job hung on the conversion task and the other did not.
After spending some time trying to figure this out, the developers tried a different solution. They changed the conversion script from using VBScript to using C#. They ran the package from there local machine and once again the package worked. This time when they ran it manually on the server it failed. When we ran it from the integration catalog it failed and when we ran it from a job it failed.
The error we keep getting is "Create CSV file: Error: Exception has been thrown by the target of an invocation" After spending several hours looking into this error nothing suggested seems to be working.
We also tried these same solutions on a newly built server to make sure we weren't dealing with an odd configuration setting that could have been changed (It is a Dev server) and it still failed there.
At this point, we are pretty lost at what is happening. The first solution worked, but for some reason would never work as a job. The 2nd solution works everywhere except when ran on the server.
We are looking at some other solutions to try to get around this. The next thing may be trying to using powershell to convert the file, but not sure if that will bring us back to the same issue. Any suggestion you guys have will be greatly appreciated
Also, we are using SQL Server 2012 dev edition, VS 2012 pro, Windows Server 2012 R2
This might be because of a bug that Excel has when trying to run jobs (that use Excel) and no user is logged on a specific machine. This might affect also the excel library. The solution is to create the following 2 folders:
C:\Windows\SysWOW64\config\systemprofile\Desktop
C:\Windows\System32\config\systemprofile\Desktop
and then restart the machine. :)
(Edited to show that a restart is needed. thanks for Dustin for checking this)
How do I save/commit/push such that the network has the latest version?
I have never used version control before.
I am new to Visual Studio 2015 (I mainly used VS 2005).
I am a VB.net developer.
I am running Windows 10 and have a Windows 2008R2 Server (not AD).
I need to keep my code private and local (no cloud).
I will eventually need to have up to 3 developers collaborate with my code.
I am not a fan of using the command line unless I absolutely have to. (GUI for me).
I feel that version control should be integrated with Visual Studio.
I think the code should be stored on the server and a local (working) copy on my machine.
I believe I would benefit from using Git. (Not GitHub).
I may also check out Gogs or Bonobo. I hate Java so not (Gitblit)
I Installed Git on my server - although I'm not sure I needed to do this.
I have installed it on my local machine.
I mapped a shared directory (v:)
I have attempted (successfully - I think) to copy my code into a repository and make a few commits.
I thought I was having some success using the Visual Studio 2015 - Built-It / Extension
However, after attempting to use/create a local clone eg C:\Users\My User Name\Source\Repos
Making some changes, Commit All, Then attempting to Push I get the following Error:
"Failed to push to the remote repository. See the Output window for more details."
Output window says:
"Error encountered while pushing to the remote repository: Local push doesn't (yet) support pushing to non-bare repos."
I've read but not sure how to apply to VS Git push error '[remote rejected] master -> master (branch is currently checked out)'
PS. Because of my specific set-up/needs I’m struggling to find help. Any tutorial recommendations are welcome.
Sorry if this is too verbose.
I had many problems trying to solve this.
One of which was attempting to use the Network Drive as the Master when I Believe the local is the Master.
I am sure that I am to much of a noob with this (even now), however just because it may help someone try bonobo git server. This allowed me to create a LAN based Git repository on windows that I seem to have got to work.
I still think that my problem was trying to find good help that was relevant to what I was trying to do was lacking (or I was looking in the wrong places).
I am having a serious problem installing this (from web platform installer and from the downloaded installer). I have a laptop with win7 x64 enterprise on it.
I have read the forums and tried all the solutions I have found, from permissions, .NET framework to copying the setup files etc. These did help move the install on but in the end it always fails for the database. I have tried following MS advice on trying to read the log files to see where it fails which is why I looked at some of the solutions but the fixes didn't work. What makes it worse is the solutions for retrying the install (removal of things from the registry) has made things worse on the laptop as other stings stop working every time I remove the SQL keys.
I was hoping someone here could look over the logs to see if they could give me a better indication of whats wrong. Problem is I can't see a way of attaching a zip file here
Ok I managed to find the site, but I'm getting tired and upset so I figured if anyone knew a command line to just install tools thru the command line. SSMS on the server is no longer allowing me to change Maintinance Plans, but it can run them just fine.
I've given up on resolving that issue after exhausting 3 hours worth of uninstall/reinstall/Register DLL/Blah/Blah/Blah. Go to install the tools on my assistance computer and the idiot uninstalled Internet Explorer so now you can't launch SQL Install from the disk.
So if anyone happens to know the syntax I'd appreciate it very much, I just need the tools I don't need anything else. SSDT/SSMS/ and the like.
http://msdn.microsoft.com/en-us/library/ms144259.aspx
Try using
setup.exe /ACTION="Install" /IACCEPTSQLSERVERLICENSETERMS /Q /INDICATEPROGRESS /FEATURES="Tools"
We have multiple SSIS packages deployed on a production box. All the scheduled jobs that call these packages run fine.
Whenever I create a new package and try to deploy, I can see the folder structure and deploy fine.
Here is the problem I am facing:
When I log into integration services from SSMS, none of the deployed packages are visible. The tree structure under "Stored Packages" does not expand.
The setup is a 64 bit cluster running SQL 2005 9.0.4226
Any help would be greatly appreciated.
Thanks,
Raj
Just a couple of troubleshooting questions:
Is this problem specific to your machine?
Can you duplicate the problem from another machine?
If you log into the server itself and use its version of SSMS, does it also have the problem?
Have you tried reinstalling SQL Server 2008 on the server?
Are you able to the see File System and MSDB folders under Stored Packages or does it just never expand Stored Packages at all as you implied in your post?
If you run the following queries, do they return any values? The first query should display the list of folders including a Maintenance Plans folder and a blank folder. The second query should show all of your deployed packages if you are relying on server storage.
select *
from msdb.dbo.sysssispackagefolders
select *
from msdb.dbo.sysssispackages