Looking for help?
Unsure where to begin or need guidance on using Ideagen Luminate? Explore our detailed articles below for step-by-step assistance.
Guides
Send us feedback
Before you start
This form is for Ideagen Luminate feedback only.
Your submission will not receive a response. To request solution support, open a ticket with us.
We'd love to hear your thoughts—whether it’s a feature suggestion, usability improvement, or what you love about Ideagen Luminate.
We have recieved your feedback
Thank you for sharing! Your input helps us enhance Luminate for all users. Feel free to close this window now.
I can’t get any answers from support since they quit responding to my emails for the past 2 weeks.
All we’re trying to do is move a Q Pulse Database from one SQL server to another. We’ve actually completed that task, and everything shows up when we connect to it, but we get an error. When We connect to the DB and try to open a file from the repository, we get an error that says:
Could not open part.
Could not lock the part ####.
Does it have something to do with the old DB connecting to the repository/Network Share.
Do we need to create a new DB and then move the data to it.
Do we need to move the repository/Network share to a new server.
It sounds like the migration worked for the database itself but the repository files are still being referenced from the old network path. Q Pulse stores metadata in SQL but the actual documents are often in a shared repository folder, so if that share wasn’t moved or permissions weren’t updated on the new server, you’ll get “could not open/lock” errors. I’d confirm the repository path in Q Pulse configuration, make sure the new SQL instance can access it, and if needed move the share and update the DB entries. If you suspect database corruption from the migration, Stellar Repair for MS SQL can help fix issues without data loss.
www.stellarinfo.com/sql-recovery.php
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.