I haven't been using my Squirrel SQL application in a while and when I tried to open it now, it loads all the plugins and then goes to the task bar but when you click on it, the window doesn't show. There's no error warning or anything it just goes to taskbar.
I tried reinsalling it with different versions and same happens, also clean the register and nothing
Right now i'm using DBeaver it's works alright also. but I'm curious of what happens with squirrel
Related
I am following the tutorials for reporting services on the microsoft website and currently on: this tutorial.
I am just going to the web portal on my local host, going to the data source option of the report, but it is impossible to change something when I select "Use the following credentials"( see below screen). what you don't see on the screen for some reason is that the cursor becomew a probibited sign when hovering over the field "user name" or "password".
I tried it in several browers (edge, IE, firefox and Chrome), but everywhere it is the same. I am logged on as administrator, so I would assume it is not a permission issue (altough the change in cursor makes me suspect otherwise).
I tried googling the subject for an hour or 2, but i didn't come across any useful information. As far as I can tell I configured the Reporting service correctly.
I do notice that the first time I open the "Manage" menu of a report I only see the options "properties" and "security". When Inavigate back to the menu and try again I suddenly see all menu options like you see on the screenshot. I also often get the pop up "something went wrong, please try again later"
I am running windows 10 on my laptop and installed SQL server express 2017. I did read that SQL express does not support all features of the reporting services, could that be the root cause of the issue's?
I know this is quite vague, that is also what makes it hard for me to look it up... I hope someone else out there has encountered the same :)
Thanks for the input!
To answer my own question:
I was stupid enough to use SQL Express edition and this does not have all the features required to run SQL reporting services. After installing SQL developer edition all worked as it should.
I built and successfully split an Access 2013 db. The front end worked fine for months up until I last used it a few months ago. I recently went to open the front end but the Access window was frozen whereby everything (e.g., navigation pane, menus, controls, right click, etc.) was disabled, including the window control buttons to minimize, expand and close. The only way to close the view was to right click the Access icon in the task bar or 'ctrl-alt-delete' to open task manager and force close the application. I was met w/ similar results when attempting to open other versions of the linked front end; however, I can successfully open the back end and other Access db files that don't contain linked tables. When I get the 'frozen' screen I can see my linked tables and other db objects in the navigation pane, but the pop-up login form does not display and the entire window behaves like it is inactive, similar to how it behaves when selecting items behind the active login form.
To confuse matters even worse, I have one user (User 1) who has the same user permissions as me who does not experience any of the problems I described above and can work within the front end as expected; in fact, he and I are the only active users as we are still in the developmental phase of our project. One other layer of complexity, he tried to open the file w/ his network profile from my computer and ran into the same problems. We have one other user who we've since tested this problem with and she experiences the same issues as me on both her laptop and PC.
So, I thought maybe it had to do with the 32-bit version I unknowingly had installed when my OS was re-installed last month since User 1 had the 64-bit version which could explain why he couldn't open from my computer. BUT, I still experienced the same issues after re-installing the 64-bit version on my computer. I'm at a loss on where/how to proceed from here and my IT guys have done all they can to troubleshoot my problem as they are not familiar w/ Access and aren't much help at this point.
Anyone run into this problem before? Thoughts or possible solutions? Any and all help would be greatly appreciated, thank you.
So, I disabled the code that prompted the login form and I was able to open the file. Based on User 1's experience, we determined that he hadn't installed updates since I was last able to open the file. As a result, we determined that an update I installed was not compatible w/ the aforementioned code resulting in the problems I described in my original post. I will re-create the code that drives the form's login and keep an uncoded version as back-up in case we experience similar issues in future updates so that we can troubleshoot from within the db rather than be locked out as we were.
I'm having a very peculiar issue with SQL Server Data Tools 2012. Whenever I attempt to launch the report previewer, I get the following exception:
There was no endpoint listening at net.pipe://localhost/PreviewProcessingServce7324/ReportProcessing that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more deatils.
As far as I can tell, nothing I did triggered the issue. It just started happening one day when I fired up SSDT. I tried the suggestion on
Report Designer Preview in SSDT throws up a 'end point' not found error.
However, my service is up and running just fine (restarting it didn't help), and using Setspn didn't do anything for it, either.
Anyone have any ideas?
That is a current bug in SSDT-BI. The current workaround for now is to right click on the report you want to preview in your Solution Explorer and click RUN.
You will also notice that if you try to preview the report for the first time a command prompt window opens up that runs the preview process, If you don't close this window and just minimize it then you can preview the report but I think the RUN method is much easier for now. Please mark as answer if this helped.
This can happen when you have some SQL Services installed and running on your machine that interfere with the Report Preview. You can check your current services by going opening Sql Server Configuration Manager:
To fix this you can do the following:
Type WinKey + R, input services.msc in the Run box, and press Enter.
Find the "Net.Pipe Listener Adapter" and either Restart or Disable it.
The workaround, as SQLnbe mentioned, is to:
Right Click the RDLC file from solution explorer
Click "Run" from there which will open up a new window.
The Preview issue was resolved for me when I deleted the .DATA files associated with the solution.
In my case I tried all the above solutions, and:
"Run" from context menu does not really work for me, as it's much, much longer than preview in VS2017, as rendering was a deciding factor in my work (lots of grouping by column etc). and render is much faster in VS compared to SSRS,
Could not find listed .Net services on my laptop,
Deleting DATA files did not fixed the issue either,
VS restart and reloading the solution.
I'm not sure if it was points 3 and 4 together that actually did the trick, but I'm putting it out there - just in case it actually is the procedure that will work for others, which is to try option 4.
I need to also note that this issue started after there was a momentary connection dropout. I need to work with WIFI instead LAN due to necessity to be roam-able, and every time I undock the laptop all my connections in SSMS are lost (and with them all the temp tables etc).
I faced the same issue and solved it.
Steps:
Right click on the report.
Click view code.
Check the parameters names in both query parameters and report parameters and make sure it's written correctly.
Close the report and open it again
Thanks
This is what I did:
Restart the .Net.Pipe service in the service console. This didn't resolve the issues.
Closed Visual Studio completely and relaunch the Visual Studio 2017 (in my case).
It seem that the preview is back. It could be the combination of (1) and (2).
None of the solution above worked for me. What did I found and it worked is to run Visual Studio as administrator.
Just closing the visual Studio by ending task with task manager and re-opening the solution worked for me to get through the error.
On my work PC I run all my SQL Server 2008 queries on a remote desktop connection to Microsoft Server 2008. Because of this I often have the window minimized and check it occasionally to see if a query has run.
Does anyone know if I can write any kind of script to blink the Windows 7 taskbar icon when a query completes. A pop up warning box would also work, anything to grab my attention whilst I'm surfing the web waiting for a query to complete.
Thanks,
Alex
You could set SSMS to play a sound to notify you, there's a link here that shows you how to set this up in options.
I am trying to generate the database scripts(tables,triggers,views,procedures) in sql server 2008, all of sudden the scriptting wizards hang up at the end state saying that scripting is completed but the close button never enable, if i stop this some of the tablels are missing, please advise
Install earlier SSMS version.
For me bug was at 15.0.18358.0, changed to 15.0.18338.0 and the wizard started working.
If the wizard says "0 Remaining", this means it has determined all the objects that it needs to script, and is writing them out to your destination. If you are writing to a file, go to that file location in Windows Explorer, and keep refreshing the view. If the file keeps growing in size, this means everything is fine and the data is still being written. Be patient, and eventually the process will finish and the Close button will become enabled.