Google Mail Calendar Documents Reader Web more »
Recently Visited Groups | Help | Sign in
Google Groups Home
microsoft.public.security.baseline_analyzer
+ new post
About this group
Subscribe to this group
This is a Usenet group - learn more
MBSA 2.1 and SQL Server 2005
Options
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
   1 message - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Follow-up To:
Add Cc | Add Follow-up to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers that you hear
 
Pablo Domingo  
View profile   Translate to Translated (View Original)
 More options 30 Sep, 19:10
Newsgroups: microsoft.public.security.baseline_analyzer
From: Pablo Domingo <PabloDomi...@discussions.microsoft.com>
Date: Wed, 30 Sep 2009 11:10:03 -0700
Local: Wed 30 Sep 2009 19:10
Subject: MBSA 2.1 and SQL Server 2005
Reply to author | Forward | Print | Individual message | Show original | Report this message | Find messages by this author
I'm running MBSA 2.1 on a fully patched SQL Server 2005 and getting these two
results, which I don't understand:

SSIS Roles --  No permissions to access database.
 This check determines if the BuiltIn Admin is part of db_DTSAdmin,
db_DTSltduser or db_dtsoperator roles.

Sysdtslog -- No permissions to access database.
 This check determines if the Sysdtslog90 table exists in the Master and
MSDB databases.

Clicking "How to correct this" just returns a generic "How to Correct Common
Errors" link.

My first question is, does "No permissions to access database" mean:
1. Everyone can access the database because there are no permissions
2. No none can access the database because there are no permissions

I would think that based on "Secure By Default" that it should be #1.

The next question is: Since SSIS isn't installed, why does it care about the
roles?

My third question is, "How do I fix whatever MBSA is flagging?"


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message, you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2009 Google