I have a database project on VS 2013 migrated from 2010 and when I do a schema compare with source Database and target the DB project, its not updating the project after I pressed the update button. I have tried it a number of times but its not working. Do you you have any clue?
I was having this same issue and Fisseha's comment on another answer really helped me.
Sorry not working on that project anymore. But I remember that somehow
it got to do with setting -> application scope-> checking/unchecking
permission. I have no idea why. – Fisseha Apr 23 '15 at 15:57
By unchecking the permission box under the settings -> application scope, it was able to run the update on the data project itself.
I've been having the same problem as well. I just experienced it on my own machine.
This was when my source SQL Server instance was referenced using a server alias, ours is something like WorkplaceDev, which points to the local instance on my machine. When I set up the schema compare using WorkplaceDev\DatabaseName the schema compare showed the changes but didn't update the destination.
I then tried again referencing the database on my machine directly (JimsMachine\DatabaseName) and it worked without issue.
Sorry I'm a bit late to the party, but can you see if that makes a difference?
Related
My question is a mix of a development and an administration question, but since it affects mainly developers and refers to a development tool (Access, VBA and the Form model), I am posting it here and hope that I don't get flamed. Having said this:
I have converted an Access 2010 x64 .adp project to Access 2016 .accdb, which was not too difficult. But now, whenever I am running code which references the UniqueTable property of a form, I am getting the following error:
Run time error 2455 You entered an expression that has an invalid reference to the property UniqueTable.
This is a known issue with Access 2013 and Access 2016; see here, for example.
Microsoft has made a fix - see here.
And here is the problem: A few days ago, I have installed Office 2016 x64. When trying to apply the fix mentioned above, I am only getting the following message:
There are no product affected by this package installed on this system.
Of course, I have double checked that I was using the right version (x64) of the patch. I have not yet tried to install Office 2016 x86 and apply the x86 version of the patch, though.
Did anybody manage to actually install this patch against the x64 version of Office 2016? According to Jim Conrad's statement (second to last post here), it cures the problem, but this doesn't help if we can't install it.
Well, the uniquie table setting really not of any use in Access (non adp). As far as I can tell, the setting tells (told) Access to use the PK from the source data table, and as a result should not effect anything of value I can think of here.
What I would do is open up the form(s) in design mode in the ADP project, and simply blank out the setting BEFORE you import the table into the accDB. The issue is you can't get at and remove this non need setting in the accDB, but it persists when you copy from the ADP.
So, simply blank out the uniqueTable setting in the ADP and then import the tables. You could also write a loop, and do all of the forms in one shot before you import them into access (so, I guess working on a copy would make sense).
So the issue here is that the setting persists when you copy the table into the accDB, but THEN you can't get at, or change, or remove this setting since it is not exposed via code, or the property sheet.
So, the simple solution here is remove the setting in the ADP application before you import the forms into the accDB.
I had to upgrade the report server used by some application from SSRS 2014 to SSRS 2016.
I did the migration manually, because the old and new SSRS were installed on different machines, and I could not do an in-place update.
So the approach was (long story short):
backup ReportServer on SSRS 2014
install SSRS 2016 on new server
restore ReportServer database
update its structure to match SSRS 2016; I used Sql Compare to get structure from an in-purpose, empty ReportServer database created by SSRS 2016
added record in ServerUpgradeHistory with version for SSRS 2016 (173)
restored the Encryption keys from SSRS 2014.
Everything works ok, with one small issue.
When I try to open SSRS Web Portal URL (http://...myServer.../Reports), or to refresh main page, I get the following error popup.
This error doesn't appear to affect the functionality of SSRS - all reports work just fine. Also it does's appear when opening Web Service URL (http://...myServer.../ReportServer).
So it's just annoying so far.
I searched for the guid string in Catalog table (I thought it might be some folder name or something), but I found nothing.
Does anyone have any idea where it comes from and how to get rid of it?
Thank you
Edit
Recently I updated from SSRS 2016 to 2017, and I kept carrying this error with me.
However I found the offending item. It is in Catalog table, and it is of Type = 3 (Resource), with mime-type application/octet-stream
I deleted it from catalog (I did a backup of it into a separate table - catalog_bak), but I still get the error when I load main page in (/reports)
Beside that, it never pops-up again, with one exception: it always shows-up when I access Site Settings -> Branding
I guess it has something to do with branding packages.
Does anyone knows where are they stored, and how can I uninstall / clean-up that?
A Branding Package is created by a user. If the original package can't be found or is corrupted it should revert to the default. Have you tried removing the package or creating and uploading a new one? Also, try downloading SQL Server Mobile Report Publisher (https://www.microsoft.com/en-us/download/details.aspx?id=50400) and then connect your server with it. It may contain a theme that was used on your original server.
For me Uninstall and Reinstall did the trick for me.
I have almost spent a day but still can't find the proper solution. I am trying to connect my DropList component in Visual Studio with MySql database. DropList component is as follows:-
Server Explorer is also showing a valid database connection:
While choosing a data source for my Droplist component, Test Connection shows that everything working fine:
Selected all columns available in the respective Table:
Here comes the Issue, in the next screen when I click on Test Query, this error pops up:
I have tried creating the DB again as well as resetting the settings of both, VS and MySQL, still no success. Can anyone please guide me through this process of how to pass this error. Using Latest version of VS and MySQL. Correct Server Name, Username and Password also entered.
I have also cleared the VS Cache and other local app data, still not able to pass through this error
You might want to go back and check your steps:
https://dev.mysql.com/doc/visual-studio/en/visual-studio-making-a-connection.html
Unfortunately, even after trying everything, I was not able to make all this work with MySQL Database. I repeated all the similar steps, as explained in my question, by moving to Microsoft SQL Server 2017, and it worked like a charm just in seconds, without any errors. Attaching the picture below after migrating to Microsoft SQL Server 2017 from MySQL 2017 :
I know this is kind of weired issue, but I'm unable to find a fix after searching for it.
In VS2015, add new 'ADO.NET Entity Data Model' process, After selecting the data connection Entity Data Model Wizard gets closed instead of proceeding to next stage(table/sp selection).
Does anyone had similar issue and can help me fix this? I've restarted VS, my machine too, no change.
I'm using:
Visual Studio community 2015, Version 14.0.25431.01 Update 3,
MySql Connector 6.9.9
I've got the solution, I've removed the MySql Connector(using MySQL Installer) and added it again and it works now.
So, I'm trying to get set up my MySQL and ASP.NET.
Currently, I have both Visual Studio 2013 and Visual Studio 2015 installed on my PC. I used this installer for MySQL (Basically one that comes with everything you need to get started, including MySQL For Visual studio): MySQL Installer
Anyways, as a quick test I made a new ASP.NET MVC project, connected to the database in the server browser (which works just fine!). However, I then tried to create an ADO.NET model from it. When I come to the step of generating the model from the database, I get this error/exception:
This happens in both Visual Studio 2013 and Visual Studio 2015.
I have tried to search my way out of this (I've also tried with different databases, I used some of the sample databases included with the MySQL server installed, still got the same error), but I don't seem to be able to find much information on it. Additionally, it might be worth noting that when I select the version of the Entity Framework to use, I get this:
Which seems odd as I'd think the newest MySQL installer did actually include MySQL for Visual Studio which supports EF 6.x?
Anyways, any assistance or hints on this problem will be much appreciated :)
EDIT - Narrowed down the problem a bit
So, I found out that this problem occours whenever I have a database with foreign keys in. Still no clue why, but databases without them I can easily generate!
Try to run this command on MySQL WorkBench:
set global optimizer_switch='derived_merge=off'
Good luck!
If you have many schema inyour database, the Global parameter is not your solution.
test with : set session optimizer_switch='derived_merge=off' to impact your schema and not the entire base