Comments
4 comments
-
Additional information from log file:
21 Sep 2010 15:22:18,870 [1] INFO RedGate.SqlPrompt.Engine.LogService - Starting new SQL Prompt editor session
21 Sep 2010 15:23:04,652 [1] WARN RedGate.SQLPrompt.CommonUI.Editor.EditorWindowBase - Cache had warnings
System.NullReferenceException: Object reference not set to an instance of an object.
at RedGate.SqlPrompt.Cache.Candidates.SynonymCandidate.get_ObjectType()
at RedGate.SqlPrompt.Cache.CandidateCollections.CandidateCollectionMultiType`1.Add(String key, T value)
at RedGate.SqlPrompt.Cache.Candidates.DatabaseCandidateBase.??(IDataReader reader, IDictionary`2 users, IDictionary`2 objects, IDictionary`2 tablecolumns)
at RedGate.SqlPrompt.Cache.Candidates.DatabaseCandidateBase. -
I'm getting similar errors. Some out of memory warning when trying to hit more than one DB. Any way to roll back or get a different build?
-Peter -
Thanks for your report. We're looking into it.
If you want to roll back to the first Early Access for now, uninstall SQL Prompt 5 using the Control Panel and then reinstall 5.0.0.224.
Paul Stephenson
SQL Prompt Project Manager
Red Gate Software -
I had to roll back. I couldn't even start using SSMS today. Not sure it's 100% related, but I didn't have that problem with .224. Re-installed that version and I can work again.
Add comment
Please sign in to leave a comment.
The error reads:
"SQL Prompt could not retrieve all schema information for <database name>".
Object reference not set to an instance of an object." (<database name> is just a placeholder for any database name).
I restarted SSMS several times, but no way. Since our servers, my login and my permissions have not changed within the minute of updating SQL Prompt, I guess that this build causes the error.
Any ideas would be greatly appreciated. Thanks!