Jump to content
nazmouse

Plastic Server 6 service doesn't start

Recommended Posts

Hello everyone,

I have a problem starting plastic server 6 service, it happened to me before but I thought it's an issue with my OS so I decided to reinstall it, that helped me for a few weeks but now I face the problem again,

I tried doing the steps from another topic I found by googling :

 

apparently it didn't help me at all,

now speaking of a problem :

I can't start the plastic service at all, it just throws me a 1067 error (here's a pic demonstrating the issue, service.msc had been launched with admin privileges)

5a39b01f933a9_1(7).thumb.png.9c57eca080f88fc1b56f8a77bcff7b38.png

 

then I decided to start following steps from the topic I pinned higher and launch thingy using the console, again, it'd been run as admin using the --server argument, didn't help at all, it just said I have to run that as a service, at this point I'm stuck in a loop5a39b0cc090d5_1(6).thumb.png.b8fef629ac76b90e3db59f506d2cd7d4.png

 

Thanks!

Share this post


Link to post
Share on other sites

Hi @nazmouse,

If you want to start the Plastic SCM server using the command line you will need to open an administrator window and execute:

plasticd.exe --console

or

plasticd.exe --tray

Can you please share with me the "C:\Program Files\PlasticSCM5\server\plastic.debug.log.txt" file?

Share this post


Link to post
Share on other sites

here it is @manu, thanks for a fast reply!

about CMD arguments - yeah I know but it doesn't help at all, when I run command line as admin, it still says "Windows Service Start failure" so I'm kinda stucked, nither I can run service as it immediately stop nor CMD allow me to do that

plastic.debug.log.txt

Share this post


Link to post
Share on other sites

@manu I read the log file I sent you, it said :

2017-12-20 21:17:36,495 InitServices-7 d2f36bd1-5c3b-47ab-85d6-de9a251b92f0 EVERY_USER_OR_GROUP Server:DESKTOP-EU8ROM3 FATAL LicenseManager - Can't load information

 

so I removed the plasticd.lic file, launched plastic scm server again, it told me another fatal error, afterwards, reinstalled plastic cloud edition and everything worked, what could it be ? Plastic couldn't generate the license file so I had to manually revert it, right ?

Thanks for help anyway!

Share this post


Link to post
Share on other sites

Hello @nazmouse,

thank you for the log provided, I don't understand how the re-installation fixed it, the problem was related with a bad "D:\PlasticSCM5\server\jet\repositories\info.dat" file. The server was not able to read it and refused to start without it.

I'm wondering if reinstalling the license forced the server to re-write the "D:\PlasticSCM5\server\jet\repositories\info.dat" fixing the problem. Because you didn't change the "basepath" on your jet.conf, right? You are still working with your old local repositories, right?

BTW, this is an issue we will be fixing during the next sprint.

Share this post


Link to post
Share on other sites

@manu sorry for the late response, no I didn't change the "basepath" in my jet.conf and I'm still working with my old local repository, right

after manipulations higher my plastic server worked and connection no more got refused, dunno what happened back there, I was tracing all the issues I showed you higher until I figured out it was a problem with the plasticd.lic file then I cleared the entire folder, reinstalled plastic and it worked fine

Share this post


Link to post
Share on other sites

Hi,

I seem to be having the same issue.  Everything has been running fine but today I had a power outage and now can't seem to start the Plastic service: 

0662bd890e87189cc74f1034467f4789.png

 

Hitting both plasticd.exe --console && plasticd.exe --tray results in no change.

I've tried refreshing the info.dat file but no joy there.  Debuglog is attached.  Any ideas on what to try next?

Thanks, Jake

 

plastic.debug.log.txt

Share this post


Link to post
Share on other sites

Hi @jakeslack27,

It seems your "E:\Jet\repositories\info.dat" is wrong:

2018-03-13 15:16:39,622 Main-1 67eb6a4e-3da0-45de-9738-b22a11e2851e EVERY_USER_OR_GROUP Server:JAKE-PC DEBUG datalayerfs -   File 'E:\Jet\repositories\info.dat' opened for reading. Size: 993 bytes.

i need you to do the following.

1) Take the "info.dat_repositories" attached and rename it to info.dat.

2) The the renamed info.dat and use it to replace the one you have at "E:\Jet\repositories\info.dat"

3) Try to start the Plastic SCM server. If everything start working.... hurray! if not go to step #4.

4) You will probably have another error at a different info.dat file, check the log file, check the last line, it will be similar to the one I posted above. Find out the failing one and replace it with the "info.dat_rep" file, attached as well, you will need to rename it to "info.dat".

This issue has been solved at the latest release of Plastic SCM so it would be great if you could upgrade your server.

Tell me if it helps!

info.dat_repositories

info.dat_rep

Share this post


Link to post
Share on other sites

Thank you for the help!

Unfortunately up to 3) didn't solve and service doesn't start but generates a new error:

892dfbf84207e8fcb75b7b54e789df3b.png

Looking at the log file I get:

Quote

2018-03-13 15:16:39,616 Main-1 6a870550-cdad-4a0b-b697-cdc2a6067dc7 EVERY_USER_OR_GROUP Server:JAKE-PC INFO  LicenseManager - License loaded. Users 1; Type eltUnlimited; Generated 12/05/2017 16:12:59; Expires 12/05/2017 16:12:59; Client Cloud Edition license; Features 1
2018-03-13 15:16:39,622 Main-1 67eb6a4e-3da0-45de-9738-b22a11e2851e EVERY_USER_OR_GROUP Server:JAKE-PC DEBUG datalayerfs -   File 'E:\Jet\repositories\info.dat' opened for reading. Size: 993 bytes.
2018-03-13 15:16:39,623 Main-1 67eb6a4e-3da0-45de-9738-b22a11e2851e EVERY_USER_OR_GROUP Server:JAKE-PC FATAL LicenseManager - Can't load information
2018-03-13 19:18:06,089 Main-1    INFO  Daemon - Initialize Datalayer
2018-03-13 19:18:06,106 Main-1    INFO  DatalayerFs.FsConfParser - JET SETTINGS:
2018-03-13 19:18:06,106 Main-1    INFO  DatalayerFs.FsConfParser - basepath=E:\Jet
2018-03-13 19:18:06,106 Main-1    INFO  DatalayerFs.FsConfParser - prefix=
2018-03-13 19:18:06,106 Main-1    INFO  DatalayerFs.FsConfParser - suffix=
2018-03-13 19:18:06,106 Main-1    INFO  DatalayerFs.FsConfParser - maxcachedtrees=50
2018-03-13 19:18:06,107 Main-1    INFO  DatalayerFs.FsConfParser - datafilesize=4294967296
2018-03-13 19:18:06,107 Main-1    INFO  DatalayerFs.FsConfParser - highperf=True
2018-03-13 19:18:06,107 Main-1    INFO  DatalayerFs.FsConfParser - cleaningtemppath=C:\WINDOWS\TEMP\
2018-03-13 19:18:06,121 Main-1    FATAL Daemon - The BlobData file size cannot be changed on existing storage
2018-03-13 19:18:06,126 Main-1    DEBUG Daemon - The BlobData file size cannot be changed on existing storage
   at DatalayerFs.StorageFiles.ValidateBlobDataSize()
   at DatalayerFs.FsDatalayer.Initialize()
   at DatalayerFs.FsDatalayer.Build(FsConf config)
   at Codice.CM.Data.Datalayer.Initialize()
   at akn.a(aas A_0)
   at akn.a(String[] A_0)
2018-03-13 19:19:48,314 Main-1    INFO  Daemon - Initialize Datalayer
2018-03-13 19:19:48,331 Main-1    INFO  DatalayerFs.FsConfParser - JET SETTINGS:
2018-03-13 19:19:48,331 Main-1    INFO  DatalayerFs.FsConfParser - basepath=E:\Jet
2018-03-13 19:19:48,331 Main-1    INFO  DatalayerFs.FsConfParser - prefix=
2018-03-13 19:19:48,332 Main-1    INFO  DatalayerFs.FsConfParser - suffix=
2018-03-13 19:19:48,332 Main-1    INFO  DatalayerFs.FsConfParser - maxcachedtrees=50
2018-03-13 19:19:48,332 Main-1    INFO  DatalayerFs.FsConfParser - datafilesize=4294967296
2018-03-13 19:19:48,332 Main-1    INFO  DatalayerFs.FsConfParser - highperf=True
2018-03-13 19:19:48,332 Main-1    INFO  DatalayerFs.FsConfParser - cleaningtemppath=C:\WINDOWS\TEMP\
2018-03-13 19:19:48,343 Main-1    FATAL Daemon - The BlobData file size cannot be changed on existing storage
2018-03-13 19:19:48,347 Main-1    DEBUG Daemon - The BlobData file size cannot be changed on existing storage
   at DatalayerFs.StorageFiles.ValidateBlobDataSize()
   at DatalayerFs.FsDatalayer.Initialize()
   at DatalayerFs.FsDatalayer.Build(FsConf config)
   at Codice.CM.Data.Datalayer.Initialize()
   at akn.a(aas A_0)
   at akn.a(String[] A_0)

 

So this looks like a different error?

Thanks, Jake

Share this post


Link to post
Share on other sites

It looks like I get the same error with the new info.dat_repositories file:

Quote

2018-03-14 14:25:33,586 Main-1    INFO  Daemon - Initialize Datalayer
2018-03-14 14:25:33,657 Main-1    INFO  DatalayerFs.FsConfParser - JET SETTINGS:
2018-03-14 14:25:33,658 Main-1    INFO  DatalayerFs.FsConfParser - basepath=E:\Jet
2018-03-14 14:25:33,658 Main-1    INFO  DatalayerFs.FsConfParser - prefix=
2018-03-14 14:25:33,658 Main-1    INFO  DatalayerFs.FsConfParser - suffix=
2018-03-14 14:25:33,658 Main-1    INFO  DatalayerFs.FsConfParser - maxcachedtrees=50
2018-03-14 14:25:33,658 Main-1    INFO  DatalayerFs.FsConfParser - datafilesize=4294967296
2018-03-14 14:25:33,658 Main-1    INFO  DatalayerFs.FsConfParser - highperf=True
2018-03-14 14:25:33,658 Main-1    INFO  DatalayerFs.FsConfParser - cleaningtemppath=C:\WINDOWS\TEMP\
2018-03-14 14:25:33,676 Main-1    FATAL Daemon - The BlobData file size cannot be changed on existing storage
2018-03-14 14:25:33,681 Main-1    DEBUG Daemon - The BlobData file size cannot be changed on existing storage
   at DatalayerFs.StorageFiles.ValidateBlobDataSize()
   at DatalayerFs.FsDatalayer.Initialize()
   at DatalayerFs.FsDatalayer.Build(FsConf config)
   at Codice.CM.Data.Datalayer.Initialize()
   at akn.a(aas A_0)
   at akn.a(String[] A_0)
 

 

 

Share this post


Link to post
Share on other sites

Are you available now for a fast online meeting?  Ran out of time :(

Can you tell me when are you available tomorrow and your time zone?

Share this post


Link to post
Share on other sites

Update:

@jakeslack27 and I get connected the issue was indeed with the "info.dat" file.

Replacing the file with a good "info.dat" file was enough to get it up and running again.

We have this issue solved at the latest release of Plastic so I recommend everybody to get upgraded :)

Share this post


Link to post
Share on other sites

Hello manu,

Me and my team have run into this issue recently. We updated the client just today but to no avail. We can just delete the existing info.dat and the server starts but can't find the repositories in the client. Any idea on how we might approach resolving it?

Share this post


Link to post
Share on other sites

Hi @DamirH

Please write to support@codicesoftware.com. We will help you to fix the problem and we can arrange a gotomeeting session with you if necessary.

Regards,

Carlos.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×