Microsoft Security Bulletin MS04-014

Vulnerability in the Microsoft Jet Database Engine Could Allow Code
Execution (837001)
Has anyone installed this patch yet? We ran it yesterday and now we can't
seem to manage our MSDE instance via an Access project. It simply says
(disconnected) at the top of the adp window. I've checked the Connection
proerties and everything looks good (the Test Connection) even succeeds.
I've tried with both Windows authentication and SQL Server authentication,
the tests always succeed, but the database remains disconnected. Anybody
else experiencing this problem or have suggestions as what to try?
Installed and Access project still working.
Michael Tissington
http://www.oaklodge.com
http://www.tabtag.com
"Steven Bergman" <sbergman@.newboundary.com> wrote in message
news:OBtP0Q9IEHA.3720@.TK2MSFTNGP11.phx.gbl...
> Vulnerability in the Microsoft Jet Database Engine Could Allow Code
> Execution (837001)
> Has anyone installed this patch yet? We ran it yesterday and now we can't
> seem to manage our MSDE instance via an Access project. It simply says
> (disconnected) at the top of the adp window. I've checked the Connection
> proerties and everything looks good (the Test Connection) even succeeds.
> I've tried with both Windows authentication and SQL Server authentication,
> the tests always succeed, but the database remains disconnected. Anybody
> else experiencing this problem or have suggestions as what to try?
>
|||Thanks. What versions are you using? We are on Access 2002 SP1 and MSDE
8.00.194.
What versions of Access and MSDE are you using?
"Michael Tissington" <michael@.nospam.com> wrote in message
news:OnEWxI%23IEHA.964@.TK2MSFTNGP10.phx.gbl...[vbcol=seagreen]
> Installed and Access project still working.
> --
> Michael Tissington
> http://www.oaklodge.com
> http://www.tabtag.com
> "Steven Bergman" <sbergman@.newboundary.com> wrote in message
> news:OBtP0Q9IEHA.3720@.TK2MSFTNGP11.phx.gbl...
can't[vbcol=seagreen]
Connection[vbcol=seagreen]
authentication,[vbcol=seagreen]
Anybody
>

Microsoft Data Link Error

A test installation script I ran on my dev rig seems to have broken the OLE DB Provider for Sql Server. The uninstall must have deleted a DLL or unregistered a lib. When I try to connect to a SQL database from this machine now get the following error:

==

Microsoft Data Link Error

Test connection failed because of an error in initializing provider. Unspecified error.

==

It is not the connection string because this was working fine prior to me running the test installation script.

Can you give advice on how to repair the SQL Server data provider for WinXP SP2?

I have tried to re-install MDAC 2.8 with no success due SP2 diallowing this. I uninstalled SP2 and re-installed MDAC 2.8 but the problem remains.

I'm all out of ideas, so any help would be appreciated.

Thanks!

Can you explain further how you are getting this error?|||May take help of KBA http://support.microsoft.com/kb/275118 in this case.

Microsoft Baseline Security Analyser 2.1

Hi

I downloaded MBSA and ran it against my SQL 2005 Server. It tells me that I have a severe risk because

'The following databases have public access.Remove the public access if it is not required - tempdb , model , msdb , ReportServer , ReportServerTempDB'

I have checked these databases and each have the Guest User but it is disabled. If I check the database properties the public role has no permissions against the listed databases.

Is this a bug with MBSA? If not how do I remove Public Access?

Hi Ewan, are you using a Xp_cmdshell enabled?

|||

Hi Emanuel

I an not sure what you mean. I have installed the product MBSA on a PC running VISTA business and am scanning the SQL server from this PC. The server operating system is Windows Server 2003 R2

Regards

|||

Hi Emanuel

I have now looked it up and xp_cmdshell is not enabled

Regards

|||

The MBSA given't u more details about this vulnerability message?

|||

Hi Emanuel

No MBSA gives no further information on this message

|||

Ewan, has your sql server a valid internet ip address or any other network vulnerability?

|||I mean, does your sql server is exposed on internet?|||

Hi Emanuel

Only via Reporting Services

|||

I'm suggest you investigate any vulnerability on SSRS like a public access on web service.

see the link below, there is a cool tool to do a verification on any possible network vulnerability.

http://www.gfi.com/lannetscan/?adv=40&loc=3&adclickid=14102298