Worksharing monitor is blank + Missing .SLOG file?

[Anonymous]

I have a Revit 2018 central model that has never shown any data in the worksharing monitor. I discovered recently that there is no .SLOG (worksharing log) file in the central model's backup folder. I've tried recreating the central model, auditing the file, as well as manually creating the .slog and slog.bak files myself, but the worksharing monitor still shows up blank.  Any ideas on how we can use the worksharing monitor with this model?

blank worksharing monitor

[Corsten.Au]

Hi..

Try This

1. Save the central file.. )

2. Open the file which will create a local file for you

3. Check Work sharing monitor now...

I think if you have the Central file opened directly ( without local ) it doesn't show on 

work sharing monitor.

Cheer!

[Anonymous]

Thanks, but I'm already in a local file and the worksharing monitor doesn't display my username nor the username of the other person in the file.

[Anonymous]

---

@Anonymous wrote:

Thanks, but I'm already in a local file and the worksharing monitor doesn't display my username nor the username of the other person in the file.

---

I have the same issue. Is anyone from Adesk reading this?

[Anonymous]

Getting this exact problem.

Is there a way to fix this without redefining the central file?

[Anonymous]

We are having the same problem, except the slog file is being created, but user information is still not being populated in WSM.  this is happening across multiple years of Revit and we have multiple users on most projects.  This ends up causing syncing issues which usually results in the central file being corrupted.

[Anonymous]

Solution:

This issue happens when your file name and folder Path has more than 256 characters in it. Revit has to create SLOG file that Revit worksharing Monitor access it to report. The slog file will be <FILE NAME>.slog. If you have the long file name and the path exceeding 256 characters, Revit fails to create SLOG file and hence Worksharing Monitor cannot display any data to its interface.

At this stage, Revit does not provide any warnings if it can't create a SLOG file however you will get a warning from Revit while you save RVT file that exceeds 256 Characters.

The solution is to reduce the number f character in the file name or folder Path. You can use MS Word to copy the path from Windows explorer to count the character. Below is an example to replicate the issue.

Hope this helps.

[Anonymous]

hi @Anonymous  , Please see if the below solution helps.

If you find this reply helpful kindly hit the LIKE BUTTON and if applicable please ACCEPT AS SOLUTION

[JanUsinger]

We have encountered the same issue and reducing the length of the file name did indeed fix the problem.

Thank you @Anonymous .

[Anonymous]

thank you, this appears to be the correct fix.

[Amanda_Lunger_AM]

@Anonymous We have also this had this issue where the .slog file exists on several projects in our office, but no information is displayed in Worksharing monitor. I checked our file path length (including file name) and we are well below the 256 character limit. 

The only "fix" we have found is resetting and renaming the central file. Without renaming the central file, we are not able to delete the original .slog file in the backups folder. Are there any other known factors besides file path length that would cause this issue, or cause the .slog file to be corrupt?