I have SQL 2005, 64bit version installed with SP1. I am seeing the followin
g
errors in the Windows event log:
Source: SideBySide Event ID: 59
Resolve Partial Assembly failed for Microsoft.VC80.CRT.mui. Reference error
message: Access is denied.
Source: SidebySide EventID: 59
Generate Activation Context failed for D:\Program Files\Microsoft SQL
Server\MSSQL.2\OLAP\bin\msmdctr90.DLL. Reference error message: Access is
denied.
Source: PerfLib EventID: 1023
Windows cannot load extensible counter DLL MSSQLServerOLAPService, the first
DWORD in data section is the Windows error code.
Does anyone know what the problem is?
Thanks
--
LehrSJHello LehrSJ,
I understand that you found some SQL related events on a SQL 2005 SP1 64bit
server, and you'd like to know what this problem is.
Based on my experience, this issue could occur if the "Performance Logs and
Alerts" service runs as "Network Service", which is member of "Performance
Log Users" local user group, does not have enough permission to SQL setup
folder.
SQL Setup grants read/execute permissions to "Performance Log Users" local
user group for the DLL only. "Performance Log Users" doesnt have any
permissions for the containing folder. Granting "List folder contents"
permission to "Performance Log Users" for the containing folder (SQL Server
binn directory) may fix this problem:
D:\Program Files\Microsoft SQL Server\MSSQL.1\mssql\bin
D:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\bin
If you have any update or the issue is not resolved, please feel free to
let's know. I look forward to your reply.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Community Support
========================================
==========
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscript...ault.aspx#notif
ications
<http://msdn.microsoft.com/subscript...ps/default.aspx>.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
<http://msdn.microsoft.com/subscript...rt/default.aspx>.
========================================
==========
This posting is provided "AS IS" with no warranties, and confers no rights.|||Thanks. That solved the problem.
--
LehrSJ
""privatenews"" wrote:
> Hello LehrSJ,
> I understand that you found some SQL related events on a SQL 2005 SP1 64bi
t
> server, and you'd like to know what this problem is.
> Based on my experience, this issue could occur if the "Performance Logs an
d
> Alerts" service runs as "Network Service", which is member of "Performance
> Log Users" local user group, does not have enough permission to SQL setup
> folder.
> SQL Setup grants read/execute permissions to "Performance Log Users" local
> user group for the DLL only. "Performance Log Users" doesn’t have any
> permissions for the containing folder. Granting "List folder contents"
> permission to "Performance Log Users" for the containing folder (SQL Serve
r
> binn directory) may fix this problem:
> D:\Program Files\Microsoft SQL Server\MSSQL.1\mssql\bin
> D:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\bin
> If you have any update or the issue is not resolved, please feel free to
> let's know. I look forward to your reply.
> Best Regards,
> Peter Yang
> MCSE2000/2003, MCSA, MCDBA
> Microsoft Online Community Support
> ========================================
==========
> Get notification to my posts through email? Please refer to
> l]
> ications
> <[url]http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx" target="_blank">http://msdn.microsoft.com/subscript...ps/default.aspx>.
> Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
> where an initial response from the community or a Microsoft Support
> Engineer within 1 business day is acceptable. Please note that each follow
> up response may take approximately 2 business days as the support
> professional working with you may need further investigation to reach the
> most efficient resolution. The offering is not appropriate for situations
> that require urgent, real-time or phone-based interactions or complex
> project analysis and dump analysis issues. Issues of this nature are best
> handled working with a dedicated Microsoft Support Engineer by contacting
> Microsoft Customer Support Services (CSS) at
> <http://msdn.microsoft.com/subscript...rt/default.aspx>.
> ========================================
==========
> This posting is provided "AS IS" with no warranties, and confers no rights
.
>|||I was having this problem as well on a 32 bit system and that fixed it.
Can you explain why that fixed it? I'm asking because I was also having
2 other problems that I think this fixed as well.
first one: There is a Java program that inserts updates and deletes
records in a very large table on the sql server. It spawns 12 processes
that each have a connection to the DB and every time this program ran,
2 of them would hang up and would not receive any errors. I looked and
they were no longer connected.
second one: The users of this server have pocket pcs that connect using
sql ce server with RDA. They use an app that we wrote to replicate
their data. Along with all the pushing and pulling of tables, there is
one stored procedure that the client runs on the server. Apparently
randomly this stored procedure stops working for about 30 minutes at a
time. What happens on the client is when it calls that sp, it just
hangs there maintaining it's connection until all the sudden the sp
start working again. During the 30 minutes nobody can run the sp.
Both of these problems did not exist before we got Error 59 or after it
was fixed.
Does anybody have any clue as to why this would fix these 2 problems or
has anybody experienced anything like this?
thanks,
cob
