Exception upon adding a new document to Raven DB Management Studio - ravendb

When I click on "New Document" in the Raven DB Management Studio, I see the following exception:
[Arg_TargetInvocationException]
Arguments:
Debugging resource strings are unavailable. Often the key and arguments provide sufficient information to diagnose the problem. See http://go.microsoft.com/fwlink/?linkid=106663&Version=4.0.60831.0&File=mscorlib.dll&Key=Arg_TargetInvocationException...
Any ideas on how to solve this?

This fixed the problem for me:
Upgrade to version 531 as recommended by Ayende

Yes, the 531 build fixed this error.
Read more about it at RavenDB's google group

Related

How do I deploy the data to the %programdata% directory when compiling a executebal in vb.net

I created.exe file and installed it on my machine.When I insert data I get an error "Failed to update database "Database.mdf" because database file is read-only". I am able to view the data but cannot insert the data. I am using local sql database and visual studio 2019. My connection string is:
Data Source=(LocalDB)\MSSQLLocalDB;AttachDbFilename=|DataDirectory|\HovedDatabase.mdf;Integrated Security=True
I have read a lot of topics on the forum about this and so fare I have changed the settings to the db in the SSMS, so that it is not longer a permisson issue.
But it still gives the same error. One thing I havent tried, because of lack of skill, is deploying the data to the %programdata% directory. It looks like this advice is given regarding this issue. So anybody have a idea on how to do this in Visual Studio. I am pretty new to this so dont be afraid to give detailed instructions :) Thank you in advance :)

Why am I getting this error from azure sql? Error Code [70527]

I am encountering this error in azure SQL [70527] any suggestions on how to fix this? This is the first time I have encountered this error.
I would appreciate any advice at all, I'm at a loss how to fix this issue, I am not well versed with azure SQL at all
I am assuming you are migrating a database from on premise sql serve to Azure. I suggest you use the migration agent which will highlight all these issues with possible resolution in some cases.
The error code 70527 is related to user login which is highlighted in the following post as well
SQL70527 error in database project
You may have to create the user as per suggestion in the post above using the script method rather than the backup restore.
You can download the migration agent from below link
https://www.microsoft.com/en-us/download/details.aspx?id=53595

Db2 database creation problem

I've just installed DB2 v8.1.18.980. Now I try to create new database. I'm getting the error with the following sql codes:
sqlcode : -902
sqlstate : 58005
Unfortunately the error itself in Russian, as a result, I cannot paste it here. Official site says the following about the problem:
"The statement cannot be processed. The application program is not permitted to issue additional SQL statements. For example, a recovery routine associated with the application program may not issue additional SQL statements.
Programmer response
Rebind the failing application program and try again. If the problem persists, examine your DBRM and make sure it matches your program."
http://publib.boulder.ibm.com/infocenter/dzichelp/v2r2/topic/com.ibm.db2z9.doc.codes/src/tpc/n902.htm
But, it's not clear to me. Any ideas, what can be wrong and how to resole it?
I'm using Windows 7 Ultimate if it may be an issue.
The documentation you linked to is for db2 v9 for z/os, not db2 v8 for Windows. So that's the first problem.
The documentation for v8 has this to say about SQL 902:
A system error (reason code = reason-code) occurred. Subsequent SQL statements cannot be processed.
Explanation:
A system error occurred.
User Response:
Record the message number (SQLCODE) and reason code in the message.
If trace was active, invoke the Independent Trace Facility at the operating system command prompt. Then contact your technical service representative with the following information:
Problem description
SQLCODE and embedded reason code
SQLCA contents if possible
Trace file if possible.
Federated system users: isolate the problem to the data source failing the request (refer to the Troubleshooting Guide to determine which data source is failing to process the SQL statement) and take the necessary diagnostic steps for that data source. The problem determination procedures for data sources vary, so refer to the applicable data source manuals.
sqlcode: -902
sqlstate: 58005
Which brings us to the second problem: it's asking you to contact IBM and open a ticket, and as far as I know v8 is out of support so it won't be that easy.
I think installing v9, v9.5 or v9.7 would be your best bet, unless you have a really compelling reason to stick with 8.

Visual Studio Adding Data Connections - Given Key not Present in the Dictionary

I've read through a couple of previous similar questions and none seem to provide a fix.
so i ask again.
I'm using Visual Studio and am trying to connect to a DB in Server Explorer. Regardless of what database i try to connect to it gives a "Given Key not Present in the Dictionary" error.
i have tried with SQL CE and SQL Express 2008 databases and each give the same issue.
I can connect quite easily with SQL Management Studio Express so i believe the Databases are the same.
Thanks in Advance.
after a lot of time searching for the answer to this i found the solution here
this is not really a workaround but in fact a SOLUTION, how to get rid of the error, in case you have missed to remove all connections before removing the provider:
edit C:\Users...\AppData\Roaming\Microsoft\VisualStudio\10.0\ServerExplorer\DefaultView.SEView and remove the connection with the wrong Provider manually. If you do not know which of the provider is failing, simply delete the file :)
If this won't help try deleting also C:\Users...\AppData\Local\Microsoft\VisualStudio\10.0
PS: you have to quit all instances of visual studios first or the files will be re-created from memory ..
The second part only worked for me , deleting the whole folder.
I had recently installed the MySQL Connector, and had multiple instances of Visual Studio open. After shutting them all down, I was able to add a connection to the Server Explorer.
Adding to what BastanteCaro said, I had open the DefaultView.SEView file in case I needed to go down that path. When I shut everything down and started up a new instance of Visual Studio, Notepad++ reported that the file had changed. So either there was an uncommitted change to the file or some sort of cleanup/addition was made on startup.

Error when restoring SSAS cube: MemberKeyesUnique element at line xxx cannot appear under (...)/Hierarchy

I'm getting this error when trying to restore an SSAS database from a backup:
The ddl2:MemberKeysUnique element at line 63, column 4862 (namespace http://schemas.microsoft.com/analysisservices/2003/engine/2) cannot appear under Load/ObjectDefinition/Dimension/Hierarchies/Hierarchy.
Google hasn't turned up any helpful solutions. (a lot of people found that installing SP2 made the error go away but this has always previously worked in our environment)
I don't really understand what the error means. Can somebody interpret or suggest a fix?
Thanks,
Phil
I'm investigating this same issue. As far as I can tell it is because SSAS 2005 pre SP2 does not support the MemberKeysUnique property. This was a bug which was fixed in SP2.
My suggestion then would be to remove this property from the source, re-backup then restore; otherwise, upgrade to SP2 and try restore again.
Cheers