Skip to main content
Solved

IFS Cloud 22R2 - Developer Studio - No project is visible when opening DS

  • February 27, 2023
  • 2 replies
  • 278 views

Forum|alt.badge.img+9
  • Sidekick (Partner)
  • 86 replies

Developer Studio version Details:

Product Version: IFS Developer Studio 23.1E.9313 (Build 2023-01-27 01:51)
Java: 14.0.2; OpenJDK 64-Bit Client VM 14.0.2+12
Runtime: OpenJDK Runtime Environment 14.0.2+12
System: Windows 10 version 10.0 running on amd64; UTF-8; en_US (developer_studio)

When I open Developer Studio, I cannot see the Project I created. I can see following exception.
Even if I open the project, it does not open.
Any hint on how to solve this issue?

Exception:
java.nio.file.FileSystemException: C:\Users\Myuser1\OneDrive - AAA\AAA\Projects\DEV_PROJ\Core\crp\server: The tag present in the reparse point buffer is invalid
    at java.base/sun.nio.fs.WindowsException.translateToIOException(WindowsException.java:92)
    at java.base/sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:103)
    at java.base/sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:108)
    at java.base/sun.nio.fs.WindowsFileAttributeViews$Basic.readAttributes(WindowsFileAttributeViews.java:53)
    at java.base/sun.nio.fs.WindowsFileAttributeViews$Basic.readAttributes(WindowsFileAttributeViews.java:38)
    at java.base/sun.nio.fs.WindowsFileSystemProvider.readAttributes(WindowsFileSystemProvider.java:198)
    at java.base/java.nio.file.Files.readAttributes(Files.java:1843)
    at java.base/java.nio.file.FileTreeWalker.getAttributes(FileTreeWalker.java:219)
    at java.base/java.nio.file.FileTreeWalker.visit(FileTreeWalker.java:276)
    at java.base/java.nio.file.FileTreeWalker.next(FileTreeWalker.java:373)
    at java.base/java.nio.file.FileTreeIterator.fetchNextIfNeeded(FileTreeIterator.java:94)
Caused: java.io.UncheckedIOException
    at java.base/java.nio.file.FileTreeIterator.fetchNextIfNeeded(FileTreeIterator.java:87)
    at java.base/java.nio.file.FileTreeIterator.hasNext(FileTreeIterator.java:103)
    at java.base/java.util.Spliterators$IteratorSpliterator.trySplit(Spliterators.java:1784)
    at java.base/java.util.stream.AbstractShortCircuitTask.compute(AbstractShortCircuitTask.java:114)
    at java.base/java.util.concurrent.CountedCompleter.exec(CountedCompleter.java:746)
    at java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:290)
    at java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1016)
    at java.base/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1665)
    at java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1598)
[catch] at java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:183)
 

Best answer by GaSoGB

UPDATE:

Hi @InfFilipV ,
Thanks for the reply. 
After doing some experiments, it looks like this is a limitation in windows file extraction.
In my case, I created the project location in Onedrive folder.
Core folder path was ‘C:\Users\Myuser1\OneDrive - AAA\AAA\Projects\DEV_PROJ\Core’.


Note: I have replaced actual folder names with ‘AAA’.


Basically , the path was bit longer to ‘Core’ folder.
What happened was that when creating the project by extracting ‘Core’ solution repository, it cannot properly extract some files into some components. 
Strange thing is, if you manually try to click on the folder location where the DS points the error, it gives the same error and I cannot even open the folder.

As a workaround, I created my project in C drive and it now has a shorter folder path to ‘Core’ folder and this solved my issue.

View original
Did this topic help you find an answer to your question?

2 replies

InfFilipV
Hero (Partner)
Forum|alt.badge.img+12
  • Hero (Partner)
  • 212 replies
  • March 1, 2023

Hi,
here is “General” solution, what could help.
At least, try it as first option.

DEVELOPER STUDIO TIP :Common solution to (most) DevStudio hard errors | IFS Community

BR


Forum|alt.badge.img+9
  • Author
  • Sidekick (Partner)
  • 86 replies
  • Answer
  • March 1, 2023

UPDATE:

Hi @InfFilipV ,
Thanks for the reply. 
After doing some experiments, it looks like this is a limitation in windows file extraction.
In my case, I created the project location in Onedrive folder.
Core folder path was ‘C:\Users\Myuser1\OneDrive - AAA\AAA\Projects\DEV_PROJ\Core’.


Note: I have replaced actual folder names with ‘AAA’.


Basically , the path was bit longer to ‘Core’ folder.
What happened was that when creating the project by extracting ‘Core’ solution repository, it cannot properly extract some files into some components. 
Strange thing is, if you manually try to click on the folder location where the DS points the error, it gives the same error and I cannot even open the folder.

As a workaround, I created my project in C drive and it now has a shorter folder path to ‘Core’ folder and this solved my issue.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings