865
Views
18
Comments
Solved
Ghost Dependencies
Question

HI,


I published a solution with an unused dependency, Offline Apps. So I removed this reference and deleted the application. Now when I try publish I have a error due a broken references but if refresh the dependencies I can publish with a warning due a missing Module. 

Anything I can do to fix it?

Thanks for any help.

2020-02-28 09-46-54
Eduardo Jauch
Solution

Hello Ana,

I already have a somewhat similar problem once.

Please, first, if you don't have yet, try to install the latest version of Service Studio. Sometimes there is a fix that could help solve the problem and very recently they launched a new version of the Service Studio.

Than, install again the Offline application from forge. You will have to force the install if your Server is version 10.
Go to your module and reference everything from the Offline (don't use anything).

Publish it.

Than remove the references and publish it again.

It seems that your module thinks that there are still a module Offline that is a producer and that is broken, but as you don't use anything, after refresh it allows you to publish it anyway.

Than, tell us if it worked :)

Cheers,
Eduardo

2022-11-12 11-28-30
Gonçalo Martins
Staff

Hi Ana.

You may have an indirect broken dependencie on your end.

Try to open all the consumers of the element you need to refresh or take a look at Service Center to check if you're getting any error that could help you with some eSpace mentioned on the full error stack.

Cheers,

GM

2017-04-20 10-16-33
Sofia Santos

Gonçalo Martins wrote:

Hi Ana.

You may have an indirect broken dependencie on your end.

Try to open all the consumers of the element you need to refresh or take a look at Service Center to check if you're getting any error that could help you with some eSpace mentioned on the full error stack.

Cheers,

GM

I reinstalled "Offline Apps" and this application only has a consumer, the Offline_Sample.

Offline_Consumers.png
2022-11-12 11-28-30
Gonçalo Martins
Staff

Hi Ana.

Can you show me the error you're getting and where/when are you getting it?


2017-04-20 10-16-33
Sofia Santos

The error happens when I publish the module.
     When I open dependencies don't exist offline module, make sense because this app was deleted of environment, after update the dependencies I can publish with a warning of missing references.

Offline_Dependencies.png
2014-10-08 20-03-52
Luciano Schiavo

You can click on refresh all and some old dependencies will disappear. If the old reference still appear on your screen you can delete it using the trash can icon that will appear.

2022-11-12 11-28-30
Gonçalo Martins
Staff

Hi Ana.

Did you try to manually remove the references mentioned?

2017-04-20 10-16-33
Sofia Santos

Hi Gonçalo,


I haven't references to offline to remove...

2017-04-20 10-16-33
Sofia Santos

Ana Sofia Santos wrote:

Hi Gonçalo,


I haven't references to offline to remove...

I don't have dependencies to refresh.


2022-11-12 11-28-30
Gonçalo Martins
Staff

If you want you can send me in a PM the eSpaces to take a look because the issue is very strange. Otherwise, I can't really see another way to help you.

2018-11-06 14-26-44
Suraj Borade

Hi Ana,

Did you try approach as suggested by Luciano?

when you go to refresh all dependencies and though don't see "Refresh All" option active, just click on Ok and it will give you broken references which you need to fix?

Thanks and Regards,

Suraj Borade

2019-07-08 11-04-35
Leonardo Fernandes
 
MVP

Hi Ana. Did you try using the menu Module -> Remove Unused Elements, and then publishing again?

2017-04-20 10-16-33
Sofia Santos

Leonardo Fernandes wrote:

Hi Ana. Did you try using the menu Module -> Remove Unused Elements, and then publishing again?

Hi Leonardo,
Yes, I did, but I still have an error while publishing eSpace.


2018-11-06 14-26-44
Suraj Borade

Ana,

Can you please share sample espace?

2017-04-20 10-16-33
Sofia Santos

Suraj Borade wrote:

Ana,

Can you please share sample espace?

Hi Suraj,

I can't. 


2014-10-08 20-03-52
Luciano Schiavo

It seems you are using some client actions (based on the error I saw in your picture). If this is the case, you could disable them in the system reference and replace for someone of the server side.

In the Truechange appears some error ?  Can you show to us ?

2020-02-28 09-46-54
Eduardo Jauch
Solution

Hello Ana,

I already have a somewhat similar problem once.

Please, first, if you don't have yet, try to install the latest version of Service Studio. Sometimes there is a fix that could help solve the problem and very recently they launched a new version of the Service Studio.

Than, install again the Offline application from forge. You will have to force the install if your Server is version 10.
Go to your module and reference everything from the Offline (don't use anything).

Publish it.

Than remove the references and publish it again.

It seems that your module thinks that there are still a module Offline that is a producer and that is broken, but as you don't use anything, after refresh it allows you to publish it anyway.

Than, tell us if it worked :)

Cheers,
Eduardo

UserImage.jpg
Pedro Menezes

Hello sorry to wake this old post. But I think it brings some further insight on this problem. I currently using Development Environment 10.0.911.0 released on 2018-12-28 and the ghost dependencies still happens.

 So that means that so far updating the service studio won't solve the problem entirely at least up to that version 10.0.911.0.

The ghost dependency for example a WebBlock that  is not used but service studio thinks it's using and needed, but not when I choose "Find Usages". But when I use Service Studio "Remove Unused dependencies" it gives error and I can't publish the eSpace.

The way I solved the problem is kind of tedious but it worked. Service Studio thinks the element in this case a webBlock exists so when I double click the error at least it says the screen that he thinks the Web Block exists and being used. Than I narrow it down to the element that contains the ghost dependcy on that screen deleting and undeleting to see where it is. Than when I find that element I make a new element equal to the corrupted element that has the ghost element and delete the corrupted element. Then the error is gone and I can publish the eSpace.

2018-10-09 22-15-12
Barnaby Ling

Old post I know, however, I had a similar issue within Service Studio 11.0.420.0 - where I'd removed from all components, deleted from the development environment and it kept giving the same warning. The fix was to "Remove Unwanted Dependencies" from within server studio, whilst removed many others it did remove this warning.

Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.