Error while creating new module

When I create a new module, there is the next error in the log file:

There is no newmod.ini file in Opentext\staging\newmod\

Find more posts tagged with

Comments

Hi Eugene,

Don't worry about it.

The New Module wizard uses the '0 DumpModuleConfigToFile' script to *create* the ini file in staging. The first thing that script does is delete any existing ini file. But it doesn't exist because we're creating a new module.

The INFO messages after the the error show it generating the file.

Over the next few releases, CSIDE will stop relying on the DumpModuleConfigToFile script file and instead generate the file from its own template in the source tree. We'll also be using the module ini file to tell CSIDE what ospaces and support folders it needs to care about.

Darcy.

Eugene_Ochkurov

Hi,

this issue still not resolved, i still can not create more than one module in project. When i create new module from wizard i still recive error in log:

13:55:51,207 ERROR KFile::Delete() - C:\OPENTEXT\staging\sstest2\sstest.ini error: The system cannot find the path specified.
13:55:51,207 ERROR KFile::Open() - apr_file_open() error The system cannot find the path specified. file: C:\OPENTEXT\staging\sstest2\sstest.ini
13:55:51,207 ERROR fileprefs_create: failed to create C:\OPENTEXT\staging\sstest2\sstest.ini
13:55:51,207 ERROR KFilePrefs::CreateKFilePrefs - failed to create prefs file: C:\OPENTEXT\staging\sstest2\sstest.ini (-1)

0 DumpModuleConfigToFile script also doens't work and generate the same log!

We use 10.5.3.139 plugin version

Darcy_Casselman

Hi Eugene,

Content Server doesn't seem to like numbers in module names. I can't tell for certain if this is a bug or by design. I'm sure at least part of it this is a bug. You might want to get in touch with Support.

Darcy.

Eugene_Ochkurov

Thanks Darcy!

I have one more question. I have closed my project in Eclipse, how can i open it again so that it appears on the Oscript Explorer tab?

Upd: I found how to open project, but when i start server i recive an eror:

FAMELIARISA

Greetings.

I want to add that we get the same error:

16:54:42,208 ERROR KFile::Delete() - C:\OPENTEXT105\staging\testmodule_1_0_0\testmodule.ini error: The system cannot find the file specified.
16:54:42,261 INFO dependencies
16:54:42,261 INFO     requires_1={'kernel',10,15}
16:54:42,261 INFO description
16:54:42,261 INFO     moduleName=testmodule
16:54:42,261 INFO     Name=testmodule
16:54:42,261 INFO     Version=1.0 r 0
16:54:42,261 INFO install
16:54:42,261 INFO     Url=func=testmodule.configure&module=testmodule&nextUrl=%1
16:54:42,262 INFO OSpaces
16:54:42,262 INFO     ospace_1=testmodule

As you can see the .ini file is not created. If one creates an .ini file by hand and then proceeds to add it in the source folder, then, the build module command succeeds and there is a proper .ini file (with proper ini file sections e.g. [dependencies] and whatnot).

This bug did not exist in previous versions (atm using com.opentext.cside_10.5.4.235 jar). Please notify support - this is a serious hindrance and can cause lots of errors.

Also, when this is fixed, make sure that the required kernel version is {10,0} and not {10,15} (obviously something goes horribly wrong there).

Craig Cole

Quoted Darcy Casselman on 04/05/2016 09:47 AM:

This is total true. It doesn't say it in the manuals, but if you have a module name say "test123" and create folder called "test123_1_0_0", the ODumpModuleConfigToFile script will fail when you run it. If you debug far enough, you find a function called SplitOffVersionNumber which does does not work correctly. It's supposed to return "test123" when it is given the folder name, but instead returns "test". Things go wrong and ODumpModuleConfigToFile ultimately doesn't write anything.