I have a cube in SSAS that work well. I access the cube via Excel/connection and create a pivot table.
But when I add one new specific dimension into it I am having problem:
As soon as that new dimension is in the cube, I can still create a new connection to it, but when I close the file and reopen it I got the following message:
"Excel encountered unreadable content in [filename.xlsx]."
Then the connection doesn't work anymore and the pivottable is empty, we have to recreate the connection and the pivot table... all working well until we close the file.
I tested it and the issu is only there when I add that dimension.
Since the error message is useless and I can't figure out what is the cause of the problem, I am asking you guys.
Any idea what it could be ?
Do you have a list of things to check?
Any help would be appreciate, thank you
I removed one by one the column/attribute from the dimension to see if and what attribute is causing the issue and I found it and removed it, even if I do not understand why it is cause an issue.
Related
I am using visual studio with sql server, i am in a middle of a practice and faced a major issue.
The issue was in the first place, when i was creating a product table , by mistake i mistyped as a categoryId ctegoryId, and later i recorrected it by thinking its over.
And now I am almost done with the identity scaffolding when updating my database, I am facing such an error. and I've tried all ways to update it by myself but failed.
I need an expert guidance so I can continue my path till the end.
I do appreciate any solution from your side.
Thanks indeed [Migration error "Each Table must be unique"](https://i.stack.imgur.com/tB3iT.png)
Just to let you know, I have deleted my migration and reinstalled again without[NotMapped]in my product table"categoryID" and it worked back normally.
Now i am using Microsoft Access 2016 and suddenly i can't open one of my tables.Its say "Not a valid bookmark".
After using compact and repair,that table is missing.
I can't export the database,That error is always.I have no idea why.
I was checked other answer and It doesn't make clue.
Please help me.
That's a corruption issue. Running C&R is your only method to get it cleaned up.
So, revert to the latest backup, restore data otherwise somehow, or - if essential and valuable data are lost - contact a paid restore service.
A reputable service can be found here.
Not sure if you made a back up before C&R so whether or not you still have that trouble-table.
Create a brand new db. Import into it everything from the problem db EXCEPT that trouble-table. Sanity check that all this behaves ok.
Create another new db - and import into it only the trouble table. It probably still won't open but it might. If it does - export the data out to excel; create a new table in your other new db; and import the data back in. If it does not open try another C&R with this new db file. If still no joy I think you'll have to create a new table.
You'll want to try and determine how this happened - I rarely see a totally corrupt table. A move to a new edition i.e. 2016 - if it is a big jump such as from 2003 - I have seen where things are less forgiving. Be sure if this is multi user that the db application is split and every user has their own front end file - this is the primary cause of corruption these days.
At the early stages of development, where data retention is no issue and experimental changes to the schema are expected to be numerous, is there a way to avoid migration? Namely, just to dump the database and start over each time.
Everything I try leads to the error: "The model used to open the store is incompatible with the one used to create the store".
Lightweight migration looks do-able, but I'll end up lots of unwanted versions and messy code. I'd also like to experiment with relationships (no wise cracks), but understand I'd need to commit to a heavyweight migration afterwards!
If the solution is to check for the existence of the original database using NSFileManager and delete/remove it if found, could someone please show the swift code with an example name of the original database, and how it can be effectively removed.
I've been trying several suggested solutions, such as dragging a copy of the .xcdatamodeld file onto the desktop, deleting the file in xcode and bringing it back in, but I keep getting the error that the model and store are not the same.
Answered in one line in first comment, but appreciated in reverse proportion.
I’m getting this error: “Field ‘[tableName].fieldName’, which is included in a
join clause , does not exist. Unable to connect to the server "serverName".
Check that the server is running and that you have access privileges to the
requested database.Errors occurred while trying to load the workbook
"/views/reportName". The load was not able to complete successfully”.
I don’t have this problem in the desktop version but I get
this error in the server version. Apparently if I refresh several times the
report eventually loads. I started having this problem after modifying my sql
server table but the field names are same as the pre-modification. Any help
would be greatly appreciated. Thanks.
Try loading the workbook in Tableau Desktop and checking for any invalid dimensions, measures, parameters or calculated fields (they may have a red exclamation mark next to them). Once this check has been done, try republishing the workbook.
Failing that, send an email to support#tableausoftware.com, describing the issue in as much detail as possible, including a screenshot of the error and, if possible, a copy of the workbook and they will help resolve the issue.
I am having a very frustrating problem with my current project. It is continually losing the connection string binding for Entity models.
I have multiple models for different databases in separate areas and was having no problems. Suddenly now whenever I try to update from the database I get the connection string setup prompt. I select for it to add it to the Web.config with the password but it doesn't ever pick it up there again. They all are still in the web config but it just doesn't see them.
If I remove all the connection strings from the config file it will write the new one there. Then when I try to set up a Stored procedure/Function Import, I still get the statement in the lower box:
No database connection has been configured for this model.
I have tried rebuilding the project and creating the models again from scratch and that works for a while. When I try and bring the project in under Perforce source control, it winds up getting re-corrupted & the connection string goes away. It affects all of my models too.
I am also using EF 4.x DbContext Generator to create context files. They work fine. I am also able to run the application and it connects to the database just fine and returns data. No issues there. I am just unable to update Entity Complex types from the DB or import any more stored procedures.
An even weirder occurrence was that I opened a broken project from a different directory then opened an uncorrupted copy it instantly became broken also. Contagious!
Any thoughts on where to look into to see why this is happening? Has anyone else had this issue?
I seem to have found where the issue is coming from.
I seem to have a bad value somewhere in my web.config which causes the issue. Here is the work around I found did the trick and showed it's the config:
When the binding breaks, I closed the project then swapped out the web.config with one from a good build which was missing a couple keys but worked well enough to bind.
I reopen the the solution and the "No database connection..." error goes away.
Then while the solution is still open I re-swap the web.config back in and it still works.
This is far from optimal but I can work until I figure out the bad value via doing some compares.
I will comment on this again once I determine the exact issue.