# Upgrading to Specify 7.7+: HTTP 500 error

**URL:** <https://speciforum.org/t/upgrading-to-specify-7-7-http-500-error/733>\
**Category:** Configuration & Installation\
**Tags:** Specify-7, Members-only\
**Created:** [July 16, 2022, 5:00am UTC](https://speciforum.org/t/upgrading-to-specify-7-7-http-500-error/733 "2022-07-16T05:00:00Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Grant](https://yyz1.discourse-cdn.com/flex029/user_avatar/speciforum.org/grant/32/4255_2.png) [@Grant](https://speciforum.org/u/Grant)\
**Post date:** [July 16, 2022, 5:00am UTC](https://speciforum.org/t/upgrading-to-specify-7-7-http-500-error/733/1 "2022-07-16T05:00:00Z")

</div>

If you are updating to Specify 7.7 or newer, Specify is supposed to create new tables related to the security and accounts features.

If you encounter the following error upon updating to 7.9.3, you should follow the same instructions:

```json
"exception": "ProgrammingError", "message": "1146", "data": "Table 'db_name.uniquenessrule' doesn't exist"

```

In your `docker-compose.yml` file, you should use your **root user credentials** instead of the master user credentials for the first run in Specify 7.

You just need to modify the following lines in the environment section, replacing `root_password` with your root user’s password:

```yml
- MASTER_NAME=root
- MASTER_PASSWORD=root_password

```

After this is complete, you can compose the containers again.

If you are still having trouble on the next run, you can run the following command in MySQL:

```sql
delete from django_migrations where app = 'permissions';

```

This will clear the `spuserpolicy` migration and allow you to run them once again.

Please let us know if you are still having trouble!

* * *

_[If you are encountering other issues with missing tables related to Specify 7, you should run the django\_migrations to ensure that the schema changes have been applied properly.](https://github.com/specify/specify7/#make-django_migrations)_

---

<div class="post-metadata">

**Author:** ![tmisilo](https://yyz1.discourse-cdn.com/flex029/user_avatar/speciforum.org/tmisilo/32/1191_2.png) [@tmisilo](https://speciforum.org/u/tmisilo)\
**Post date:** [February 22, 2023, 3:20pm UTC](https://speciforum.org/t/upgrading-to-specify-7-7-http-500-error/733/2 "2023-02-22T15:20:26Z")

</div>

Hello,

I didn’t see this error, but I am seeing

```auto
ProgrammingError at /context/user.json

(1146, "Table 'specify.agentidentifier' doesn't exist")

Request Method: GET
Request URL: http://dev-biodis22.ksulib.net/context/user.json
Django Version: 2.2.10
Exception Type: ProgrammingError
Exception Value: 	

(1146, "Table 'specify.agentidentifier' doesn't exist")

Exception Location: /opt/specify7/ve/lib/python3.8/site-packages/MySQLdb/connections.py in query, line 276
Python Executable: /opt/specify7/ve/bin/python3.8
Python Version: 3.8.0
Python Path: 	

['/opt/specify7',
 '/opt/specify7',
 '/opt/specify7/ve/bin',
 '/usr/lib/python38.zip',
 '/usr/lib/python3.8',
 '/usr/lib/python3.8/lib-dynload',
 '/opt/specify7/ve/lib/python3.8/site-packages',
 '/opt/specify7']

Server time: Wed, 22 Feb 2023 15:16:51 -0600

```

Any ideas on solving this?

* * *

_Edit by @Grant:_

This has been discussed further in the following topic:

> [@Data Export for Webportal / Specify 7.7 Upgrade](https://speciforum.org/t/data-export-for-webportal-specify-7-7-upgrade/1062/4):
>
> It looks like the schema update did not take place somehow. You could manually change the AppVersion back to 6.8.01 and try to run the update again, though it may skip those tables again. You can [send us a copy of the database](https://spaces.hightail.com/uplink/specify) if you would like us to take a closer look. I should be able to kickstart the process so that the migration runs correctly from here! If you’d prefer to get it working temporarily, you could just change the AppVersion to 6.8.01 and set the corresponding specify6 image b…