Comments
Sort by recent activity
Thanks, Jason.
Do you happen to know if this fix will require us to install version 5.2 on our servers or will installing the client application on our local machines suffice?
Thanks, again. / comments
Thanks, Jason.
Do you happen to know if this fix will require us to install version 5.2 on our servers or will installing the client application on our local machines suffice?
Thanks, again.
Thanks for your response, Brian.
I always use an account with Sysadmin permissions to connect to the SQL Docs 2 project.
I've run DBCC Check on the database and found nothing wrong internally. If I remove the offending object from the list of objects to document, it stumbles over an object further down the list. If I remove that object and it stumbles over another object yet further down the list. I've tried this about 10 times and decided that even if it did finally succeed, the resulting documentation would be missing so many items as to be quite useless.
It would be nice if SQL Doc would tell me what it's expecting to find that isn't there. It must know if there is an "object reference" in the first place. It doesn't do that, however, nor does it write this information to its log. If I knew what it was stumbling over, I could fix it, but there are just too many objects in this database to guess.
Any ideas or strategies you may have for tracking down this "missing" object would be greatly appreciated.
Thanks again, Brian. / comments
Thanks for your response, Brian.
I always use an account with Sysadmin permissions to connect to the SQL Docs 2 project.
I've run DBCC Check on the database and found nothing wrong internally. If ...
Was this issue ever resolved? I'd be very intersted in the resolution.
I'm having the very same problem (SQL Server 2005, local OS: Windows 7, SQL Doc v2.1.2.1) and I'd like to know how to fix it. Unfortunately the SQL Doc log doesn't help me much but I'd be happy to make it available to anyone who thinks it might help them unravel this problem.
Thanks! / comments
Was this issue ever resolved? I'd be very intersted in the resolution.
I'm having the very same problem (SQL Server 2005, local OS: Windows 7, SQL Doc v2.1.2.1) and I'd like to know how to fix it....
Adding the SQL Monitor site to my "Trusted Sites" zone seems to have resolved the problem for me. (At least for now.)
It seems reasonable to think that if you remove it from your Trusted Sites zone, you may be one step closer to duplicating this problem.
IMHO, this is a serious compatibility issue with the most widely used browser on the internet. (Yes, I know IE is declining rapidly in popularity but, at least for now, it appears to still be in the lead.) Moreover, many companies have business critical web applications that prevent them from moving to other browsers (or even other versions of Internet Explorer). Switching to another browser just isn't an option in many cases and certainly no solution to this problem.
Hopefully, adding the SQL Monitor site to the Trusted Sites zone will be a workable solution for others as it seems to have been for me. Thanks for the suggestion. / comments
Adding the SQL Monitor site to my "Trusted Sites" zone seems to have resolved the problem for me. (At least for now.)
It seems reasonable to think that if you remove it from your Trusted Sites zon...