We had a problem with our sql server this morning. Since then, we can't publish a project on groupshare (it's stuck on "Publishing project"). The other databases are available (tm's, tb's). All the services are running and the Groupshare server seems perfect. Any idea what could cause this?
Hello Vincent,
Sometimes it's caused by reference (not translatable) files in the project.
Sometimes it happens the project is on a shared volume and Studio can't update the .sdlproj file.
Sometimes you have huge memories/many many files and it takes really a long time to produce analysis/project tm/package to send to the server.
I'd check if the project is available in GS despite the fact Studio didn't confirm the operation, and then decide how to solve from there.
Best regards
Hello Vincent,
Sometimes it's caused by reference (not translatable) files in the project.
Sometimes it happens the project is on a shared volume and Studio can't update the .sdlproj file.
Sometimes you have huge memories/many many files and it takes really a long time to produce analysis/project tm/package to send to the server.
I'd check if the project is available in GS despite the fact Studio didn't confirm the operation, and then decide how to solve from there.
Best regards
SOLVED!
Actually, the SDL Application.exe and the SDL Execution.exe services were stuck in a on/off loop (probably due to the outage). We noticed that when we restarted the services it always skipped those 2. After trying to stop them we got a Error 1061: The service cannot accept control messages at this time.
We killed the processes and restarted the server and everything went back to normal.
It was not due to file sizes or reference files, the publishing task just never started.
Translate
