August 31, 2012 at 8:05 am
The dimensions have processed Successfully prior to the updating of the SEN Cubes
The attribute key cannot be found when processing: Table: 'fact_SEN_Workflow_Steps', Column: 'DW_Prov_ID', Value: '370194'. The attribute is 'DW Prov Child ID'.
Checking the Source data and this attribute key matches the dimension so it’s fine.
Can I check the dimension now that the cube has failed?
Analysis Services…. Dimensions….. Provisions
No it doesn’t allow you to check for an ID Can I do in in SMS using MDX?
Q. Can you do this in MDX SELECT * FROM dim.Service_Prov WHERE DW_Prov_Child_ID = 370194
You cant browse the cube in Alalysis Services or SMS ‘ Error Loading Metadata. No Cubes were found.’
If I run it in Analysis Services on Full it succeeds which means I can never actually test for this issue.
Once it Suceeds when manually processed in Analysis Services it works in IS. Then fails again during the overnight.
Ive put this into the forum before and didn’t get anywhere but I thought Id try again because surely it can’t be me having these issues.
Can I get it to ignore errors and send them to a report so I can see what it thinks has happened and still have a cube I can look at at the end.
I have been totally stuck with this for months and haven’t got any further.
August 31, 2012 at 10:32 am
Not sure I can be much help, but "stuck for months" got to me.
When I get a cube processing error, I usually can fix it by processing each dimension separately and then re-trying. Sounds like you have done that AND checked that your fact key does, in fact, match the dimension key. At least, it sounds like you have done that?
I don't do MDX querying, I query the underly SQL dim table to see if that key is there. Sounds like you cannot access the dimension data ?
Process Full on the cube should process all dimensions,too. When you do that manually, all is well? I do not use the AS components in SSIS, my SQL Agent cube does it for me:
<Batch xmlns="http://schemas.microsoft.com/analysisservices/2003/engine">
<Parallel>
<Process xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ddl2="http://schemas.microsoft.com/analysisservices/2003/engine/2" xmlns:ddl2_2="http://schemas.microsoft.com/analysisservices/2003/engine/2/2">
<Object>
<DatabaseID>Fake Cube</DatabaseID>
</Object>
<Type>ProcessFull</Type>
<WriteBackTableCreation>UseExisting</WriteBackTableCreation>
</Process>
</Parallel>
</Batch>
Hope I've at least given you a few ideas. Good luck!
Debbie Edwards (8/31/2012)
The dimensions have processed Successfully prior to the updating of the SEN CubesThe attribute key cannot be found when processing: Table: 'fact_SEN_Workflow_Steps', Column: 'DW_Prov_ID', Value: '370194'. The attribute is 'DW Prov Child ID'.
Checking the Source data and this attribute key matches the dimension so it’s fine.
Can I check the dimension now that the cube has failed?
Analysis Services…. Dimensions….. Provisions
No it doesn’t allow you to check for an ID Can I do in in SMS using MDX?
Q. Can you do this in MDX SELECT * FROM dim.Service_Prov WHERE DW_Prov_Child_ID = 370194
You cant browse the cube in Alalysis Services or SMS ‘ Error Loading Metadata. No Cubes were found.’
If I run it in Analysis Services on Full it succeeds which means I can never actually test for this issue.
Once it Suceeds when manually processed in Analysis Services it works in IS. Then fails again during the overnight.
Ive put this into the forum before and didn’t get anywhere but I thought Id try again because surely it can’t be me having these issues.
Can I get it to ignore errors and send them to a report so I can see what it thinks has happened and still have a cube I can look at at the end.
I have been totally stuck with this for months and haven’t got any further.
August 31, 2012 at 10:40 am
Thanks loads for that
herladygeekedness (8/31/2012)
Not sure I can be much help, but "stuck for months" got to me.When I get a cube processing error, I usually can fix it by processing each dimension separately and then re-trying. Sounds like you have done that AND checked that your fact key does, in fact, match the dimension key. At least, it sounds like you have done that?
Yep I process each dimension successfully in Integration Services on FULL. It seems to go fine every time
I don't do MDX querying, I query the underly SQL dim table to see if that key is there. Sounds like you cannot access the dimension data ?
I have checked the underlying data in SQL and its totally fine. It the data in the cube that I cant check due to the unsuccessful process.
Process Full on the cube should process all dimensions,too. When you do that manually, all is well?
Thats it, if I do a manual process it works fine, Its just the IS Package where the cubes fail after processing the dimensions.
I do not use the AS components in SSIS, my SQL Agent cube does it for me:
<Batch xmlns="http://schemas.microsoft.com/analysisservices/2003/engine">
<Parallel>
<Process xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ddl2="http://schemas.microsoft.com/analysisservices/2003/engine/2" xmlns:ddl2_2="http://schemas.microsoft.com/analysisservices/2003/engine/2/2">
<Object>
<DatabaseID>Fake Cube</DatabaseID>
</Object>
<Type>ProcessFull</Type>
<WriteBackTableCreation>UseExisting</WriteBackTableCreation>
</Process>
</Parallel>
</Batch>
Hope I've at least given you a few ideas. Good luck!
Ooh this is the interesting bit. What do you mean by SQL Agent Cube and what is the script that you included? Do you process all your dimensions and cubes overnight in a seperate job just for Analysis Services?
If I could figure this bit out I might be somewhere to getting it sorted. Unfortunately I dont have access to setting up over night jobs so I need to make sure I know what Im taking about to give instructions to the dba team.
Thanks for your help 🙂
Debbie Edwards (8/31/2012)
The dimensions have processed Successfully prior to the updating of the SEN CubesThe attribute key cannot be found when processing: Table: 'fact_SEN_Workflow_Steps', Column: 'DW_Prov_ID', Value: '370194'. The attribute is 'DW Prov Child ID'.
Checking the Source data and this attribute key matches the dimension so it’s fine.
Can I check the dimension now that the cube has failed?
Analysis Services…. Dimensions….. Provisions
No it doesn’t allow you to check for an ID Can I do in in SMS using MDX?
Q. Can you do this in MDX SELECT * FROM dim.Service_Prov WHERE DW_Prov_Child_ID = 370194
You cant browse the cube in Alalysis Services or SMS ‘ Error Loading Metadata. No Cubes were found.’
If I run it in Analysis Services on Full it succeeds which means I can never actually test for this issue.
Once it Suceeds when manually processed in Analysis Services it works in IS. Then fails again during the overnight.
Ive put this into the forum before and didn’t get anywhere but I thought Id try again because surely it can’t be me having these issues.
Can I get it to ignore errors and send them to a report so I can see what it thinks has happened and still have a cube I can look at at the end.
I have been totally stuck with this for months and haven’t got any further.
August 31, 2012 at 11:09 am
happy to help! I'm not such an old pro at this myself so I know how frustrating it can be!
The script is the second step in my SQL Agent overnight job. The first step runs all the dimension ETLs and then Fact Table ETLS in one big SSIS "parent" package with tons of "kids".
If that is all successful, this next step should be configured as SQL Server Analysis Services Command. The user in the RunAs must have SSAS privileges (I'm no authority on the permissions but whoever sets it up for you will need to test it, and reprocessing a cube is not damaging, so do insist that they test it before telling you It's Set!). It should be obvious to them which server to enter, wherever the cube lives!
You said you process in Integration Services - not SSAS? I open AS instance and right-click cubes to manually do it - are you only using the SSIS components for it as "manual"? I have not used any SSIS components for SSAS operations so if they have tricks, sorry, I'm not going to know them. We also don't use manifests, so not helpful on that, either.
If they have not provided you credentials to log in to SSAS I guess there isn't much you can do on that, but if you CAN access it, the script I provided can be run in a query window there. Likely generating same error message.
Maybe you are processing it via IBIDS, in your AS project interface? Just trying to figure out if you are confined to SSIS components or if you can open the AS project? If you can open the AS project, you should definitely be able to browse dimensions that processed. Check your datasource view(s) also. Make sure to preview the data. I'm hoping that something will jump out at you. If yours is set for queries vs tables (ours are queries), run them, see if you can spot any nulls or odd values. Verify relationships, also. I doubt anything moved, but it will be worthwhile to check all pieces.
I have to ask, though the answer is implied, does your fact table look ok otherwise? No weirdo data or unexpected nulls? especially in that field you are getting an error in - could be you solve for the first id, and, oh crap, now it can't find the next! Only time I had that was when I made a boo boo and had built the facts off of wrong dims. Solved for one key, then, uh oh, another! I strongly feel that it's a data issue and maybe a change was made some time ago that seemed like it would have no impact...?
Can't tell you how many times I've been bitten by that assumption much later...
Debbie Edwards (8/31/2012)
Thanks loads for thatherladygeekedness (8/31/2012)
Not sure I can be much help, but "stuck for months" got to me.When I get a cube processing error, I usually can fix it by processing each dimension separately and then re-trying. Sounds like you have done that AND checked that your fact key does, in fact, match the dimension key. At least, it sounds like you have done that?
Yep I process each dimension successfully in Integration Services on FULL. It seems to go fine every time
I don't do MDX querying, I query the underly SQL dim table to see if that key is there. Sounds like you cannot access the dimension data ?
I have checked the underlying data in SQL and its totally fine. It the data in the cube that I cant check due to the unsuccessful process.
Process Full on the cube should process all dimensions,too. When you do that manually, all is well?
Thats it, if I do a manual process it works fine, Its just the IS Package where the cubes fail after processing the dimensions.
I do not use the AS components in SSIS, my SQL Agent cube does it for me:
<Batch xmlns="http://schemas.microsoft.com/analysisservices/2003/engine">
<Parallel>
<Process xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ddl2="http://schemas.microsoft.com/analysisservices/2003/engine/2" xmlns:ddl2_2="http://schemas.microsoft.com/analysisservices/2003/engine/2/2">
<Object>
<DatabaseID>Fake Cube</DatabaseID>
</Object>
<Type>ProcessFull</Type>
<WriteBackTableCreation>UseExisting</WriteBackTableCreation>
</Process>
</Parallel>
</Batch>
Hope I've at least given you a few ideas. Good luck!
Ooh this is the interesting bit. What do you mean by SQL Agent Cube and what is the script that you included? Do you process all your dimensions and cubes overnight in a seperate job just for Analysis Services?
If I could figure this bit out I might be somewhere to getting it sorted. Unfortunately I dont have access to setting up over night jobs so I need to make sure I know what Im taking about to give instructions to the dba team.
Thanks for your help 🙂
Debbie Edwards (8/31/2012)
The dimensions have processed Successfully prior to the updating of the SEN CubesThe attribute key cannot be found when processing: Table: 'fact_SEN_Workflow_Steps', Column: 'DW_Prov_ID', Value: '370194'. The attribute is 'DW Prov Child ID'.
Checking the Source data and this attribute key matches the dimension so it’s fine.
Can I check the dimension now that the cube has failed?
Analysis Services…. Dimensions….. Provisions
No it doesn’t allow you to check for an ID Can I do in in SMS using MDX?
Q. Can you do this in MDX SELECT * FROM dim.Service_Prov WHERE DW_Prov_Child_ID = 370194
You cant browse the cube in Alalysis Services or SMS ‘ Error Loading Metadata. No Cubes were found.’
If I run it in Analysis Services on Full it succeeds which means I can never actually test for this issue.
Once it Suceeds when manually processed in Analysis Services it works in IS. Then fails again during the overnight.
Ive put this into the forum before and didn’t get anywhere but I thought Id try again because surely it can’t be me having these issues.
Can I get it to ignore errors and send them to a report so I can see what it thinks has happened and still have a cube I can look at at the end.
I have been totally stuck with this for months and haven’t got any further.
August 31, 2012 at 11:10 am
oh, and it never hurts to ask for a reboot of the server!
August 31, 2012 at 8:29 pm
I may have found a way around the cube being offline - when you go to process, check the options for ignoring errors. It's maybe not the best thing to do, but it might get the cube back to where just seeing the thing can make the problem obvious.
September 3, 2012 at 4:25 am
right......
Trying very very hard to get my head round this but there are so many pieces to it, it gets very complicated.
herladygeekedness (8/31/2012)
The script is the second step in my SQL Agent overnight job. The first step runs all the dimension ETLs and then Fact Table ETLS in one big SSIS "parent" package with tons of "kids".
So the script is the one you added above? How is this created?
The first step I believe Is the same as I do. I use IS to grab all the source data and add to my warehouse (relational Star Schemas etc so isnt in the Analysis Services as a cube yet.
If that is all successful, this next step should be configured as SQL Server Analysis Services Command. The user in the RunAs must have SSAS privileges (I'm no authority on the permissions but whoever sets it up for you will need to test it, and reprocessing a cube is not damaging, so do insist that they test it before telling you It's Set!). It should be obvious to them which server to enter, wherever the cube lives!
You said you process in Integration Services - not SSAS? I open AS instance and right-click cubes to manually do it - are you only using the SSIS components for it as "manual"? I have not used any SSIS components for SSAS operations so if they have tricks, sorry, I'm not going to know them. We also don't use manifests, so not helpful on that, either.
If they have not provided you credentials to log in to SSAS I guess there isn't much you can do on that, but if you CAN access it, the script I provided can be run in a query window there. Likely generating same error message.
Trying to get my head round this bit. Is it this..... Integration services runs all the source data into the destination relational tables. (Star Schemas)
The next step in the package is not an Analysis Services step at all but a SQL Server Analysis Services step. This is where it gets fuzzy. I rely on the DBA team setting up the job for me. I dont have access to it. Any they arent used to setting up Analysis Services jobs at all so I could really use a guide on this. And I cant find anything on the internet at all. Do you know of any decent guides on how to do this...
Also so in this Analysis Services Step do you process your dimensions and then Cubes to Refresh Analysis Services?
Maybe you are processing it via IBIDS, in your AS project interface? Just trying to figure out if you are confined to SSIS components or if you can open the AS project? If you can open the AS project, you should definitely be able to browse dimensions that processed. Check your datasource view(s) also. Make sure to preview the data. I'm hoping that something will jump out at you. If yours is set for queries vs tables (ours are queries), run them, see if you can spot any nulls or odd values. Verify relationships, also. I doubt anything moved, but it will be worthwhile to check all pieces.
I dont know what IBIDS is? Yep I can open the Analysis Services project, I created it. It is always sucessful If I manually run in Analysis Services on Full. But I dont want to only be able to do it manually. It just doesnt make sense since its supposed to run overnight.
When the cubes fail in IS I always check the errors and the data in SQL is always 100% correct.
I have to ask, though the answer is implied, does your fact table look ok otherwise? No weirdo data or unexpected nulls? especially in that field you are getting an error in - could be you solve for the first id, and, oh crap, now it can't find the next! Only time I had that was when I made a boo boo and had built the facts off of wrong dims. Solved for one key, then, uh oh, another! I strongly feel that it's a data issue and maybe a change was made some time ago that seemed like it would have no impact...?
Can't tell you how many times I've been bitten by that assumption much later...
When I have checked its always fine. I have a process that gets rid of NULLs if anything does get through. Im going to have another go now though............
The attribute key cannot be found when processing:
Table: 'fact_SEN_Fact',
Column: 'DW_Prov_ID',
Value: '370279'.
The second error message tells me that in the fact table its record 230241 that doesnt have the corresponding attribute key
THE DW_Prov_Id for this row is 370279 with the person ID of 95201
Going into Analysis Services to use the data source view script in the Provision dimension
(It always seems to be the provision dimension....)
Yep there is a DW_Prov_Id of 370279 With the person ID of 95201 So this shouldnt be showing as an error
So still lost really......
And If I did it manually in Analysis Services on full it would work fine.....
Debbie Edwards (8/31/2012)
Thanks loads for thatherladygeekedness (8/31/2012)
Not sure I can be much help, but "stuck for months" got to me.When I get a cube processing error, I usually can fix it by processing each dimension separately and then re-trying. Sounds like you have done that AND checked that your fact key does, in fact, match the dimension key. At least, it sounds like you have done that?
Yep I process each dimension successfully in Integration Services on FULL. It seems to go fine every time
I don't do MDX querying, I query the underly SQL dim table to see if that key is there. Sounds like you cannot access the dimension data ?
I have checked the underlying data in SQL and its totally fine. It the data in the cube that I cant check due to the unsuccessful process.
Process Full on the cube should process all dimensions,too. When you do that manually, all is well?
Thats it, if I do a manual process it works fine, Its just the IS Package where the cubes fail after processing the dimensions.
I do not use the AS components in SSIS, my SQL Agent cube does it for me:
<Batch xmlns="http://schemas.microsoft.com/analysisservices/2003/engine">
<Parallel>
<Process xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ddl2="http://schemas.microsoft.com/analysisservices/2003/engine/2" xmlns:ddl2_2="http://schemas.microsoft.com/analysisservices/2003/engine/2/2">
<Object>
<DatabaseID>Fake Cube</DatabaseID>
</Object>
<Type>ProcessFull</Type>
<WriteBackTableCreation>UseExisting</WriteBackTableCreation>
</Process>
</Parallel>
</Batch>
Hope I've at least given you a few ideas. Good luck!
Ooh this is the interesting bit. What do you mean by SQL Agent Cube and what is the script that you included? Do you process all your dimensions and cubes overnight in a seperate job just for Analysis Services?
If I could figure this bit out I might be somewhere to getting it sorted. Unfortunately I dont have access to setting up over night jobs so I need to make sure I know what Im taking about to give instructions to the dba team.
Thanks for your help 🙂
Debbie Edwards (8/31/2012)
The dimensions have processed Successfully prior to the updating of the SEN CubesThe attribute key cannot be found when processing: Table: 'fact_SEN_Workflow_Steps', Column: 'DW_Prov_ID', Value: '370194'. The attribute is 'DW Prov Child ID'.
Checking the Source data and this attribute key matches the dimension so it’s fine.
Can I check the dimension now that the cube has failed?
Analysis Services…. Dimensions….. Provisions
No it doesn’t allow you to check for an ID Can I do in in SMS using MDX?
Q. Can you do this in MDX SELECT * FROM dim.Service_Prov WHERE DW_Prov_Child_ID = 370194
You cant browse the cube in Alalysis Services or SMS ‘ Error Loading Metadata. No Cubes were found.’
If I run it in Analysis Services on Full it succeeds which means I can never actually test for this issue.
Once it Suceeds when manually processed in Analysis Services it works in IS. Then fails again during the overnight.
Ive put this into the forum before and didn’t get anywhere but I thought Id try again because surely it can’t be me having these issues.
Can I get it to ignore errors and send them to a report so I can see what it thinks has happened and still have a cube I can look at at the end.
I have been totally stuck with this for months and haven’t got any further.
[/quote]
September 3, 2012 at 4:26 am
herladygeekedness (8/31/2012)
oh, and it never hurts to ask for a reboot of the server!
Yep and Ive asked for this already a fair few times....
September 3, 2012 at 4:29 am
herladygeekedness (8/31/2012)
I may have found a way around the cube being offline - when you go to process, check the options for ignoring errors. It's maybe not the best thing to do, but it might get the cube back to where just seeing the thing can make the problem obvious.
Is this in Integration Services on the Analysis Services task on in Analysis Services task itsself?
A long while again I was trying to figure out if I could do this and send the errors to a file to be looked at later.... but again the errors its picking out arent actually errors, the data is always fine.
And I could find any decent help files on this at all.
September 6, 2012 at 8:57 am
Well, Debbie, I must have had some weird premonitiion as I now have the exact same problem. Oh boy!
Sounds like we do things in a similar fashion. IBIDS = Vis Studio where you create SSIS packages. probably you hadn't heard it by this moniker. All data loads via ssis pkg, from prod > dw.
Where we differ is in using SSIS Analysis Services task in a package. The piece of Analysis Services Command I included earlier is what processes my cube in the SQL Job after dims and facts are popped. Just put in the name of yours. DBA just has to select the step type as Analysis Services Command, paste in with your cube name in it vs whatever I left in there, it should be no big whoop for them. What they do for your SSIS pkgs is select Integration Services Package step in the SQL job. Don't present it to them as creating an analysis services job and they should be okie dokie with it. Only potential fly in that ointment is Permissions. Job should fail on that step if not appropriate access. Perms are far from my forte, especially when it gets into job agents and proxies and so forth ... presumably the dbas can handle it.
I have been given a deadline of tomorrow night to get this resolved. Scares me that you've had the issues for months!!!
I figure if it comes to desperate measures, I'll clone the bugger with a different name and see if it's just some werido corruption, as I do not at all have a feel for cube corruption and wonder if I found it? What caused it is just a big fog to me. "One day, it just quit working ..."
I was talking about from VS project/IBIDS/SSIS Package creation on processing cube with error suppression. Noodle with the different options. if you suppress those error messages, you may find, as I did., that the first error is a red herring - after it tells you that key is crap, it goes on to identify the next key name as crap, on and on. This is why I fear corruption.
Where we differ is that I cannot get mine to process anywhere anyhow without ignoring errors. When I steal the queries out of the processing progress window, they execute perfoectly on my cube server so it is not true that the keys cannot be found, as you have also confirmed.
I'll post back if I find an answer or anything new to try. Especially if my cloning experiment works as it may not solve the problem, but it gets a cube back online, and that's my goal. I only hope that we can both learn from the post-mortem.
September 6, 2012 at 9:08 am
Oh no! 🙁
This has been my least favourite issue this year. Ive still not got my issue resolved at all.
Thanks for the extra advice. Ill get myself a block of time to have another go at it tomorrow.
Id been thinking If I could ignore all errors and send them to a text file I could get a better idea of what was going on but I have no idea how to do that. It only seems to be one dimension that is causing the problem.
I wonder how much this affects people?
Im guessing if you run it manually in Analysis Services it processes fine, just like me (Making it so much more frustrating)
Debbie
September 6, 2012 at 4:05 pm
Debbie Edwards (9/6/2012)
Oh no! 🙁This has been my least favourite issue this year. Ive still not got my issue resolved at all.
Thanks for the extra advice. Ill get myself a block of time to have another go at it tomorrow.
Id been thinking If I could ignore all errors and send them to a text file I could get a better idea of what was going on but I have no idea how to do that. It only seems to be one dimension that is causing the problem.
I wonder how much this affects people?
Im guessing if you run it manually in Analysis Services it processes fine, just like me (Making it so much more frustrating)
Debbie
Sadly, mine fails no matter where I process it! I can tell you how to suppress the messages - you have the basic Process window, where you say Process Full or whatever .. there is a button at the bottom Change Settings ... Go to Dimension Key Errors tab. I haven't logged the errors as when I said Report and Continue, that's when I saw key after key after key supposedly INVALID. I could deal with one flawed dimension or a handful of keys but EVERY DIMENSION, most every key? Not buying it!!!
Be sure you have disk space for logging the errors. I hope I'm just teasing but no clue how big your recordsets are.
It's been one thing after another today and still a couple Hot Projects in front of this one but getting closer to trying the cloning experiment. YIKES, only 12 more hours!!!
S'ok, boss has been disappointed before. Don't like disappointing him, but, troubleshooting is a process. I came up thru IT, he came up thru business. Sometimes, he doesn't understand my world. I have not mentioned the word corruption but it is my gut feel.
I intend to look on the bright side - once we can figure out how to get our cubes back, we'll know that helpful lifesaving technique!!! I am certain that something like this will happen again and for me, the next one will most certainly be an even more important cube. altho this one concerns Effectiveness and with a big ole partners meeting going on, I'm sure they are talking about Effectiveness.
So, here I go off on some wild rampage that I hope will be Effective!
Be very sure that I will share my results with you.
And I wondered - you wouldn't happen to have ever used a Blackbaud product? I'm sure there are at least 2 Debbie Edwards in the world, but the cube tie narrows the field. I may have talked to you by phone some years ago.
September 10, 2012 at 7:19 am
Ive got the same issue with the managers over here. They have no clue how a show stopper like this can change things.
Ive had a fail on a dimension over the weekend and Im struggling even more now.
BTW Ive gone to Process full and change settings. Ive gone to the Dimensions key errors tab and set everything up as below (Ive added the screen shot)
I tried runing it but got the error saying that the log file couldnt be found. Well.... yes I hadnt created it.
So I tried creating it and running again after creating the attendance log file......
And then got this error
File system error: The following error occurred while opening the file 'H:\VSP\Data Warehouse\2008 Reports\Reports_Execution_Auditing\attendance.log': The system cannot find the path specified. .
But Ive created it so it should be OK....
Tried again and got the same thing.... Ive had this and given up on this before...
So basically things are getting a whole log worse. Have you managed to get your working well again?
You hadnt actually said how you had set yours to log so i was just hoping for the best.
BTW do youmean Blackboard? It rings a bell but Im not too sure.....
Sigh...another week ahead for me of getting no where.:(
September 10, 2012 at 12:51 pm
Nope, still stuck. Boss is looking at me like I am the biggest idiot but after pulling a double shift Thurs tryign everything I could find, I am also still very much in the weeds.
Sadly, we do no logging here (boss comes from biz side, not usually into my spending time on things that just may help when I'm the weeds like this).
I am planning to rebuild the cube. Everythign found online is it's-your-data-it's-your-data-it's-your-data and I cannot find how it;s my data, and one guy out there has had teh same Not My Data problem and rebuilds the cube every time this happens.
Wish I'd found the answer to share with you, but , well, Not Yet.
~~~~
Definitely meant Blackbaud as I had a phone call regarding their BI tool, InfoEdge, years ago and thought, hey, maybe... No matter. more than one Debbie Edwards!
September 11, 2012 at 7:12 am
Sounds like you are having the same kind of week as me. The good news is I have managed to fix the dimension that was causing problems. I had some bad data coming through but thats seperate to the main issue.
The good news is Ive managed to sep up .log files with help from the dba team to log issues coming through......
This might help see whats going on in the overnight run. Although....
Should I be OK doing it from the Integration Services Project?
the script that you had in your post.... What exactly does that do? Does that process the dimensions and the cubes in the same way as me adding Analysis Services Integration Services package does? Im still confused about this side of things and a few people have in the past sent me that code.
Viewing 15 posts - 1 through 15 (of 21 total)
You must be logged in to reply to this topic. Login to reply