No history of Users or Assets showing in Version v8.0.4 - build 17196 (master)

[Pkumar22in]

Hi,

I recently installed Version v8.0.4 - build 17196 (master) and I noticed that I can't see the Device or User history, Any idea or clue where I should look

regards Prem

[snipe]

Hi - sorry you're having trouble. As mentioned in the docs, we need a stack trace and browser console errors in order to help you.

You can do one of the following, per the docs:

1. Tail the log file and trigger the error, providing us with whatever new information appears in the log file when the error occurs. More information is available in the documentation.
2. Provide the contents of your storage/logs/laravel.log. Please do not attach files, just paste in the log lines that occur when you trigger the error. It's okay if they're long, but re-triggering the error (
3. For systems NOT exposed to the internet only: Turn APP_DEBUG=true and then trigger the error and show us what's on the screen. Debug mode can expose sensitive information that you do not want the world to see.

https://snipe-it.readme.io/docs/getting-help https://snipe-it.readme.io/docs/advanced-debugging

If this error is occurring within the web UI, you should also check your browser console logs.

Providing this information will allow us to better isolate whether the issue is a configuration issue or a bug on our end, and will help us answer your questions much more quickly. The more specific you can be, the better we can target the issue for you.

Snipe-IT Documentation

Getting Help

If you're having trouble setting up Snipe-IT, don't worry!

Snipe-IT Documentation

Advanced Debugging

Snipe-IT ships with the Laravel Debugbar, an amazing piece of software that lets you introspect much further into the framework and application to troubleshoot issues that may be a little harder to track down. To enable the debugbar, set the following in your .env file, and clear your config cache: ...

[rajesh2728]

I am also facing the same issue, Asset History is showing blank page, but able to view user and license history. The activity reports are also seems to be fine, I am getting all the changes. Only I am not able to view the asset history.

My Snipeit Version v8.1.15 - build 18405 (master)

I already changed to BS_TABLE_STORAGE=localStorage

[snipe]

@rajesh2728 did you also clear your browser cookies?

[rajesh2728]

@snipe, yes I already cleared the browser cookies, also I tried with different browser.

[snipe]

@rajesh2728 do you have anything in your error logs or browser console?

[rajesh2728]

@snipe /var/www/html/snipeit# tail -f storage/logs/laravel.log [2025-06-13 14:32:17] production.WARNING: User sysadmin (ID: 1) is attempting a PURGE

[snipe]

@rajesh2728 - thanks, that's really helpful. Do you perhaps have a "weird" character in your asset name? What language are you set to in your view of Snipe-IT?

[snipe]

@uberbrady can you take a look at that JS and see if there's anything that stands out where some strange encoding or characters would break the table rendering?

[rajesh2728]

@uberbrady can you take a look at that JS and see if there's anything that stands out where some strange encoding or characters would break the table rendering?

Snipe

@snipe , its a default English US. I guess, there is no any weird characters on Assets information. Is re-installing the snipe it will resolve the issue? if yes, please share me the steps.

[uberbrady]

I think the actual problem here is something else; the "Bad character in JSON" is just a red herring.

You probably need to run: php artisan migrate - and take a close look at the output.

What I think is happening is that you're missing some new columns that we've added. So some parts of Snipe-IT load up fine, but stuff that actually looks at lists of assets or things like that actually causes an error 500 - which will probably return an HTML page, which is not valid JSON. The way a lot of those views work is that they load up their contents via that JSON call.

You would probably get a pretty good idea about this in the Laravel error logs - on your Snipe-IT instance, find the file storage/logs/laravel.log and look at the output, near the bottom. That's probably going to say something like: "Unknown column 'blah' in table 'blah'" or something like that. That's a sure sign that you're missing migrations.

But, also - if your migrations won't run correctly, you might need to upgrade your database. This is a newly-discovered requirement that we never imposed, but was done either by our framework vendor, or the database vendors themselves. We're still trying to dig through that, but it's a pain.

[rajesh2728]

Hello,

php artisan migrate - says nothing to migrate.

I cleared storage/logs/laravel.log - and tried to re produce the error - but it seems to be empty.

The table assest_logs - are empty.

Is the below error is relevant to this issue:

Warning: Ambiguous class resolution, "League\Flysystem\AwsS3V3\AwsS3V3AdapterTes t" was found in both "/var/www/html/snipeit/vendor/league/flysystem-aws-s3-v3/Aw sS3V3AdapterTest.php" and "/var/www/html/snipeit/vendor/league/flysystem/src/Aws S3V3/AwsS3V3AdapterTest.php", the first will be used. Warning: Ambiguous class resolution, "League\Flysystem\AwsS3V3\AwsS3V3Adapter" w as found in both "/var/www/html/snipeit/vendor/league/flysystem-aws-s3-v3/AwsS3V 3Adapter.php" and "/var/www/html/snipeit/vendor/league/flysystem/src/AwsS3V3/Aws S3V3Adapter.php", the first will be used. Warning: Ambiguous class resolution, "League\Flysystem\AwsS3V3\PortableVisibilit yConverter" was found in both "/var/www/html/snipeit/vendor/league/flysystem-aws -s3-v3/PortableVisibilityConverter.php" and "/var/www/html/snipeit/vendor/league /flysystem/src/AwsS3V3/PortableVisibilityConverter.php", the first will be used. Warning: Ambiguous class resolution, "League\Flysystem\AwsS3V3\S3ClientStub" was found in both "/var/www/html/snipeit/vendor/league/flysystem-aws-s3-v3/S3Client Stub.php" and "/var/www/html/snipeit/vendor/league/flysystem/src/AwsS3V3/S3Clien tStub.php", the first will be used. Warning: Ambiguous class resolution, "League\Flysystem\AwsS3V3\VisibilityConvert er" was found in both "/var/www/html/snipeit/vendor/league/flysystem-aws-s3-v3/V isibilityConverter.php" and "/var/www/html/snipeit/vendor/league/flysystem/src/A wsS3V3/VisibilityConverter.php", the first will be used. Warning: Ambiguous class resolution, "League\Flysystem\Local\FallbackMimeTypeDet ector" was found in both "/var/www/html/snipeit/vendor/league/flysystem-local/Fa llbackMimeTypeDetector.php" and "/var/www/html/snipeit/vendor/league/flysystem/s rc/Local/FallbackMimeTypeDetector.php", the first will be used. Warning: Ambiguous class resolution, "League\Flysystem\Local\LocalFilesystemAdap ter" was found in both "/var/www/html/snipeit/vendor/league/flysystem-local/Loca lFilesystemAdapter.php" and "/var/www/html/snipeit/vendor/league/flysystem/src/L ocal/LocalFilesystemAdapter.php", the first will be used. Warning: Ambiguous class resolution, "League\Flysystem\Local\LocalFilesystemAdap terTest" was found in both "/var/www/html/snipeit/vendor/league/flysystem-local/ LocalFilesystemAdapterTest.php" and "/var/www/html/snipeit/vendor/league/flysyst em/src/Local/LocalFilesystemAdapterTest.php", the first will be used.

[snipe]

The table assest_logs - are empty.

That's normal, that table isn't used. storage/logs/laravel.log is where logs would be. Check the permissions on your storage directory and everything within it to make sure it's writable by the user the web server runs as. You should at least see something in there, and it's weird that you don't.

[uberbrady]

That "Ambiguous class resolution" error I have seen before - I suspect that you can at least make that go away by doing this:

1. Take a backup. Ideally, some kind of 'snapshot' that you can quickly and easily restore to.
2. delete the ./vendors directory
3. Run composer install (or php composer.phar install, depending on how you have composer installed on your machine.

Then, you can see if you can still replicate the bug, and/or try to re run php artisan migrate, and see what you get.

[snipe]

Hi there - We haven't heard back in a bit, so I'm going to close this ticket for now, but will re-open it if you're still having issues.