Usual cases are that the user trying to publish has no Write access to the destination.
I ran into this myself and well... I am admin... So the real cause in this case was that there already was a folder with exactly the same name. There obviously is no feedback from the system about this, so it is all about finding that out yourself!
4 comments:
Hi,
I face the same issue and am really puzzled why it is happening. I am a Admin and I don't change anything in folder structure. Now when I publish the model, I see this BMT-MDC-0001 Unable to publish error mesage, the package is visible but not aavailble (no way to open it in the Report Studio or QS).
If you have time, could you please, put here what steps exactly did you take to resolve the issue? I'd really appreciate your help.
Thanks a lot in advance
Yuri
Yuri, the issue I encountered at that occasion what caused by a folder (not package) that had exactly the same name as I tried to use for my newly published package. Have you tried using another name? I sense that that is also the reason why it is 'visible' but you don't get to see it while opening via RS or QS. You see a folder.
The package could not be created because it is the same name.
Either choose a new name for your package or rename the folder.
Hi, Mindaugas. Thanks a lot for your promt reply.
You mean that in your case the package and the folder both have the same name, right? Say, a folder called Test1 and then you are trying to publish there a package called Test1? So you just renamed a package to Test 2 and you problem was solved.
In my case the names are different. I have a folder called Packages and publish there packages with names such as Sales, Promo and so on. And I face the same issue for one of the packages, say, Sales.
I am thinking about 3 possible reasons beihind the issue:
1. Package is Last Publish Location is somehow corrupted and the new packages inherits these flaws from it.
2. I use exisiting model in non-DRM mode but create another model on the same datasource on DRM mode. There might be conflict.
3. Login under different login name (not own). We have 2 namespaces in Cognos and one of the logins is not mine. I have heard that this might be the cause as well as it is reccommended to close browsers when you are working with Framework manager. Probably, when I tried to publish the package with opened browsers smth had happened to already published package in Last Publsih location.
As workaround I had to use previous version of the model (with different Last Publish Location) and these packages have been set up ok.
As I said it is all really puzzling)). I am trying to investigate the issue.
Thanks again for your attention to the problem.
Cheers,
Yuri
It is a shame that same error message appears for multiple reasons...
I guess you will have to tackle and test variois scenarios to pin your specific issue.
I have changed between DQM and non DQM modes and that never caused issues. I guess that is what you mean in your point no 2, so I would say it is unlikely cause.
As for no 1- my gut feeling says that it is unlikely, but it is just a gut feeling...
No3 you could test with a new model. Just create one from scratch with a static view (no db connections) and try to publish that. Add components one by one till you hit your error message.
Post back here if you come across more clues, maybe we'll crack this somehow :)
Post a Comment