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.
Related
I am trying to utilize windows task scheduler to distribute Access reports to End Users in my company.
All I am doing is triggering a macro that runs code from a module which exports a report to a PDF, prints it out, then exits access.
DoCmd.Quit acQuitSaveNone
That's what I've been using at the end of my code in VBA to close access after running a macro.
When I manually run the macro it works fine, but when scheduled on a task, it gets held up a lot and stuck.
I've checked event viewer to try and find any Microsoft Office alerts but do not see any.
It appears that Access is unable to quit many times when running through Task Scheduler. Would there be a VBS I can run, say, 5 minutes after the task to close down the .accdb file and MSACCESS.EXE or is there something I can do to make these Tasks actually work??
It seems maybe when running in the background through task scheduler.. the code is getting ahead of itself and trying to quit at the same instance that it is finishing the output to the printer, causing it to seem "busy" and unable to actually close?
I have an entire domino of code that shoots off after this but it stops dead in its tracks when it cannot finishing closing access.
Any suggestions?
Thanks,
Ian
Here is the gist of what I would do, I am just addressing the print on open and quit actions. You may need to tweak to ensure that you have validation etc in place.
First, make sure that your report has a default printer specified. (Report design-->Page Setup-->Page-->Use Specific Printer and then select your printer)
Create an Autoexec (auto execute) macro, this macro will be saved with the name Autoexec. Macros named Autoexec executes when Access is opened automatically. Note that once you have this macro, it will run each time you open Access, to prevent it from running, hold down the shift key and then open Access, this bypasses the Autoexec
First action in your Autoexec Macro is OpenReport and set the View to Print (report is printed when opened)
Next action in your Autoexec Macro is QuitAccess with options set to SaveAll.
When you run an application from the scheduler, it runs with different credentials. You want to make sure that you choose the appropriate options here.
Fixed it. Very glad as I've seen many with this issue and hope this gets to them.
If anyone has any issues regarding access macros and task scheduler and this doesn't work - I'll be happy to help as best as I can as the frustration of wanting to remove administrative tasks through automation that don't work out is just terrible.
Since I needed the task scheduler to wake the computer up, log me in, and open access databases on network drives that reference SQL servers.. there was a couple things I had to make sure were set up.
First is trusted locations. Any network drives you are access should probably be in the trusted locations.
Secondly, my last command on the macro is DoCmd.RunCommand.Close (I believe.. if im wrong Ill change tomorrow when I'm back in the office)
Third, use the root path to the network folder and not a mapped drive as they may not map when your logged off... so instead U:\file path... would have to be \computer1\filepath\ etc..
This path should be made with all linked tables or databases among the network especially if you have code calling for those files.
Fourth, I ended up having to do it the less preferred way and have a folder called "accessjobs" where I put shortcuts to Access Macros which triggered code and simply ran that path in task scheduler with "start in:" the folder the macro shortcut is in.
Fifth I had to run with highest privileges, and selected "run whether user is logged on or not"
A couple of these things may be coincidental that they work, but I am not about to spend even more time with trial and error to see which settings are benine as I spent TOOO long figuring this all out. But now it is solved and the sky is the limit now!
Thanks for the help!
Ian
So I started with the Access contact database template and have been building up from there. There is a functionality in which by clicking on the ID number in the Contact List, it should call up the form to edit the details. I have made no changes to this code, and have even tried recopying it from the template from scratch.
However I am getting the error "A problem occurred while Microsoft Access was communicating with the OLE server or ActiveX Control." It is telling me to restart the OLE server and try the operation again.
I have an old version of the database saved, and it runs fine over there. It just is something within my code here.
Any guidance would be appreciated.
All of solutions I found online was not working for me.
Found that only rebuilding damaged form from scratch help me to solve this issue.
W10, Office 2016.
I have ran into this error three times in my database. Each time to fix it I simply just open a new blank project and import everything from your old project into your new project.
This might sound like a large undertaking basically you just go into the new project and select "Import Access Database". Then just run through the wizard selecting everything in your current database. Click okay and let it run for a few minutes.
This has fixed it for me every time I have run into your error. I suspect it is just something to do with corruption.
My programs also run into this error sometimes.
I have recently noticed that the error most often occurs on UNBOUND forms (forms without a RECORDSOURCE).
What I have done most recently for these forms is the following:
Add "some" table (I usually take a Config table with just one record) as the RecordSource.
Compile the program code (this usually goes well, even before the fix!).
Save the form
Open the form. This should work fine now!
Remove the form's RecordSource, recompile and save again.
The form should still work fine!
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.
Last week I was modifying portions of two modules in an access 2010 db when the program crashed, and would crash every time I tried opening up the db thereafter. I was able to create a new database and import the tables and queries from the corrupted one, but when I tried to import the forms/macros/modules the new database would start crashing also. I keep daily backups, but ended up losing several hours worth of work. This happened twice last week, each time MS Access would crash without warning and the VBA was unrecoverable.
The functionality works as intended until the db crashes seemingly at some unknown point. There must be some sort of issue with my VBA code, since this only started happening when I started modifying the module last week, but I can't pinpoint it since the crashes actually occurred when nothing was being executed. Ie during save.
Does anyone know if it's possible to export the VBA out of access without exporting it to another database? Ie export it without having to use MS Access to do so. On a related note, has anyone created a library that exports query definitions, table schema, and all VBA to text files that I could drop them into source control?
Thanks.
In addition to the method suggested by #Remou, you could try the SaveAsText method to save a code module to a text file.
Application.SaveAsText acModule, "Module1", "D:\Access\Module1.txt"
However, that doesn't satisfy your desire to do it without using Access.
Try a decompile operation on the chance your project includes saved compiled code which has been corrupted. You can find detailed instructions for decompile in the 2 answers to this Stack Overflow question: ms-access: HOW TO decompile and recompile
After decompile, make sure all your modules include Option Explicit in their Declarations sections. Check the project's references, and fix any that are broken (missing). Then run Debug->Compile from the VB editor's main menu to verify your code compiles without error.
Those steps are the best I can offer to reduce potential for continued corruption problems.
For integrating source control with Access, start with this selection of related Stack Overflow threads: site:stackoverflow.com ms-access version control
Folks
We're having the same problem. There is a bug in SP1 that causes it. If you keep opening the database, you'll finally end up with a backup that works - rename the old one BROKEN and remove the _backup from the new database, and you are oky till your next bit of development. Our IT guys (Microsoft Gold Partners) are looking at a fix reported on http://answers.microsoft.com/en-us/office/forum/office_2010-access/access-2010-sp1-you-receive-random-crashes-in/d2bf6175-075a-4a12-a2b1-f55d40af271b
I may go take a look at decompile/recompile however as some of our database have come all the way up from Access 97, to 2000, 2003 and now as mdb/2003 file format still, running under 2010. Having said that, converting to accdb/2007 seems even worse!
I have created a SSAS project and it works perfectly fine my cubes, data-sources and such first time I deploy the cube, but if I change the data in my database and I click Cube>Process in BIDS it will not reflect the new changes even though when I retrieve the table data in SQL server Management Studio the table shows my data is changed.
I have also tried updating the cube in SSIS package using the Analysis Services Processing Task. However, the changes in my underlying data is not shown. It stays the same. Can anybody give me the few possible scenarios that can cause this problem.
Much appreciated
Thanks in Advance
First step is to verify that the datasource ON THE SERVER (not locally on your dev machine) is set to the correct database.
Are you processing the whole project or just the cube? I noticed that I have to process the top level item in the solution explorer. Processing just the cube was not enough.
Do you get any error messages?
Try processing the dimensions first and then process the cube.
I am not an expert myself, but I understood that there is a difference between updating ("process") and "deploy".
So when you create or add dimensions you will first have to deploy the cube to the analysis server and then process it.
Later when there is new data in your datasource, you can just process the cube (it's already deployed) to update the data.
Try this:
Identify which Dimension or Fact Table data you have updated.
Goto the SSAS project you have created in Visual Studio for the CUBE.
In the Solution Explorer expand Dimensions folder.
Right Click the Dimension or Dimension related fact table for which data is updated and Click on Process.
Then once the Process window is opened then do confirm in the window then Object Name = and Process Option = "Process Update".
Then Click on run on the bottom of the Process window.
Verify the process is succeed, if failed then fix the errors.
Go to Browser Tab of the CUBE and check the data is updated.
Any changes made to the cube structure i.e. adding new measure(s) or business intel. will reflect merely after processing the cube, there is no need to deploy the whole project again. However if any changes are made in underlying data or data structure, then the whole project needs to be deployed.
Changes can be seen right after processing/deployment in Cube>Browser but will take some time to be realized in SSRS because of caching.