500 Internal Server Error when attempting to delete Tags after Import

After doing a large import of 14,000+ listings from another directory into GEO I am getting Errors when attempting to delete Tags.

Error Received:
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator and inform them of the time the error occurred, and the actions you performed just before this error.

I did the upload in 4 separate upload files, I pushed the 2 MB file limit.
I had to turn off Location Data for post type to take my CSV file, I chose to make the post_tag the first field so as not to have to hand delete 14,000 fields of data, and figured I could just delete the Category Tags from the Admin.
———————-
Sample of SCV input file

post_tags,post_title,post_content,geodir_website,post_category,post_author,geodir_email,post_type,post_status
“11571”,”Title”,”Description”,”http://www.site.com”,”Salons”,Author,”admin@mysite.com”,gd_website,publish
___________________
Testing with 100 showing, repeatable behavior.
Select 1- Delete: Works
Select 1- Bulk Actions- Delete -Apply: Works
Select 2- Bulk Actions- Delete- Apply: Works, takes about 1 minute
Select 3- Bulk Actions- Delete- Apply: Error, Refresh Tag Page, 3 of 3 deleted, takes about 3 minutes.
Select 4- Bulk Actions- Delete- Apply: Error, Refresh, 3 of 4 deleted, 3 minutes
Select 5- Bulk Actions- Delete- Apply: Error, Refresh, 3 of 5 deleted.
Select 100- B A- Del- Apply: Error, Refresh, 3 of 100 deleted.

I created 5 tags directly from Tag admin,
**Select 5- Bulk Actions- Delete- Apply: Successful, all 5 deleted no error.**

Select 5 of the imported- BA- Del- Apply: Error, 3 of 5 deleted

I have confirmed this on a completely different internet network, conditions are the same.

Could you also tell me where the Tags are in the Data Base.
I need to be able to dump the Tags ASAP, 13,000+
—————————————–

More information about this error may be available in the server error log.

I attached your login to the Development server where this is being encountered.