Comments
1 comment
-
Official comment
Hi mattewwade06,
Thanks for your reaching out on the Redgate forums regarding your SQL Date Generator error message — the issue you're seeing does sound similar to a past case we've come across.
In that instance, the root cause was that even after copying the project to a different network drive/location, the internal references to pre/post scripts were still pointing to the original network location.
If that network path becomes unavailable, it can lead to errors like "network name not found" and crashes when editing the project.
Suggested steps:
- Re-store the project to the last known working location
- Open the project and delete any pre- or post-deployment scripts that reference the network path.
- Copy the project to the mapped drive.
- Re-import the scripts from the mapped drive to ensure all internal references are valid.
- Save the project and try opening it again via “Edit Project…”
Hopefully this process will allow you to clear this invalid network reference and allow the project to be used in the new location.
Add comment
Please sign in to leave a comment.
Hello!
I moved a couple of SQL Data Generator projects from one server to another and placed them on a mapped drive. Initially, everything worked fine I could open the project, make minor edits, and run them on my local SQL Server as well as our remote TEST server.
But now when I try to open the project , it lets me load it and make a few changes, but the moment I go to "Edit the Project" to view pre and post scripts, it throws an error saying "network name not found or not connect." Then the app crashes and prompts to send an error report to Red Gate, which I’ve already done a few times.
Not sure if it's a permissions issue or something with the drive mapping, but I haven’t changed anything major aside from relocating some shared folders. Any suggestions on how to fix this?
Thanks!