BookmarkSubscribeRSS Feed
turcay
Lapis Lazuli | Level 10

Hello everybody,

 

I was able to open Job Editor screen, when I double click to DI Studio Job but suddenly, I am not able to open Job Editor screen in DI Studio.

 

I checked for the following note-> https://support.sas.com/kb/41/571.html  and it seems that the file is JavaArgs_1=-Xmx1024m and JavaArgs_13=-XX:MaxPermSize=128m

 

I also went to SAS Management Console Metadata Manager - Active Server - Foundataion - Analyze/Repair Metadata and it seems that it verified Metadata Files.

 

@joeFurbee @LinusH @AllanBowe @JohnJPS @Bipasha @Patrick 

 

Thanks

11 REPLIES 11
turcay
Lapis Lazuli | Level 10

I also applied following note too -> http://support.sas.com/kb/56/034.html

Patrick
Opal | Level 21

I was able to open Job Editor screen, when I double click to DI Studio Job but suddenly, I am not able to open Job Editor screen in DI Studio.

 

I checked for the following note-> https://support.sas.com/kb/41/571.html  and it seems that the file is JavaArgs_1=-Xmx1024m and JavaArgs_13=-XX:MaxPermSize=128m

 

I also went to SAS Management Console Metadata Manager - Active Server - Foundataion - Analyze/Repair Metadata and it seems that it verified Metadata Files.

 


 

You need to provide the exact SAS and especially the exact DIS version.

The issues you encounter could be caused by SAS/DIS version conflicts as your other question indicates. This is the bit you need to resolve first.

https://communities.sas.com/t5/SAS-Data-Management/How-to-Create-and-Configure-an-Amazon-S3-Download... 

 

If it's not a version conflict then...

"...but suddenly, I am not able to open Job Editor screen in DI Studio."

What happens exactly? Just a spinning wheel which never ends or something else?

 

Can other users open the DIS job? This would tell you quickly if it's more likely a metadata or a DIS client problem.

I remember having had such issues years ago in a project and changing the settings as per the SAS notes you've posted fixed it.

 

Is it only a specific job or does this apply for all jobs?

 

Does the issue persist even after restarting DIS - or eventually even after restarting your computer?

turcay
Lapis Lazuli | Level 10

Hello,

 

It is -> Current version: 9.04.01M5P091317 so you mean that if I first resolve other issue, I can fix this problem too?

Actually, this one seems that independent from other subject because I could open Job Editor before, and never happened, it just does not let me to see Job Editor screen aynmore, my jobs are located there but I cannot display them. Just a spinning wheel for a second, then nothing happens. It is for all jobs and for every people.It started to appear for everybody on thursday.

 

Thanks

Patrick
Opal | Level 21

Referring to the other discussion:

Did somehow "someone" change the DIS version? So now with DIS4.8 you can't open the jobs anymore which have been created with DIS4.9?

turcay
Lapis Lazuli | Level 10

I do not think so because this week, I tried to import that file before that, I have my other own jobs and those were working. I think your suggestions will be following these notes->

https://support.sas.com/kb/41/571.html

http://support.sas.com/kb/56/034.html

 

This should fix the problem, right? Any idea?

Patrick
Opal | Level 21

The log you've posted clearly tells you that you've got a mix-up with DIS versions. This will likely cause issues as forward compatibility (opening DIS4.9 created jobs with DIS4.8) is not something you can expect to work properly (like DIS4.9 writing metadata which isn't readable by DIS4.8).

 

WARNING: The custom transform 'Download File From Amazon S3' found at configured location '/System/Applications/SAS Data Integration Studio/DI Studio Common Data/Generated Transformations' is not a recognised standard transform for DI Studio 4.8. Exported projects which utilise this transform will not be compatible with standard installations.

turcay
Lapis Lazuli | Level 10

But I received that file from another environment and in that environment DI Studio was probably 4.8 but here it is 4.9 and this is the reason I receive that error, I am okay with that

but why I cannot open Job Editor screen which I could open before and I know that there is no upgrade and or renewal or etc. Except from the importation process why I cannot open my current jobs?

 

Thanks

Patrick
Opal | Level 21

@turcay wrote:

But I received that file from another environment and in that environment DI Studio was probably 4.8 but here it is 4.9 and this is the reason I receive that error, I am okay with that

but why I cannot open Job Editor screen which I could open before and I know that there is no upgrade and or renewal or etc. Except from the importation process why I cannot open my current jobs?

 

Thanks


It's the other way round! You're importing a .spk created under DIS4.9 with a DIS4.8 version. ....and the log tells you that this isn't a good thing to do.

turcay
Lapis Lazuli | Level 10

I agrree with this but how can I fix those warnings then?

Patrick
Opal | Level 21

@turcay wrote:

I do not think so because this week, I tried to import that file before that, I have my other own jobs and those were working. I think your suggestions will be following these notes->

https://support.sas.com/kb/41/571.html

http://support.sas.com/kb/56/034.html

 

This should fix the problem, right? Any idea?


You can try. Only the 2nd one though as the other one is for an earlier SAS version.

But: If restarting DIS then things should in the beginning also work without the fix.

turcay
Lapis Lazuli | Level 10

Okay, I will try it, thanks

SAS Innovate 2025: Save the Date

 SAS Innovate 2025 is scheduled for May 6-9 in Orlando, FL. Sign up to be first to learn about the agenda and registration!

Save the date!

How to connect to databases in SAS Viya

Need to connect to databases in SAS Viya? SAS’ David Ghan shows you two methods – via SAS/ACCESS LIBNAME and SAS Data Connector SASLIBS – in this video.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 11 replies
  • 2367 views
  • 0 likes
  • 2 in conversation