Provide Used: Microsoft OLE DB Provider for SQL Server. Can anyone help me with this.. I was trying to connect with LLBLgen
提供使用:用于SQL Server的Microsoft OLE DB提供程序。任何人都可以帮我这个..我试图与LLBLgen联系
10 个解决方案
#1
2
This MSDN blog page has some useful on this...
这个MSDN博客页面有一些有用的...
#2
2
In my case, I found the account was locked. Reason was I previously, on another machine more than 3 times tried to login. It did not recognise me - and tthen finally it locked my account.
就我而言,我发现该帐户已被锁定。原因是我以前,在另一台机器上尝试登录超过3次。它不认识我 - 然后它终于锁定了我的帐户。
Reopening account made all work fine.
重新开帐户使一切正常。
br Jan
#3
1
The error you get is almost always caused by a problem with using Windows Authentication. Please try switching to a SQL server login (username/password), or make sure your current Windows login has access to the SQL server and database you're trying to connect to.
您获得的错误几乎总是由使用Windows身份验证的问题引起的。请尝试切换到SQL服务器登录名(用户名/密码),或确保您当前的Windows登录名有权访问您尝试连接的SQL服务器和数据库。
-Edoode
#4
1
I fixed this by mapping a drive to the server running MSSQL. This seemed to generate some kind of trust that allows MSSQL to connect without this error even after a reboot.
我通过将驱动器映射到运行MSSQL的服务器来修复此问题。这似乎产生某种信任,允许MSSQL即使在重新启动后也没有出现此错误。
#5
0
I used to get this error sometimes when connecting to my local SQL Server with Windows Authentication. I never fixed it unfortunately - it went away when I reinstalled windows.
我有时在使用Windows身份验证连接到本地SQL Server时会出现此错误。我从来没有修好它 - 当我重新安装Windows时它就消失了。
I think a reboot used to fix it - have you tried that? Not exactly the best solution, I know :P
我认为用于修复它的重启 - 你试过吗?我知道,这不是最好的解决方案:P
#6
0
Try to synchronize your date and time with the your domain's. The SSPI issue may be related to Active Directory authentication problems, some of them related to date and time changes. This is very simple to check and fix. Try it out!
尝试将您的日期和时间与您的域名同步。 SSPI问题可能与Active Directory身份验证问题有关,其中一些问题与日期和时间更改有关。这很容易检查和修复。试试看!
#7
0
There is a Microsoft KB article that addresses many of the reasons for this area (KB811889) at the following URL: http://support.microsoft.com/kb/811889.
Microsoft KB文章在以下URL中解决了该领域的许多原因(KB811889):http://support.microsoft.com/kb/811889。
A lot of Googling shows that one of the diagnostic steps helped most people who encountered the issue.
许多谷歌搜索显示,其中一个诊断步骤帮助了大多数遇到此问题的人。
I recently had this exact issue where I'd get this error only when authenticating with certain accounts, but not others. Ultimately what was causing my problem was not mentioned in any KB or article I found on the net, but through trial and error I discovered that when the account used through SSPI authentication to SQL Server (2k8) happened to be in a large number of groups (in my case over 250) you would get the "Cannot Generate SSPI context" error. I suspect it has something to do with overflowing the security token that Kerberos uses and have seen similar strange authentication problems for user accounts in a large number of groups.
我最近有这个确切的问题,我只有在使用某些帐户进行身份验证时才会收到此错误,而不是其他帐户。最终导致我的问题的是我在网上找到的任何KB或文章中都没有提到,但是通过反复试验,我发现当通过SSPI身份验证使用到SQL Server(2k8)的帐户碰巧出现在大量的群组中时(在我的情况下超过250)你会得到“无法生成SSPI上下文”错误。我怀疑它与溢出Kerberos使用的安全令牌有关,并且已经看到许多组中的用户帐户存在类似的奇怪身份验证问题。
#8
0
I get the problem when I have the time set differently on my client machine than either the server or the AD machine ( I was trying to test into the future).
当我在客户端计算机上设置的时间与服务器或AD计算机的设置不同时,我遇到了问题(我试图测试未来)。
#9
0
Short Answer: Have you recently change the user the service is running as? Was there a system crash?
简答:您最近是否更改了服务运行的用户?系统崩溃了吗?
Long Answer: I know this is old, but I want to post my experience that I just had. We had spent hours Googling and found nothing that worked. Eventually we ran across a set of actions that could cause this:
答案:我知道这已经过时了,但我想发布我刚才的经历。我们花了几个小时谷歌搜索,发现没有任何工作。最终我们遇到了一系列可能导致此问题的操作:
If you change the user that the Sql Server runs as (e.g. from Local System to a domain usr) and do certain updates and the server doesn't safely reboot -- you get this.
如果您更改Sql Server运行的用户(例如从本地系统更改为域usr)并执行某些更新,并且服务器无法安全地重新启动 - 那么您就可以了。
So, we set things back to Local System and bam it worked. Swapped it to the domain user, no worky worky. Ok. Swapped it to Local System, rebooted, swapped it to domain user, rebooted, bam -- worky worky. All was good in our world. Later that morning it crapped out again... still working on that now but the priority is changing and I'm not sure we're going to continue work on this problem so I wanted to post something in case this happens to someone else.
因此,我们将事情重新设置为本地系统,并使其发挥作用。将其交给域用户,没有任何工作。好。将其交换到本地系统,重新启动,将其交换到域用户,重新启动,bam - worky worky。一切都在我们的世界里很好。那天上午晚些时候它再次被淘汰......现在仍然在努力,但优先事项正在发生变化,我不确定我们是否会继续解决这个问题,所以我想发布一些事情以防万一发生在其他人身上。
What caused ours was we did an update and, apparently, we learned that it's bad practice to let Sql Server run as Local System so we changed it to a domain user. We never rebooted, but restart the service. A month later, we do updates. We don't reboot. A month goes by and a power strip fries causing the server to have an unexpected shutdown. Yet another month later we find out problem because we rarely connect to this particular database (Interestingly, Sql Server 2008 worked fine... it was only 2005). Or... at least this is the best we've come across.
导致我们的原因是我们做了更新,显然,我们了解到让Sql Server作为本地系统运行是不好的做法,因此我们将其更改为域用户。我们从未重启,但重新启动服务。一个月后,我们会做更新。我们不重启。一个月过去了,电源板炸薯条导致服务器意外关机。又一个月后,我们发现了问题,因为我们很少连接到这个特定的数据库(有趣的是,Sql Server 2008运行良好...它只是2005年)。或者......至少这是我们遇到的最好的。
Our admin guy doesn't like Vista and likes to blame everything on Vista (refuses to let us test Windows 7)... so he Googled "sspi vista" or something like (I know it had sspi and vista, but it might have had another one... in case you need to Google it was well) that and ran across an article that pretty explained our scenario after we had a meeting we all remember these pieces and placed this picture together.
我们的管理员不喜欢Vista,并喜欢责怪Vista上的一切(拒绝让我们测试Windows 7)...所以他用Google搜索“sspi vista”或类似的东西(我知道它有sspi和vista,但它可能有还有另外一个......如果你需要谷歌那就很好了)并且在我们开会后我们都记得很好地解释了我们的场景并将这张图片放在一起。
#10
0
In my case, the time synchronization issue in the Windows 2003 domain environment was actually the issue.
在我的例子中,Windows 2003域环境中的时间同步问题实际上是问题。
This was quite easy to overlook as the two had been on two different time zones, whilst showing the same times on their clocks; which in effect was about 1 hour apart.
这很容易被忽视,因为两人在两个不同的时区,同时在他们的时钟上显示相同的时间;实际上相隔大约1小时。
So other than the time on their watches, check the time zones as well.
除了手表上的时间外,还要检查时区。
#1
2
This MSDN blog page has some useful on this...
这个MSDN博客页面有一些有用的...
#2
2
In my case, I found the account was locked. Reason was I previously, on another machine more than 3 times tried to login. It did not recognise me - and tthen finally it locked my account.
就我而言,我发现该帐户已被锁定。原因是我以前,在另一台机器上尝试登录超过3次。它不认识我 - 然后它终于锁定了我的帐户。
Reopening account made all work fine.
重新开帐户使一切正常。
br Jan
#3
1
The error you get is almost always caused by a problem with using Windows Authentication. Please try switching to a SQL server login (username/password), or make sure your current Windows login has access to the SQL server and database you're trying to connect to.
您获得的错误几乎总是由使用Windows身份验证的问题引起的。请尝试切换到SQL服务器登录名(用户名/密码),或确保您当前的Windows登录名有权访问您尝试连接的SQL服务器和数据库。
-Edoode
#4
1
I fixed this by mapping a drive to the server running MSSQL. This seemed to generate some kind of trust that allows MSSQL to connect without this error even after a reboot.
我通过将驱动器映射到运行MSSQL的服务器来修复此问题。这似乎产生某种信任,允许MSSQL即使在重新启动后也没有出现此错误。
#5
0
I used to get this error sometimes when connecting to my local SQL Server with Windows Authentication. I never fixed it unfortunately - it went away when I reinstalled windows.
我有时在使用Windows身份验证连接到本地SQL Server时会出现此错误。我从来没有修好它 - 当我重新安装Windows时它就消失了。
I think a reboot used to fix it - have you tried that? Not exactly the best solution, I know :P
我认为用于修复它的重启 - 你试过吗?我知道,这不是最好的解决方案:P
#6
0
Try to synchronize your date and time with the your domain's. The SSPI issue may be related to Active Directory authentication problems, some of them related to date and time changes. This is very simple to check and fix. Try it out!
尝试将您的日期和时间与您的域名同步。 SSPI问题可能与Active Directory身份验证问题有关,其中一些问题与日期和时间更改有关。这很容易检查和修复。试试看!
#7
0
There is a Microsoft KB article that addresses many of the reasons for this area (KB811889) at the following URL: http://support.microsoft.com/kb/811889.
Microsoft KB文章在以下URL中解决了该领域的许多原因(KB811889):http://support.microsoft.com/kb/811889。
A lot of Googling shows that one of the diagnostic steps helped most people who encountered the issue.
许多谷歌搜索显示,其中一个诊断步骤帮助了大多数遇到此问题的人。
I recently had this exact issue where I'd get this error only when authenticating with certain accounts, but not others. Ultimately what was causing my problem was not mentioned in any KB or article I found on the net, but through trial and error I discovered that when the account used through SSPI authentication to SQL Server (2k8) happened to be in a large number of groups (in my case over 250) you would get the "Cannot Generate SSPI context" error. I suspect it has something to do with overflowing the security token that Kerberos uses and have seen similar strange authentication problems for user accounts in a large number of groups.
我最近有这个确切的问题,我只有在使用某些帐户进行身份验证时才会收到此错误,而不是其他帐户。最终导致我的问题的是我在网上找到的任何KB或文章中都没有提到,但是通过反复试验,我发现当通过SSPI身份验证使用到SQL Server(2k8)的帐户碰巧出现在大量的群组中时(在我的情况下超过250)你会得到“无法生成SSPI上下文”错误。我怀疑它与溢出Kerberos使用的安全令牌有关,并且已经看到许多组中的用户帐户存在类似的奇怪身份验证问题。
#8
0
I get the problem when I have the time set differently on my client machine than either the server or the AD machine ( I was trying to test into the future).
当我在客户端计算机上设置的时间与服务器或AD计算机的设置不同时,我遇到了问题(我试图测试未来)。
#9
0
Short Answer: Have you recently change the user the service is running as? Was there a system crash?
简答:您最近是否更改了服务运行的用户?系统崩溃了吗?
Long Answer: I know this is old, but I want to post my experience that I just had. We had spent hours Googling and found nothing that worked. Eventually we ran across a set of actions that could cause this:
答案:我知道这已经过时了,但我想发布我刚才的经历。我们花了几个小时谷歌搜索,发现没有任何工作。最终我们遇到了一系列可能导致此问题的操作:
If you change the user that the Sql Server runs as (e.g. from Local System to a domain usr) and do certain updates and the server doesn't safely reboot -- you get this.
如果您更改Sql Server运行的用户(例如从本地系统更改为域usr)并执行某些更新,并且服务器无法安全地重新启动 - 那么您就可以了。
So, we set things back to Local System and bam it worked. Swapped it to the domain user, no worky worky. Ok. Swapped it to Local System, rebooted, swapped it to domain user, rebooted, bam -- worky worky. All was good in our world. Later that morning it crapped out again... still working on that now but the priority is changing and I'm not sure we're going to continue work on this problem so I wanted to post something in case this happens to someone else.
因此,我们将事情重新设置为本地系统,并使其发挥作用。将其交给域用户,没有任何工作。好。将其交换到本地系统,重新启动,将其交换到域用户,重新启动,bam - worky worky。一切都在我们的世界里很好。那天上午晚些时候它再次被淘汰......现在仍然在努力,但优先事项正在发生变化,我不确定我们是否会继续解决这个问题,所以我想发布一些事情以防万一发生在其他人身上。
What caused ours was we did an update and, apparently, we learned that it's bad practice to let Sql Server run as Local System so we changed it to a domain user. We never rebooted, but restart the service. A month later, we do updates. We don't reboot. A month goes by and a power strip fries causing the server to have an unexpected shutdown. Yet another month later we find out problem because we rarely connect to this particular database (Interestingly, Sql Server 2008 worked fine... it was only 2005). Or... at least this is the best we've come across.
导致我们的原因是我们做了更新,显然,我们了解到让Sql Server作为本地系统运行是不好的做法,因此我们将其更改为域用户。我们从未重启,但重新启动服务。一个月后,我们会做更新。我们不重启。一个月过去了,电源板炸薯条导致服务器意外关机。又一个月后,我们发现了问题,因为我们很少连接到这个特定的数据库(有趣的是,Sql Server 2008运行良好...它只是2005年)。或者......至少这是我们遇到的最好的。
Our admin guy doesn't like Vista and likes to blame everything on Vista (refuses to let us test Windows 7)... so he Googled "sspi vista" or something like (I know it had sspi and vista, but it might have had another one... in case you need to Google it was well) that and ran across an article that pretty explained our scenario after we had a meeting we all remember these pieces and placed this picture together.
我们的管理员不喜欢Vista,并喜欢责怪Vista上的一切(拒绝让我们测试Windows 7)...所以他用Google搜索“sspi vista”或类似的东西(我知道它有sspi和vista,但它可能有还有另外一个......如果你需要谷歌那就很好了)并且在我们开会后我们都记得很好地解释了我们的场景并将这张图片放在一起。
#10
0
In my case, the time synchronization issue in the Windows 2003 domain environment was actually the issue.
在我的例子中,Windows 2003域环境中的时间同步问题实际上是问题。
This was quite easy to overlook as the two had been on two different time zones, whilst showing the same times on their clocks; which in effect was about 1 hour apart.
这很容易被忽视,因为两人在两个不同的时区,同时在他们的时钟上显示相同的时间;实际上相隔大约1小时。
So other than the time on their watches, check the time zones as well.
除了手表上的时间外,还要检查时区。