I have a strange situation. IT installed SSMS on my laptop and it runs well the first time, connected to my SQL servers remotely etc. But then it's frozen. I forced quit and then started SSMS again. Now it's totally frozen, no popup window at all to enter the server-connection text string. Then I did a force quit and got a pop up window (see it here ).
Microsoft SQL Server Management Studio has detected that an operation is blocking user input. This can be caused by an active modal dialog or a task that needs to block user interaction. Would you like to shut down anyway?
Has anyone seen this before? My IT department has no clue.
Often this is due to the new connection dialog being off screen (usually due to changing monitor setup e.g. 1 to 2 monitors or resolution change etc).
If so the really easy fix (if your connection dialog just needed approval without changing fields) is :
Focus on SSMS and Hit Enter/Return
..or the easy fix (if above does not work - as your last connection is not ready to go) is:
Alt Tab to SSMS
Alt + Space - context menu
M - select Move (in offscreen context menu)
Arrow Key(s) - to move it back onto screen
As per answers here from #Eirik Toft and here from #Lee Chetwynd
Fixed an issue which presented the same on my machine today by renaming a entry in my registry:
After some digging there seems to be multiple issues that can produce the same error (Application, settings, registry). This blog entry covers it pretty well:
http://www.armedia.com/blog/2012/08/sql-server-management-studio-freeze/
In my case deleteing the SQL server management studio folder under AppData ( c:\users\%userName%Appdata\raoming\microsoft\ ) didn't work.
However I was successfully after deleting / renaming the regisitry entry:
[HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL Server]
(update)
Worked out the underlying issue on my laptop - was using additional 2 screens with much higher resolutions which caused windows / SSMS to open up the connect to new data source dialog off all of them. If your using multiple screens try returning to just use the native laptop screen to see if you can find the dialog that SSMS is waiting on your input for.
I just had this same situation, with two additional screens connected to my laptop. SQL Server Management Studio was opened on the third screen, with the modal dialog nowhere to be seen.
Two options:
Press tab three times and enter. This cancels the dialog. Now you can move the window to another screen.
Set Windows to only use one or two screens. SSMS opens on the first and should still open there when you move back to using three screens.
When SSMS is on your primary or secondary screen, the modal dialog opens on the first and should be usable.
It was because multi screen display. Turning off multiscreen to single one resolved it. Reenabled multi screen display after ssms started working
In my case, "Run as Administrator" option worked like charm. I was accessing my server screen with the windows RDP. And when I open SQL Server Management Studio and Visual Studio 2010 user hangs at the moment and wont operate unless sign off r disconnected by administrator.
But when I set compatibility mode of both the application to the "run as Administrator", it starts working fine.
the problem also occurs if you have a touch screen. I fixed this by disabling the local thouch screen when I switch to RDP.
Related
My Android Studio (0.4.3 now) often displays a message that is ready to update, but the alert does not have an "Update and Restart" button:
I want to install this update but I don't know how I can do this. After I click the "Remind Me Later" button few times, the fourth button on the left is sometimes visible, allowing me to download and install the update. I haven't discovered any pattern when this button shows up and when it doesn't.
Why isn't it always visible?
This is bug https://code.google.com/p/android/issues/detail?id=56737. If you dismiss the dialog and check for updates again, you usually get the button you're looking for. I don't know why this happens.
I have found a temporary solution for this problem (until they release a fix for it).
When Android Studio opens and the update popup shows up without the button, close it with the X button.
Press Ctrl+Shift+A to open action search dialog, enter Event Log and open it.
There will be a message telling that Android Studio is ready to update and the word update is a link that will open a window with an Update and restart button.
Actually this issue is kind a bug not really a bug :). This is what you need to do
When an update is available, you'll see a balloon notification in the IDE.
Two important known issues:
1. The first time, you'll see a dialog that asks you to accept this channel. You need to press "More info" to accept this channel, otherwise you won't get notified about updates.
2. If you press the "Ignore This Update" button, there is currently no mechanism available to revert that decision and Android Studio will never tell you about that update ever again.
For more info. visit : Android Tools Project Sitebelow is snap from android tools official site
I am not sure why the button is not available, It might be possible that the version you have currently can't be upgraded to the latest version directly.
In such cases follow the steps mentioned below :
Download the latest OS respective Android Studio as zip(sdk excluded) from here :
http://tools.android.com/download/studio/canary
Extract the downloaded Zip file somewhere
Close Android studio if running.
Go to current Android Studio installation directory.
Take a backup(safer side) of that and replace everything except sdk directory
with the content of extracted Zip file .
This also allows you to update studio in an offline system.
Clicking on 'ignore updates' and rerunning Check for updates for a couple of times did the trick for me.
I have created a custom Close Opportunity script which is complete replica of CRM's default opps.js with exception that it has couple lines of code that I've wrote. I replaced default Close Opportunity ribbon buttons with my own and made everything work as it should work. There's one little problem I can't understand though.
I'm using VPN and remote desktop connection when I'm developing in this particular case. Everytime I open VPN and connect to the remote desktop, then open CRM and then click my Close Opportunity ribbon button my script wont work. Opportunity is closed correctly, but my custom logic is not run. If I reactivate the opportunity and close it again or in addition close another opportunity everything works just fine. I can't repeat this problem in any other way than just closing remote desktop and disconnecting VPN and then connecting again.
But that should not have nothing to do with how CRM works right? Or is there some cache or something I'm not aware of but which could cause this problem? Anyway, I'm keeping myself busy with this but any advices are welcome.
Edit: And I have tried to clear Internet Explorer's cache etc.
Can we see an example of the code?
Also when calling a webresource from the ribbon remember to reference using "$"
Example $webresource:SomeScript.js
When I run or debug a winrt application, Visual Studio 2012 seems to start it always on the same monitor.
How can I force Visual Studio 2012 to start the app on my other monitor?
Windows will deploy to which ever monitor you last viewed the Start screen on. So, here is what I do.
Start VS in Main Monitor
Bring up charms bar on Secondary monitor and select the Start charm
Launch debug from VS in Main Monitor
Your app should now launch in the secondary monitor.
I don't know if there is a way to set an option to do this - I haven't found one but haven't looked very hard since this works easy enough for me.
On Win8.1, it seems like the app always opens on the primary display. I swapped my primary and secondary displays (right click on desktop -> screen resolution -> "Make this my main display").
I also customized my taskbar so that it appears on all monitors (right click on task bar -> properties -> "Show taskbar on all displays").
I think, it is impossible.
The only solution you have is to move it to that monitor and then open Start Screen only on it while debugging.
In this case Win Store apps will open there
You cannot force the app to start on the second monitor but you can move Visual Studio 2012 to the second monitor and start the WinRT app on the first monitor. Swap or move the primary monitor if needed.
You do just active the Metro screen where you want to start the app ! Or after you can use these shortcut : Win+PageUp and Win+PageDown to switch
You can also drag the app itself to the alternative monitor. As others have noted, the apps will continue to open on the last monitor that you used.
Update: If you have Visual Studio 2013, the latest update remembers which monitor was being used to run the WinRT app and opens it on that screen.
I am taking a class and our instructor gave us a file to download called cs.bak and its supposed to be formatted for the version of SQL we are using. So I downloaded the one for Microsoft SQL Server.
Well I tried to do the restore but when I get to the part that I choose device and locate the file cs.bak it loads and now I am suppose to be able to choose destination. Well after I choose destination I do not have the OK button to go through with the restore.
On these instructions http://www.katieandemil.com/sql-server-2012-restore-database-backup-file
If you count the window screens. I can only get as far as the 6th screen.
I am suppose to do this, "Some questions will ask you to write out query results from a database. In order to answer these questions you will need to have the example database available to you."
Well I can't open it to do this. Any help would appreciated. Thank you.
Check this:
This checkbox might be unchecked - and then the [OK] button remains disabled...
This seems to be a Windows Layout issue. To resolve this, reset the SSMS Window Layout by selecting from the main menu Window -> Reset Windows Layout.
I have a virtual machine (VMware) with Mercury Quick Test Professional 9.2 installed. I have a script to test an application, written in VB.NET using the Infragistics library.
If I access this virtual machine using my laptop (using Remote Desktop), everything works fine, the script completes without a problem. My laptop runs XP, with Windows Classic theme.
If I access this virtual machine using another machine (using Remote Desktop), the script starts fine, but stops halfway through, without no error message from QTP, nothing. This machine runs XP, with Windows Classic theme.
One difference between the two setups is the size of the screen, the laptop is 1920x1280, other machine 1280x1024.
The step where the script stops involves checking a checkbox within an UltraWinGrid. The checkbox itself is displayed, is on the screen in both cases.
Has anyone had this problem before, or have any idea why the behaviour is different between the two machines?
Thanks.
OK. I've found the problem. In fact, the script was failing silently because that's what the person who wrote the script told it to do. It couldn't validate something which was off screen, so the script failed.
The problem was the QTP definition of 'off screen'. I have two screens attached to my laptop, the screen for the laptop itself (1920x1200) and another screen (1280x1024). I connect to the VM for QTP using remote desktop, and it uses the settings of the screen for the laptop. This means that when I launch my QTP script, and move it to the other screen, it doesn't fit, so the screen is no longer maximized, and the object is partially off screen, so can't be found.
The fix is simple: in the Remote Desktop, use the Display tab, and set the size of the screen to a size to 1280x1024, and QTP doesn't have any more problems.
Voilà.
If you are not using Expert Mode, and / or are allowing QTP to do most of the work to create your repository objects, then yes it is referencing everything by pixels.
I create all of my repository objects by hand, viewing the source (in the case of automated web-application testing) and using the Object Spy for assistance where needed. I make a point to not have any positioning information as part of my object definition, for the very reason you are running in to.
For the parts of my web-app that interacted with Windows (opening a file to upload, etc.) the Object Spy was essential for the trial and error necessary to create a unique identifier for creating the repository object. But it can be done.
Ex1: File Browse Dialog
text = "Choose file"
nativeclass = #32770 (apparently some Windows VooDoo for a file open dialog?)
Ex2: Filename textbox in Browse dialog:
nativeclass = "Edit"
attached text "File &name:" (more Windows VooDoo? It woudn't work for me without the "&")
Ex3: Open Button in the dialog:
text = "&Open"
object class = "Button"
Good Luck!
Point of clarification: You mentioned that QTP stops with no error message. Does that also mean that the test results log file also has no error message? If the log has any information, that may be helpful in diagnosing the problem. Could you share the lines of code at the point where the script fails?
Also, remote desktop will resize the desktop on the remote machine. Although QTP scripts are not inherently coordinate based, individual statements can be coordinate-based relative to an object. The resolution could be an issue in that regard. For example, imagine you had a line like Button.Click(5, 150) recorded on a higher resolution machine. But if you attempted to play it back on a lower resolution machine, and the 150 is out of bounds of the object on the lower resolution, it could cause an issue.
QTP does not use screen coordinates except as a last resort, if the objects are identified as high level objects (SwfTable in this case) you should be OK, if however QTP doesn't recognise the object it falls back to WinObject and screen coordinates.
If you're using Infragistics then you should know that they extend QTP's support with their TestAdvantage product which will probably solve your issue.
Edit:
#MatthieuF said:
In fact, we use the Infragistics plugin for QTP, and we still have the problem
Can you give me an example of a line that fails?
A few things:
You should be able to debug on the VM easily - just wait for it to stop, go into your object repository, and see if it can identify the object. If no then use object spy to figure out what properties are different between the OSes. If there is a difference then you can always set that property to a regular expression and have it check for both possibilities.
Assuming that isn't the issue we've run into problems using remote desktop with QTP if the Remote window is closed or minimized. For us, it was an issue where the clipboard can not be changed when an RDP window isn't visible, but there could be other surprises when using QTP that way.