Failed to notify 'Operator' via email

32-bit SQL 2005 sp2 jobs recieve this error when trying to send an email to an Operator. Database Mail is setup and is working for all SSIS jobs where the email is sent through code or Send email task but simply trying to notify on job completion will not work even though the Agent is running & configured to use Database Mail profile with proper permissions.

Make sure sql agent configured properly and restart sql agent after mail configuration and test the mail from agent..

Make sure operator email is correct...and check if there are any other errors in mail log.

|||Enable DatabaseMail on the SQL Server Agent -> properties -> Alert System (check the checkbox), and then restart SQL Server Agent.

Failed to notify 'DBA' via email

We have some SQL jobs those run on a schedule basis. These jobs are setup to
notify us via email in case of job fails. However, Some time we get this
error "Failed to notify 'DBA' via email." Initially I thought it may be b/c
of mail server was not available but our exchnage server admin has looked at
exchange logs and not found any thing at that time. I also looked at the SQL
server logs and did not find any issues. My question is: is there any thing
can go wrong in the SQL server that can cause this probelm?
Help is appreciated.
Thanks,
MohMoh,
FWIW - SQL Server MAPI will only wait a certain amount of time to deliver a
message. If it cannot get out, then the mail will 'fail' even though
Exchange is up and running and healthy. It might be Exchange, networking,
domain issues, etc. that cause the problem.
If you Google on "sql mail Failed to notify" you will see a few comments on
this, without any real help that I could find.
(Unless xp_smtp_sendmail would work for you.)
RLF
"Moh Abb" <mabbas@.aligntech.com> wrote in message
news:eiv3swh3EHA.3376@.TK2MSFTNGP12.phx.gbl...
> We have some SQL jobs those run on a schedule basis. These jobs are setup
to
> notify us via email in case of job fails. However, Some time we get this
> error "Failed to notify 'DBA' via email." Initially I thought it may be
b/c
> of mail server was not available but our exchnage server admin has looked
at
> exchange logs and not found any thing at that time. I also looked at the
SQL
> server logs and did not find any issues. My question is: is there any
thing
> can go wrong in the SQL server that can cause this probelm?
> Help is appreciated.
> Thanks,
> Moh
>|||"Russell Fields" <RussellFields@.NoMailPlease.Com> wrote in message
news:ePA64pj3EHA.2600@.TK2MSFTNGP09.phx.gbl...
> Moh,
> FWIW - SQL Server MAPI will only wait a certain amount of time to deliver
a
> message. If it cannot get out, then the mail will 'fail' even though
> Exchange is up and running and healthy. It might be Exchange, networking,
> domain issues, etc. that cause the problem.
> If you Google on "sql mail Failed to notify" you will see a few comments
on
> this, without any real help that I could find.
Generally I find if you don't absolutely need to use Exchange, setup a local
SMTP server right on teh SQL box and send email through that directly.
Eliminates timeouts, etc.
> (Unless xp_smtp_sendmail would work for you.)
> RLF
> "Moh Abb" <mabbas@.aligntech.com> wrote in message
> news:eiv3swh3EHA.3376@.TK2MSFTNGP12.phx.gbl...
> > We have some SQL jobs those run on a schedule basis. These jobs are
setup
> to
> > notify us via email in case of job fails. However, Some time we get this
> > error "Failed to notify 'DBA' via email." Initially I thought it may be
> b/c
> > of mail server was not available but our exchnage server admin has
looked
> at
> > exchange logs and not found any thing at that time. I also looked at the
> SQL
> > server logs and did not find any issues. My question is: is there any
> thing
> > can go wrong in the SQL server that can cause this probelm?
> >
> > Help is appreciated.
> >
> > Thanks,
> > Moh
> >
> >
>
>

Failed to Net Send to the address '%s'

Can you please post your code.
Peter

>--Original Message--
>i'm trying to setup operators on one of our SQL Server.
>On the server locally i can open a command window, and
enter
>and it works.
>But SQL Server agent says, when i test send the
message, "Failed to Net Send
>to the address '%s'"
>Agent is logging on with a valid domain account.
>
>.
>
Start->Programs->Microsoft SQL Server->Enterprise Manager
Expand your server.
Managment->SQL Server Agent->Operators
Double click an operator
Net send address: Type in a user name or machine name
Click "Test"
"Peter the Spate" <anonymous@.discussions.microsoft.com> wrote in message
news:68cb01c4756f$b3a19fb0$a501280a@.phx.gbl...[vbcol=seagreen]
> Can you please post your code.
> Peter
>
> enter
> message, "Failed to Net Send
sql

Failed to Net Send to the address '%s'

i'm trying to setup operators on one of our SQL Server.
On the server locally i can open a command window, and enter
>net send TargetMachine message
and it works.
But SQL Server agent says, when i test send the message, "Failed to Net Send
to the address '%s'"
Agent is logging on with a valid domain account.Can you please post your code.
Peter
>--Original Message--
>i'm trying to setup operators on one of our SQL Server.
>On the server locally i can open a command window, and
enter
>>net send TargetMachine message
>and it works.
>But SQL Server agent says, when i test send the
message, "Failed to Net Send
>to the address '%s'"
>Agent is logging on with a valid domain account.
>
>.
>|||Start->Programs->Microsoft SQL Server->Enterprise Manager
Expand your server.
Managment->SQL Server Agent->Operators
Double click an operator
Net send address: Type in a user name or machine name
Click "Test"
"Peter the Spate" <anonymous@.discussions.microsoft.com> wrote in message
news:68cb01c4756f$b3a19fb0$a501280a@.phx.gbl...
> Can you please post your code.
> Peter
>
> >--Original Message--
> >i'm trying to setup operators on one of our SQL Server.
> >
> >On the server locally i can open a command window, and
> enter
> >>net send TargetMachine message
> >
> >and it works.
> >
> >But SQL Server agent says, when i test send the
> message, "Failed to Net Send
> >to the address '%s'"
> >
> >Agent is logging on with a valid domain account.
> >
> >
> >.
> >

Failed to Net Send to the address '%s'

Can you please post your code.
Peter

>--Original Message--
>i'm trying to setup operators on one of our SQL Server.
>On the server locally i can open a command window, and
enter
>and it works.
>But SQL Server agent says, when i test send the
message, "Failed to Net Send
>to the address '%s'"
>Agent is logging on with a valid domain account.
>
>.
>Start->Programs->Microsoft SQL Server->Enterprise Manager
Expand your server.
Managment->SQL Server Agent->Operators
Double click an operator
Net send address: Type in a user name or machine name
Click "Test"
"Peter the Spate" <anonymous@.discussions.microsoft.com> wrote in message
news:68cb01c4756f$b3a19fb0$a501280a@.phx.gbl...[vbcol=seagreen]
> Can you please post your code.
> Peter
>
> enter
> message, "Failed to Net Send

Failed to install MSDE 2000a

I have been tring to install the MSDE 200Aon my marchine that is using
the command prompt.
this is the command that i was using:
(setup INSTANCENAME="SA" SECURITYMODE=SQL SAPWD="SqlAdmin1"
TARGETDIR="C:\" )
but it gave me the following error message;
(Go to the control panel to install and configure system components)
now i really dont know what to do from here can you advice me?
hi Tino,
Tino wrote:
> I have been tring to install the MSDE 200Aon my marchine that is using
> the command prompt.
> this is the command that i was using:
> (setup INSTANCENAME="SA" SECURITYMODE=SQL SAPWD="SqlAdmin1"
> TARGETDIR="C:\" )
> but it gave me the following error message;
> (Go to the control panel to install and configure system components)
> now i really dont know what to do from here can you advice me?
did you navigate and posittioned your command prompt window in the folder
hosting the setup.exe boostrap installer of MSDE?
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.bizhttp://italy.mvps.org
DbaMgr2k ver 0.20.0 - DbaMgr ver 0.64.0 and further SQL Tools
-- remove DMO to reply
sql

Failed to convert parameter value from a String to a Guid?

Hi all,

I have setup my database that have 3 columns:

1. Primary Key

2. UserId (UniqueIdentifier, Guid I guess) - I set it up so I can insert the value from the Membership table (UserId) for some relationship.

3. Another Foreign key with just an int.

I tried to build a DAL, ran a test and received this error: "Failed to convert parameter value from a String to a Guid." Before I setup my UserId to be UniqueIdentifier and let it be just an Int, I don't have any problem retrieving data. Here is the SELECT query that I built with the DataSet:

SELECT aspnet_Users.UserId, t_music.MUSIC_TITLE
FROM t_user_viewed
JOIN aspnet_Users ON aspnet_Users.UserId = t_user_viewed.UserId
JOIN t_music ON t_music.MUSIC_PK = t_user_viewed.MUSIC_PK_FK
WHERE aspnet_Users.UserId = @.UserId

Any help would be greatly appreciated,

Kenny.

You need to post definition for @.UserId parameter.

|||

Can you please elaborates? I'm new to asp.net as well as ms-sql.

Thank you,

Kenny.

|||

Sounds like you need to cast the string value to GUID on the @.UserId when you call the select function and pass the @.UserId value.

ctype(StringValueGUID, GUID)

Burl

|||

Where do I cast the string value? In the DAL (dataset) or where I have my ObjectDataSource doing the select? Sorry for my lack of knowledge on asp.net and mssql.

Thanks,

Kenny.

|||

How are you passing the GUID to the ObjectDataSource for the select? Wherever that value comes from, its in a string type and needs to be cast as a GUID type. Can you post some code?

Burl

|||

I've created a Dataset and setup my table, then I've created a BLL that have this code to get the fields:

[System.ComponentModel.DataObjectMethodAttribute(System.ComponentModel.DataObjectMethodType.Select, false)]
public NotesNhac.t_user_viewedDataTable GetSongsByUserPK(Guid UserId)
{
return Adapter2.GetSongsByUserPK(UserId);
}

In my ObjectDataSource, I chose the above method (GetSongsByUserPK) and have the parameter source as a session. Here is the code for the ObjectDataSource:

<asp:ObjectDataSource ID="ObjectDataSource1" runat="server" SelectMethod="GetSongsByUserPK"
TypeName="SongsBBL">
<SelectParameters>
<asp:SessionParameter Name="UserId" SessionField="UserId" Type="Object" />
</SelectParameters>
</asp:ObjectDataSource>

The SELECT query is the same as my first post... is there anything else I need to do?

Thank you very, very much.

Kenny.

|||

Well,

I've made some minor adjustment to my code and it's working now, however, the SELECT statement that I wrote in the DataSet didn't return the proper table. Here are the changes:

1. In my DataSet, I have setup the table called t_user_viewed that will store the primary key of t_music database as foreign key, and the UserId from the aspet_users as another foreign key. Here is the select statement:

SELECT *
FROM t_music a
JOIN t_user_viewed b on a.MUSIC_PK = b.MUSIC_PK_FK
JOIN aspnet_Users c ON b.UserID = c.UserId
WHERE b.UserID = @.UserId

So when I run this code, and enter the UserId, it should return the information from table "t_music" (with all information such as song title, artist, etc...) instead.

2. This is the code for the SongsBLL.cs class, to get the above select statement:

private t_user_viewedTableAdapter _t_user_viewed = null;

protected t_user_viewedTableAdapter Adapter2
{
get
{
if (_t_user_viewed == null)
_t_user_viewed = new t_user_viewedTableAdapter();

return _t_user_viewed;
}
}

[System.ComponentModel.DataObjectMethodAttribute(System.ComponentModel.DataObjectMethodType.Select, false)]
public NotesNhac.t_user_viewedDataTable GetSongsByUserPK(Guid UserId)
{
return Adapter2.GetSongsByUserPK(UserId);
}

3. Here is the ObjectDataSource that was generated by VS:

<asp:ObjectDataSource ID="ObjectDataSource1" runat="server" SelectMethod="GetSongsByUserPK"
TypeName="SongsBBL" OldValuesParameterFormatString="original_{0}">
<SelectParameters>
<asp:SessionParameter Name="UserId" SessionField="UserId" Type="Object" />
</SelectParameters>
</asp:ObjectDataSource>

4. Here is the GridView that was generated automatically when I select the DataSourceID to the above ObjectDataSource:

<asp:GridView ID="GridView1" runat="server" AutoGenerateColumns="False" DataKeyNames="VIEWED_PK"
DataSourceID="ObjectDataSource1">
<Columns>
<asp:BoundField DataField="VIEWED_PK" HeaderText="VIEWED_PK" InsertVisible="False"
ReadOnly="True" SortExpression="VIEWED_PK" />
<asp:BoundField DataField="MUSIC_PK_FK" HeaderText="MUSIC_PK_FK" SortExpression="MUSIC_PK_FK" />
<asp:BoundField DataField="UserID" HeaderText="UserID" SortExpression="UserID" />
</Columns>
</asp:GridView>

Apparently, the GridView & the ObjectDataSource only pick up the t_music_viewed table columns, instead of the "t_music" columns that I specified in my Select statement.

Any idea?

Thank you very much,

Kenny.

|||

I've solved it by building my SELECT query in the "t_music" table instead.

THANK YOU!

Kenny.

|||

I've solved it by building my SELECT query in the "t_music" table instead.

THANK YOU!

Kenny.

sql

Failed integrity check

The accounting system we support runs on SQL 2000. We have setup a SQL Job that checks the integrity of a each accounting database each evening. After running successufully for a few weeks the job started retuning a failed message. I checked the job log and the reason for the failure was because one of the databases couldn't be set to single user mode. When I first saw this I figured OK someone forgot to logout before leaving for the night. When discussing this with the accounting staff, they swear this couldn't be the case with this particular database since only 1 person accesses it and then only rarley, and he says he hasn't been in for days. The amount of activity in this database is minimal
The server was cycled and eveything ran fine for about 3 weeks. Then the same thing happned again over a span of a few nights consecutive. The are no overnight business processes. There are database backups that are scheduled in the evening, including one for this particualr database. Nothing is showing in the active processes during the day to this database, i.e. no run away processes. Any ideas on what is causing the SQL Server to think there is a open connection to this database?
Thanks much for any ideas!If these jobs are set up through maintenance plans, remove
the option for Attempt to repair any minor problems.
You really don't want this to run automatically anyway. If
you have problems with DBCCs, you should be investigating
the cause first before taking any action.
-Sue
On Sat, 18 Oct 2003 12:41:04 -0700, "DL"
<anonymous@.discussions.microsoft.com> wrote:
>The accounting system we support runs on SQL 2000. We have setup a SQL Job that checks the integrity of a each accounting database each evening. After running successufully for a few weeks the job started retuning a failed message. I checked the job log and the reason for the failure was because one of the databases couldn't be set to single user mode. When I first saw this I figured OK someone forgot to logout before leaving for the night. When discussing this with the accounting staff, they swear this couldn't be the case with this particular database since only 1 person accesses it and then only rarley, and he says he hasn't been in for days. The amount of activity in this database is minimal
>The server was cycled and eveything ran fine for about 3 weeks. Then the same thing happned again over a span of a few nights consecutive. The are no overnight business processes. There are database backups that are scheduled in the evening, including one for this particualr database. Nothing is showing in the active processes during the day to this database, i.e. no run away processes. Any ideas on what is causing the SQL Server to think there is a open connection to this database?
>Thanks much for any ideas!

Failed installation to cluster

I have a 2 node cluster on which I am trying to install a
virtual SQL Server.
I am able to complete the setup process, but the
installation fails after checking the cluster resources.
In the application log I see that the ports have
automatically been disabled (as I'm installing SQL from a
CD without sp3a as yet) and the errors that follow show
that connections to the SQL Server were unable to be made.
Is there a switch for the install to stop the disabling of
ports? Has anyone else seen this issue?
Any help would be very much appreciated.
Kind regards,
Simon
Here is the workaround you need.
PRB: Installation of a Named Instance of SQL Server 2000 Virtual Server on a
Windows 2003-Based Cluster Fails
http://support.microsoft.com/default...&Product=sql2k
Once you install SP3a you can remove the alias.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Simon Call" <Simon@.eduserv.org.uk> wrote in message
news:138901c4265c$191f39a0$a101280a@.phx.gbl...
> I have a 2 node cluster on which I am trying to install a
> virtual SQL Server.
> I am able to complete the setup process, but the
> installation fails after checking the cluster resources.
> In the application log I see that the ports have
> automatically been disabled (as I'm installing SQL from a
> CD without sp3a as yet) and the errors that follow show
> that connections to the SQL Server were unable to be made.
> Is there a switch for the install to stop the disabling of
> ports? Has anyone else seen this issue?
> Any help would be very much appreciated.
> Kind regards,
> Simon
|||Geoff,
Many thanks for this.
Kind regards,
Simon

>--Original Message--
>Here is the workaround you need.
>PRB: Installation of a Named Instance of SQL Server 2000
Virtual Server on a
>Windows 2003-Based Cluster Fails
>http://support.microsoft.com/default.aspx?scid=kb;en-
us;815431&Product=sql2k[vbcol=seagreen]
>Once you install SP3a you can remove the alias.
>--
>Geoff N. Hiten
>Microsoft SQL Server MVP
>Senior Database Administrator
>Careerbuilder.com
>I support the Professional Association for SQL Server
>www.sqlpass.org
>"Simon Call" <Simon@.eduserv.org.uk> wrote in message
>news:138901c4265c$191f39a0$a101280a@.phx.gbl...
a[vbcol=seagreen]
a[vbcol=seagreen]
made.[vbcol=seagreen]
of
>
>.
>
|||You probably noticed this but you cannot disable named pipes if you want to
install on Windows 2003, because setup needs named pipes to work.
Rand
This posting is provided "as is" with no warranties and confers no rights.

Failed Connected to Sql 2005 Enterprise Edition

Hi,

We have a Sql 2005 server. It was setup by out network administrators who do not know much about sql server. It's running on Mixed Mode (Sql Server & Windows Authentication Mode). I have been able to connect to it use Integrated Security. However, I have not been able to connect to it using an username and a password. I have tried with sql accounts and windows accounts. Out of frustration, I used sql administrator account and windows domain administrator accounts. I also tried using the account the sql server is running on. But each and every time, I failed and received the following error message:

Login failed for user '<<User Name>>'. The user is not associated with a trusted SQL Server connection.

I have also changed my connection string many times, but it doesn't matter. And I have been able to connect to our Sql 2000 servers successfully.

Please help!!

Pak

The error message indicates that you are only using WIndows authentication. After switching to Mixed Auth., did you restart the service ? do have eventually have multiple instances on the machine and you are connecting to the wrong database ?

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de|||

its looks like still in Windows Authentication. Check that first. ALso if it is a named instance of sql server 2005 you need to start SQL browser Server or Mention the Port in connection string

Check this.

http://madhuottapalam.blogspot.com/2007/01/sql-browser-service-in-sql-2005.html

|||

Jens and Madhu:

Thanks for your help. You are 100% correct. It turned out that one of our developers change the authentication mode to mix mode without restarting SQL server.

Pak

Fail to setup sql 2000 on win standard 2003

I can not install SQl 2000 on my new win 2003 server.
It says: setup failed to configure the server.
What should I do?

This is my Sqlstp.log file

01:51:11 Begin Setup
01:51:11 8.00.194
01:51:11 Mode = Normal
01:51:11 ModeType = NORMAL
01:51:11 GetDefinitionEx returned: 0, Extended: 0x0
01:51:11 ValueFTS returned: 1
01:51:11 ValuePID returned: 1
01:51:11 ValueLic returned: 1
01:51:11 System: Windows NT Terminal Server
01:51:11 SQL Server ProductType: Standard Edition [0x2]
01:51:11 Begin Action: SetupInitialize
01:51:11 End Action SetupInitialize
01:51:11 Begin Action: SetupInstall
01:51:11 Reading Software\Microsoft\Windows\CurrentVersion\CommonFi

lesDir ...
01:51:11 CommonFilesDir=C:\Program Files\Common Files
01:51:11 Windows Directory=C:\WINDOWS\
01:51:11 Program Files=C:\Program Files\
01:51:11 TEMPDIR=C:\WINDOWS\TEMP\
01:51:11 Begin Action: SetupInstall
01:51:11 digpid size : 256
01:51:11 digpid size : 164
01:51:11 Begin Action: CheckFixedRequirements
01:51:11 Platform ID: 0xf00
01:51:11 Version: 5.2.3790
01:51:11 File Version - C:\WINDOWS\system32\shdocvw.dll: 6.0.3790.94
01:51:11 End Action: CheckFixedRequirements
01:51:11 Begin Action: ShowDialogs
01:51:11 Initial Dialog Mask: 0x183000f7, Disable Back=0x1
01:51:11 Begin Action ShowDialogsHlpr: 0x1
01:51:11 Begin Action: DialogShowSdWelcome
01:51:12 End Action DialogShowSdWelcome
01:51:12 Dialog 0x1 returned: 1
01:51:12 End Action ShowDialogsHlpr
01:51:12 ShowDialogsGetDialog returned: nCurrent=0x2,index=1
01:51:12 Begin Action ShowDialogsHlpr: 0x2
01:51:12 Begin Action: DialogShowSdMachineName
01:51:14 ShowDlgMachine returned: 1
01:51:14 Name = ETOUCHHOST, Type = 0x1
01:51:14 Begin Action: CheckRequirements
01:51:14 Processor Architecture: x86 (Pentium)
01:51:14 ComputerName: ETOUCHHOST
01:51:14 User Name: Administrator
01:51:14 IsAllAccessAllowed returned: 1
01:51:14 OS Language: 0xc09
01:51:14 End Action CheckRequirements
01:51:14 This combination of Package and Operating System allows a full product install.
01:51:14 CreateSetupTopology(ETOUCHHOST), Handle : 0x1134168, returned : 0
01:51:14 CreateSetupTopology returned : 0, Handle : 0x1134168
01:51:14 Topology Type : 1, Return Value : 0
01:51:14 ST_GetPhysicalNode returned : 0, PNHandle : 0x11341b8
01:51:14 PN_EnumerateEx returned : 0
01:51:14 PN_GetSQLStates returned : 0, SqlStates : 0x0
01:51:14 PN_StartScan [0x11341b8] returned : 0
01:51:14 PN_GetNext [0x11341b8] returned : 18, Handle: [0x0]
01:51:14 No more items in enumeration.
01:51:14 ReleaseSetupTopology
01:51:14 Named instance limit: 100, quota: 0
01:51:14 End Action DialogShowSdMachineName
01:51:14 begin ShowDialogsUpdateMask
01:51:14 nFullMask = 0x183000f7, nCurrent = 0x2, nDirection = 0
01:51:14 Updated Dialog Mask: 0xbf00037, Disable Back = 0x1
01:51:14 Dialog 0x2 returned: 0
01:51:14 End Action ShowDialogsHlpr
01:51:14 ShowDialogsGetDialog returned: nCurrent=0x4,index=2
01:51:14 Begin Action ShowDialogsHlpr: 0x4
01:51:14 Begin Action: DialogShowSdInstallMode
01:51:15 ShowDlgInstallMode returned: 1
01:51:15 InstallMode : 0x1
01:51:15 End Action DialogShowSdInstallMode
01:51:15 begin ShowDialogsUpdateMask
01:51:15 nFullMask = 0xbf00037, nCurrent = 0x4, nDirection = 1
01:51:15 Updated Dialog Mask: 0x1bf40037, Disable Back = 0x1
01:51:15 Dialog 0x4 returned: 1
01:51:15 End Action ShowDialogsHlpr
01:51:15 ShowDialogsGetDialog returned: nCurrent=0x10,index=4
01:51:15 Begin Action ShowDialogsHlpr: 0x10
01:51:15 Begin Action: DialogShowSdRegisterUserEx
01:51:24 End Action DialogShowSdRegisterUserEx
01:51:24 Dialog 0x10 returned: 1
01:51:24 End Action ShowDialogsHlpr
01:51:24 ShowDialogsGetDialog returned: nCurrent=0x20,index=5
01:51:24 Begin Action ShowDialogsHlpr: 0x20
01:51:24 Begin Action: DialogShowSdLicense
01:51:27 End Action DialogShowSdLicense
01:51:27 Dialog 0x20 returned: 1
01:51:27 End Action ShowDialogsHlpr
01:51:27 ShowDialogsGetDialog returned: nCurrent=0x40000,index=18
01:51:27 Begin Action ShowDialogsHlpr: 0x40000
01:51:27 Begin Action: DialogShowSdCliSvr
01:51:27 DisplaySystemPreReq
01:51:28 ShowDlgClientServerSelect returned: 1
01:51:28 Type : 0x2
01:51:28 End Action DialogShowSdCliSvr
01:51:28 begin ShowDialogsUpdateMask
01:51:28 nFullMask = 0x1bf40037, nCurrent = 0x40000, nDirection = 1
01:51:28 Updated Dialog Mask: 0x1bfc0037, Disable Back = 0x1
01:51:28 Dialog 0x40000 returned: 1
01:51:28 End Action ShowDialogsHlpr
01:51:28 ShowDialogsGetDialog returned: nCurrent=0x80000,index=19
01:51:28 Begin Action ShowDialogsHlpr: 0x80000
01:51:28 Begin Action: DialogShowSdInstanceName
01:51:28 Begin Action: ShowDlgInstanceName
01:51:29 End Action: ShowDlgInstanceName
01:51:29 ShowDlgInstanceName returned : 1
01:51:29 InstanceName : MSSQLSERVER
01:51:29 CreateSetupTopology(ETOUCHHOST), Handle : 0x1134730, returned : 0
01:51:29 CreateSetupTopology returned : 0, Handle : 0x1134730
01:51:29 Topology Type : 1, Return Value : 0
01:51:29 ST_GetPhysicalNode returned : 0, PNHandle : 0x11341b8
01:51:29 PN_EnumerateEx returned : 0
01:51:29 PN_GetSQLStates returned : 0, SqlStates : 0x0
01:51:29 PN_StartScan [0x11341b8] returned : 0
01:51:29 PN_GetNext [0x11341b8] returned : 18, Handle: [0x0]
01:51:29 No more items in enumeration.
01:51:29 ReleaseSetupTopology
01:51:29 End Action DialogShowSdInstanceName
01:51:29 begin ShowDialogsUpdateMask
01:51:29 nFullMask = 0x1bfc0037, nCurrent = 0x80000, nDirection = 1
01:51:29 Updated Dialog Mask: 0x1bfc0037, Disable Back = 0x1
01:51:29 Dialog 0x80000 returned: 1
01:51:29 End Action ShowDialogsHlpr
01:51:29 ShowDialogsGetDialog returned: nCurrent=0x100000,index=20
01:51:29 Begin Action ShowDialogsHlpr: 0x100000
01:51:29 Begin Action: DialogShowSdSetupType
01:51:29 Begin Action: Setup Type
01:51:31 SQL program folder: C:\Program Files\Microsoft SQL Server
01:51:31 SQL data folder: C:\Program Files\Microsoft SQL Server
01:51:31 Windows system folder: C:\WINDOWS\system32\
01:51:31 Prog req: 38205, Data req: 34432, Sys req: 182917
01:51:31 Prog avail: 73899760, Data avail: 73899760, Sys avail: 73899760
01:51:31 Prog req vs. avail, 255554, 73899760
01:51:31 Data req vs. avail, 34432, 73899760
01:51:31 Sys req vs. avail, 217349, 73899760
01:51:31 DisplaySystemPreReq
01:51:31 [SetupTypeSQL]
01:51:31 szDir = C:\Program Files\Microsoft SQL Server
01:51:31 szDir = %PROGRAMFILES%\Microsoft SQL Server
01:51:31 Result = 301
01:51:31 szDataDir = C:\Program Files\Microsoft SQL Server
01:51:31 szDataDir = %PROGRAMFILES%\Microsoft SQL Server
01:51:31 End Action: Setup Type
01:51:31 Setup Type: Typical (301)
01:51:31 End Action DialogShowSdSetupType
01:51:31 begin ShowDialogsUpdateMask
01:51:31 nFullMask = 0x1bfc0037, nCurrent = 0x100000, nDirection = 301
01:51:31 Updated Dialog Mask: 0x1bdc0037, Disable Back = 0x1
01:51:31 Dialog 0x100000 returned: 301
01:51:31 End Action ShowDialogsHlpr
01:51:31 ShowDialogsGetDialog returned: nCurrent=0x400000,index=22
01:51:31 Begin Action ShowDialogsHlpr: 0x400000
01:51:31 Begin Action: DlgServices
01:51:36 ShowDlgServices returned: 1
01:51:36 [DlgServices]
01:51:36 Local-Domain = 3855
01:51:36 AutoStart = 15
01:51:36 Result = 1
01:51:36 End Action DlgServices
01:51:36 begin ShowDialogsUpdateMask
01:51:36 nFullMask = 0x1bdc0037, nCurrent = 0x400000, nDirection = 1
01:51:36 Updated Dialog Mask: 0x1bdc0037, Disable Back = 0x1
01:51:36 Dialog 0x400000 returned: 1
01:51:36 End Action ShowDialogsHlpr
01:51:36 ShowDialogsGetDialog returned: nCurrent=0x800000,index=23
01:51:36 Begin Action ShowDialogsHlpr: 0x800000
01:51:36 Begin Action: DlgSQLSecurity
01:51:38 ShowDlgSQLSecurity returned: 1
01:51:38 LoginMode = 1,szPwd
01:51:38 End Action DlgSQLSecurity
01:51:38 begin ShowDialogsUpdateMask
01:51:38 nFullMask = 0x1bdc0037, nCurrent = 0x800000, nDirection = 1
01:51:38 Updated Dialog Mask: 0x1bdc0037, Disable Back = 0x1
01:51:38 Dialog 0x800000 returned: 1
01:51:38 End Action ShowDialogsHlpr
01:51:38 ShowDialogsGetDialog returned:nCurrent=0x1000000,index=24
01:51:38 Begin Action ShowDialogsHlpr: 0x1000000
01:51:38 Begin Action: DlgCollation
01:51:38 ShowDlgCollation returned: 1
01:51:38 collation_name = Latin1_General_CI_AS,locale_name = Latin1_General,lcid = 0xc09,SortId = 0,dwCompFlags = 0x30001
01:51:38 End Action DlgCollation
01:51:38 begin ShowDialogsUpdateMask
01:51:38 nFullMask = 0x1bdc0037, nCurrent = 0x1000000, nDirection = 1
01:51:38 Updated Dialog Mask: 0x1bdc0037, Disable Back = 0x1
01:51:38 Dialog 0x1000000 returned: 1
01:51:38 End Action ShowDialogsHlpr
01:51:38 ShowDialogsGetDialog returned: nCurrent=0x2000000,index=25
01:51:38 Begin Action ShowDialogsHlpr: 0x2000000
01:51:38 Begin Action: DlgNetwork
01:51:38 ShowDlgNetwork returned: 1
01:51:38 [DlgServerNetwork]
01:51:38 NetworkLibs = 255
01:51:38 TCPPort = 1433
01:51:38 TCPPrxy = Default
01:51:38 NMPPipeName = \\.\pipe\sql\query
01:51:38 Result = 1
01:51:38 End Action DlgNetwork
01:51:38 begin ShowDialogsUpdateMask
01:51:38 nFullMask = 0x1bdc0037, nCurrent = 0x2000000, nDirection = 1
01:51:38 Updated Dialog Mask: 0x1bdc0037, Disable Back = 0x1
01:51:38 Dialog 0x2000000 returned: 1
01:51:38 End Action ShowDialogsHlpr
01:51:38 ShowDialogsGetDialog returned: nCurrent=0x8000000,index=27
01:51:38 Begin Action ShowDialogsHlpr: 0x8000000
01:51:38 Begin Action: DialogShowSdStartCopy
01:51:38 End Action DialogShowSdStartCopy
01:51:38 begin ShowDialogsUpdateMask
01:51:38 nFullMask = 0x1bdc0037, nCurrent = 0x8000000, nDirection = 1
01:51:38 Updated Dialog Mask: 0x1bdc0037, Disable Back = 0x1
01:51:38 Dialog 0x8000000 returned: 1
01:51:38 End Action ShowDialogsHlpr
01:51:38 ShowDialogsGetDialog returned: nCurrent=0x10000000,index=28
01:51:38 Begin Action ShowDialogsHlpr: 0x10000000
01:51:38 Begin Action: DialogShowSdLicenseMode
01:51:40 ShowDlgLicense returned: 1
01:51:40 ShowDlgLicense returned: LicenseMode = 0, LicenseLimit = 5
01:51:40 End Action DialogShowSdLicenseMode
01:51:40 Dialog 0x10000000 returned: 1
01:51:40 End Action ShowDialogsHlpr
01:51:40 ShowDialogsGetDialog returned: nCurrent=0x0,index=0
01:51:40 End Action ShowDialogs
01:51:40 Begin Action ProcessBeforeDataMove:
01:51:40 DeinstallStart returned (C:\Program Files\Microsoft SQL Server\MSSQL): 0
01:51:40 End Action ProcessBeforeDataMove:
01:51:40 Begin Action SetToolsComponentSelection:
01:51:40 End Action SetToolsComponentSelection:
01:51:40 Begin Action ProcessComponentSelection:
01:51:40 End Action ProcessComponentSelection
01:51:40 Begin Action LogSelectedComponents:
01:51:40 SQLProg
01:51:40 SQLProg\SQLServr
01:51:40 SQLProg\SQLServr\Help
01:51:40 SQLProg\SQLServr\SCMDev
01:51:40 SQLProg\SQLServr\SCMDev\SCMh
01:51:40 SQLProg\SQLServr\SCMDev\SCMX86Lb
01:51:40 SQLProg\SQLServr\SCMDev\SCMALb
01:51:40 SQLProg\SQLServr\Rs1033
01:51:40 SQLProg\SQLServr\RsIntl
01:51:40 SQLProg\SQLServr\ActiveX
01:51:40 SQLProg\SQLServr\System
01:51:40 SQLProg\UpgTools
01:51:40 SQLProg\UpgTools\UpgSys
01:51:40 SQLProg\UpgTools\ActiveX
01:51:40 SQLProg\UpgTools\Res1033
01:51:40 SQLProg\UpgTools\ResOther
01:51:40 SQLProg\UpgTools\Resld
01:51:40 SQLProg\ReplSupp
01:51:40 SQLProg\ReplSupp\ReplDat
01:51:40 SQLProg\ReplSupp\RepComm
01:51:40 SQLProg\ReplSupp\RepNoDk
01:51:40 SQLProg\ReplSupp\ActiveX
01:51:40 SQLProg\Install
01:51:40 SQLProg\System
01:51:40 SQLProg\SvrExt
01:51:40 SQLProg\SvrExt\Help
01:51:40 SQLProg\SvrExt\SvrExtRs
01:51:40 SQLProg\SvrExt\ResIntl
01:51:40 SQLProg\Dat
01:51:40 SQLProg\DatSmpl
01:51:40 SQLProg\BaseSys
01:51:40 SQLProg\BaseBinn
01:51:40 SQLProg\MSSearch
01:51:40 SQLProg\MSSearch\Help
01:51:40 SQLProg\MSSearch\ActiveX
01:51:40 SQLProg\BaseInst
01:51:40 SQLProg\Symbols
01:51:40 SQLProg\Symbols\EXE
01:51:40 SQLProg\Symbols\DLL
01:51:40 SQLProg\Perfmon
01:51:40 SQLProg\Perfmon\System
01:51:40 SQLProg\Root
01:51:40 MgtTool
01:51:40 MgtTool\SEM
01:51:40 MgtTool\SEM\HTML
01:51:40 MgtTool\SEM\MSD98
01:51:40 MgtTool\SEM\MSD98SYS
01:51:40 MgtTool\SEM\MSD98Res
01:51:40 MgtTool\SEM\MSD98Hlp
01:51:40 MgtTool\SEM\Help
01:51:40 MgtTool\SEM\Res1033
01:51:40 MgtTool\SEM\ResIntl
01:51:40 MgtTool\SEM\MSD98RsI
01:51:40 MgtTool\SEM\ActiveX
01:51:40 MgtTool\SEM\ActiveX\Res1033
01:51:40 MgtTool\SEM\ActiveX\ResIntl
01:51:40 MgtTool\SEM\Scripts
01:51:40 MgtTool\SEM\OLEDB
01:51:40 MgtTool\SEM\OLEDB\Res1033
01:51:40 MgtTool\SEM\OLEDB\ResIntl
01:51:40 MgtTool\Profiler
01:51:40 MgtTool\Profiler\Help
01:51:40 MgtTool\Profiler\Res1033
01:51:40 MgtTool\Profiler\ResIntl
01:51:40 MgtTool\Qryanlz
01:51:40 MgtTool\Qryanlz\Help
01:51:40 MgtTool\Qryanlz\Res1033
01:51:40 MgtTool\Qryanlz\ResIntl
01:51:40 MgtTool\DTCCLi
01:51:40 MgtTool\Wzcnflct
01:51:40 MgtTool\Wzcnflct\WzcnHlp
01:51:40 MgtTool\Wzcnflct\Wzcn1033
01:51:40 MgtTool\Wzcnflct\WzcnOthr
01:51:40 MgtTool\Wzcnflct\WzcnCmn
01:51:40 MgtTool\UtilSys
01:51:40 MgtTool\UtilBinn
01:51:40 Connect
01:51:40 Connect\ConnSys
01:51:40 Books
01:51:40 Books\Bookso
01:51:40 Books\Bookso\Utils
01:51:40 DevTools
01:51:40 DevTools\Dbg Int
01:51:40 DevTools\Dbg Int\Dbg Int Common
01:51:40 DevTools\Dbg Int\EXE
01:51:40 CoreRepl
01:51:40 CoreRepl\Res1033
01:51:40 CoreRepl\ResIntl
01:51:40 Core
01:51:40 Core\Res1033
01:51:40 Core\ResOther
01:51:40 Repostry
01:51:40 Repostry\RepstSys
01:51:40 Repostry\Res1033
01:51:40 Repostry\ResIntl
01:51:40 CoreMisc
01:51:40 CoreMisc\ActiveX
01:51:40 CoreMisc\ActiveX\Res1033
01:51:40 CoreMisc\ActiveX\ResIntl
01:51:40 CoreMisc\Res1033
01:51:40 Monarch
01:51:40 Monarch\Monr1033
01:51:40 Monarch\MonrIntl
01:51:40 Jet
01:51:40 CoreInst
01:51:40 CoreCOM
01:51:40 CoreCOM\Res1033
01:51:40 CoreCOM\ResIntl
01:51:40 CoreTool
01:51:40 CoreTool\Res1033
01:51:40 CoreTool\ResOther
01:51:40 DBLibCli
01:51:40 SFExt
01:51:40 SFExt\ActiveX
01:51:40 SFExt\ActiveX\Res1033
01:51:40 SFExt\ActiveX\ResIntl
01:51:40 SFExt\Res1033
01:51:40 SFExt\ResIntl
01:51:40 Trace
01:51:40 Trace\Res1033
01:51:40 Trace\ResOther
01:51:40 MiscCore
01:51:40 MC
01:51:40 MC\MC1033
01:51:40 MC\MCIntl
01:51:40 MC\Help
01:51:40 SQLMgr
01:51:40 SQLMgr\Res1033
01:51:40 SQLMgr\ResIntl
01:51:40 SvrTool
01:51:40 SvrTool\Res1033
01:51:40 SvrTool\ResIntl
01:51:40 DTSUI
01:51:40 DTSUI\Res1033
01:51:40 DTSUI\ResIntl
01:51:40 MSOlap
01:51:40 MSOlap\Res1033
01:51:40 MSOlap\ResIntl
01:51:40 ATL
01:51:40 ATL\winnt
01:51:40 ATL\win9x
01:51:40 MFC42U
01:51:40 VC
01:51:40 VB
01:51:40 OCX1
01:51:40 SQLAdHlp
01:51:40 SQLAdHlp\Res1033
01:51:40 SQLAdHlp\ResOther
01:51:40 {E07FDDBE-5A21-11d2-9DAD-00C04F79D434}
01:51:40 {E07FDDC7-5A21-11d2-9DAD-00C04F79D434}
01:51:40 {E07FDDC0-5A21-11d2-9DAD-00C04F79D434}
01:51:40 {E07FDDBF-5A21-11d2-9DAD-00C04F79D434}
01:51:40 End Action LogSelectedComponents
01:51:40 Begin Action InstallPkgs:
01:51:40 Begin Action: Locked Connectivity Files Check
01:51:40 ConnectivityLocked returned: 0
01:51:40 The operation completed successfully.

01:51:40 End Action: Locked Connectivity Files Check
01:51:41 Setup is installing Microsoft Data Access Components (MDAC) ...
01:51:41 C:\INETPUB\FTPROOT\x86\Other\sqlredis.exe /q:a /C:"setupre.exe WARN=1 -s -SMS"
01:51:58 ExitCode: 0
01:51:58 Setup is installing Microsoft Distributed Transaction Coordinator (MSDTC) ...
01:51:58 C:\WINDOWS\TEMP\SqlSetup\Bin\cldtcstp.exe -SupportDir "C:\WINDOWS\TEMP\SqlSetup\Bin" -DTCPkg "C:\INETPUB\FTPROOT\x86\Other\dtcsetup.exe" -LogFile "C:\WINDOWS\sqlstp.log"
01:51:58 Process Exit Code: (0)
01:51:58 InstallMSSearch instance: MSSQLSERVER
01:51:58 Software\Microsoft\Search\Install:Version not present
01:51:58 MSSearch 2.0 or greater version check returned -1
01:51:58 Setup is installing the Microsoft Full-Text Search Engine ...
01:51:58 " C:\INETPUB\FTPROOT\x86\FullText\MSSearch\Search\Se

archStp.exe" /s /a:SQLServer
01:52:11 Process Exit Code: (0)
01:52:11 /Q:A /T:C:\WINDOWS\TEMP\ixp001.tmp
01:52:11 Setup is installing HTML Help ...
01:52:11 HTML Help installer exit code: 0
01:52:32 End Action InstallPkgs
01:52:32 Begin Action MoveFileData:
01:52:32 Enabled SELFREGISTERBATCH
01:52:32 Enabled CORECOMPONENTHANDLING
01:52:54 Begin Action: MoveFileDataSpecial|||01:52:55 End Action: MoveFileDataSpecial
01:52:55 End Action MoveFileData
01:52:55 Begin Action ProcessAfterDataMove:
01:52:55 C:\INETPUB\FTPROOT\x86\Binn\hhcol.exe C:\Program Files\Microsoft SQL Server\80\Tools\Books
01:52:55 End Action ProcessAfterDataMove
01:52:55 Begin Action BuildServer:
01:52:55 C:\WINDOWS\TEMP\SqlSetup\Bin\scm.exe -Silent 1 -Action 5 -ExePath "C:\Program Files\Microsoft SQL Server\MSSQL\binn\sqlservr.exe" -Service "MSSQLSERVER"
01:52:55 Process Exit Code: (0)
01:52:55 Begin Action: CreateRegistrySetSQL
01:52:55 End Action: CreateRegistrySetSQL
01:52:55 Begin Action: RegWriteSetupEntry
01:52:55 End Action: RegWriteSetupEntry
01:52:55 Begin Action: CreateSer
01:52:55 End Action: CreateSer
01:52:55 Begin Action: SkuIt
01:52:55 End Action: SkuIt
01:52:56 SetFileSecuritySQLAndAdmin for C:\Program Files\Microsoft SQL Server\MSSQL returned: 0, 0
01:52:56 SetRegSecuritySQLAndAdmin for Software\Microsoft\MSSQLServer\MSSQLServer returned: 0, 0
01:52:56 Begin Action: UpdateSystemPath
01:52:56 Path successfully updated.
01:52:56 %SystemRoot%\system32;%SystemRoot%;%SystemRoot%\Sy

stem32\Wbem;C:\Program Files\Microsoft SQL Server\80\Tools\BINN
01:52:56 End Action: UpdateSystemPath
01:52:57 C:\Program Files\Microsoft SQL Server\80\Tools\Binn\cnfgsvr.exe -F "C:\WINDOWS\sqlstp.log" -I MSSQLSERVER -V 1 -M 0 -Q "Latin1_General_CI_AS" -H 131390 -U sa -P
01:52:57 Process Exit Code: (193)
01:54:06 Setup failed to configure the server. Refer to the server error logs and C:\WINDOWS\sqlstp.log for more information.
01:54:06 Action CleanUpInstall:
01:54:06 C:\WINDOWS\TEMP\SqlSetup\Bin\scm.exe -Silent 1 -Action 4 -Service SQLSERVERAGENT
01:54:06 Process Exit Code: (1060) The specified service does not exist as an installed service.

01:54:06 C:\WINDOWS\TEMP\SqlSetup\Bin\scm.exe -Silent 1 -Action 4 -Service MSSQLSERVER
01:54:07 Process Exit Code: (0)
01:54:07 StatsGenerate returned: 2
01:54:07 StatsGenerate (0x0,0x1,0xf00,0x0,1033,303,0x0,0x1,0,0,0
01:54:07 StatsGenerate -1,Administrator)
01:54:07 Installation Failed.|||Check the sqlstp.log under c:\winnt. Also look for information in the event logs. I am not sure if these will exist yet, but check for errorlog files under the sql server directory.|||there is no errorlog files under the sql server directory. I already check it. Also the above is my Sqlstp.log file.

I have try so many way to solve the problem, however I can't ...pls help|||How about sqlsp.log and event logs ? Did the log end on "01:52:54 Begin Action: MoveFileDataSpecial" ?|||Its end with 01:54:07 Installation Failed.|||This is another one

06:20:21 Begin Setup
06:20:21 8.00.194
06:20:21 Mode = Normal
06:20:21 ModeType = NORMAL
06:20:21 GetDefinitionEx returned: 0, Extended: 0x0
06:20:21 ValueFTS returned: 1
06:20:21 ValuePID returned: 1
06:20:21 ValueLic returned: 1
06:20:21 System: Windows NT Terminal Server
06:20:21 SQL Server ProductType: Standard Edition [0x2]
06:20:21 Begin Action: SetupInitialize
06:20:21 End Action SetupInitialize
06:20:21 Begin Action: SetupInstall
06:20:21 Reading Software\Microsoft\Windows\CurrentVersion\CommonFi lesDir ...
06:20:21 CommonFilesDir=C:\Program Files\Common Files
06:20:21 Windows Directory=C:\WINDOWS\
06:20:21 Program Files=C:\Program Files\
06:20:21 TEMPDIR=C:\WINDOWS\TEMP\
06:20:21 Begin Action: SetupInstall
06:20:21 digpid size : 256
06:20:21 digpid size : 164
06:20:21 Begin Action: CheckFixedRequirements
06:20:21 Platform ID: 0xf00
06:20:21 Version: 5.2.3790
06:20:21 File Version - C:\WINDOWS\system32\shdocvw.dll: 6.0.3790.94
06:20:21 End Action: CheckFixedRequirements
06:20:21 Begin Action: ShowDialogs
06:20:21 Initial Dialog Mask: 0x183000f7, Disable Back=0x1
06:20:21 Begin Action ShowDialogsHlpr: 0x1
06:20:21 Begin Action: DialogShowSdWelcome
06:20:23 End Action DialogShowSdWelcome
06:20:23 Dialog 0x1 returned: 1
06:20:23 End Action ShowDialogsHlpr
06:20:23 ShowDialogsGetDialog returned: nCurrent=0x2,index=1
06:20:23 Begin Action ShowDialogsHlpr: 0x2
06:20:23 Begin Action: DialogShowSdMachineName
06:20:29 ShowDlgMachine returned: -1
06:20:29 ShowDlgMachine: GetLastError returned: 0
06:20:29 The operation completed successfully.

06:20:29 End Action DialogShowSdMachineName
06:20:29 End Action ShowDialogs
06:20:29 Action CleanUpInstall:
06:20:29 StatsGenerate returned: 2
06:20:29 StatsGenerate (0x0,0x0,0xf00,0x0,1033,0,0x0,0x0,0,0,0
06:20:29 StatsGenerate -1,)
06:20:29 Installation Failed.|||I missed the 3rd post with the log dump. Anyway, try running the sql setup in debug mode - using \x86\setup\setupsql.exe k=Dbq. When you get to the server configuration portion - see if you can start the sql server service.|||hi,

It doesn't work. samw problem. any more suggestion?|||What happens when you are in debug and the configure server prompts and you attempt to start the sql server service - without proceeding with the configure server (just leave it at the prompt) ?|||it quit automatically after it says setup failed to configure the server

fail to installation of MDAC on SQL Server install

this log message occour when installation of microsoft
SqlServer 2k:
11:25:20 Setup is installing Microsoft Data Access
Components (MDAC) ...
11:25:20 E:\SQL Server 2000\x86
\Other\sqlredis.exe /q:a /C:"setupre.exe WARN=1 -s -SMS"
11:27:23 ExitCode: -1
11:27:37 Installation of the Microsoft Data Access
Components package failed. (-1)
11:27:37 ConnectivityLocked returned: 0
what can i do to repair this problem?
If you update MDAC to the most recent version manually, SQL Server can skip
that step. MDAC 2.8 can be retrieved from:
http://msdn.microsoft.com/data/downl...#MDACDownloads
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"Renato Cabelino" <renatocabelino@.yahoo.com> wrote in message
news:1bdf201c42165$2d0803d0$a301280a@.phx.gbl...
> this log message occour when installation of microsoft
> SqlServer 2k:
> 11:25:20 Setup is installing Microsoft Data Access
> Components (MDAC) ...
> 11:25:20 E:\SQL Server 2000\x86
> \Other\sqlredis.exe /q:a /C:"setupre.exe WARN=1 -s -SMS"
> 11:27:23 ExitCode: -1
> 11:27:37 Installation of the Microsoft Data Access
> Components package failed. (-1)
> 11:27:37 ConnectivityLocked returned: 0
> what can i do to repair this problem?

fail to installation of MDAC on SQL Server install

this log message occour when installation of microsoft
SqlServer 2k:
11:25:20 Setup is installing Microsoft Data Access
Components (MDAC) ...
11:25:20 E:\SQL Server 2000\x86
\Other\sqlredis.exe /q:a /C:"setupre.exe WARN=1 -s -SMS"
11:27:23 ExitCode: -1
11:27:37 Installation of the Microsoft Data Access
Components package failed. (-1)
11:27:37 ConnectivityLocked returned: 0
what can i do to repair this problem?If you update MDAC to the most recent version manually, SQL Server can skip
that step. MDAC 2.8 can be retrieved from:
http://msdn.microsoft.com/data/downloads/updates/default.aspx#MDACDownloads
--
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"Renato Cabelino" <renatocabelino@.yahoo.com> wrote in message
news:1bdf201c42165$2d0803d0$a301280a@.phx.gbl...
> this log message occour when installation of microsoft
> SqlServer 2k:
> 11:25:20 Setup is installing Microsoft Data Access
> Components (MDAC) ...
> 11:25:20 E:\SQL Server 2000\x86
> \Other\sqlredis.exe /q:a /C:"setupre.exe WARN=1 -s -SMS"
> 11:27:23 ExitCode: -1
> 11:27:37 Installation of the Microsoft Data Access
> Components package failed. (-1)
> 11:27:37 ConnectivityLocked returned: 0
> what can i do to repair this problem?

fail to installation of MDAC on SQL Server install

this log message occour when installation of microsoft
SqlServer 2k:
11:25:20 Setup is installing Microsoft Data Access
Components (MDAC) ...
11:25:20 E:\SQL Server 2000\x86
\Other\sqlredis.exe /q:a /C:"setupre.exe WARN=1 -s -SMS"
11:27:23 ExitCode: -1
11:27:37 Installation of the Microsoft Data Access
Components package failed. (-1)
11:27:37 ConnectivityLocked returned: 0
what can i do to repair this problem?If you update MDAC to the most recent version manually, SQL Server can skip
that step. MDAC 2.8 can be retrieved from:
http://msdn.microsoft.com/data/down...x#MDACDownloads
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"Renato Cabelino" <renatocabelino@.yahoo.com> wrote in message
news:1bdf201c42165$2d0803d0$a301280a@.phx
.gbl...
> this log message occour when installation of microsoft
> SqlServer 2k:
> 11:25:20 Setup is installing Microsoft Data Access
> Components (MDAC) ...
> 11:25:20 E:\SQL Server 2000\x86
> \Other\sqlredis.exe /q:a /C:"setupre.exe WARN=1 -s -SMS"
> 11:27:23 ExitCode: -1
> 11:27:37 Installation of the Microsoft Data Access
> Components package failed. (-1)
> 11:27:37 ConnectivityLocked returned: 0
> what can i do to repair this problem?

Fail to hide the restart dialog after installed MSDE

Hi,
I want to hide the restart dialog after installed MSDE. I
use the follow command:
setup /settings "setup.ini" /qb
But, the result fails. The restart dialog is also
prompted. Is my command wrong? How to do it?
Thanks.
Using /qn instead of /qb did the trick for me. Do you only get the restart
dialog, or do you get other dialogs as well? I ran mine without a settings
file, just with all the parameters on the command prompt.
Jacco Schalkwijk
SQL Server MVP
<anonymous@.discussions.microsoft.com> wrote in message
news:1311101c41243$45fd3f30$a501280a@.phx.gbl...
> Hi,
> I want to hide the restart dialog after installed MSDE. I
> use the follow command:
> setup /settings "setup.ini" /qb
> But, the result fails. The restart dialog is also
> prompted. Is my command wrong? How to do it?
> Thanks.
|||A solution I saw on another newsgroup was to include the following switch:
REBOOTPROMPT=Suppress
(I haven't had chance to try it yet)
Posted using Wimdows.net NntpNews Component -
Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine supports Post Alerts, Ratings, and Searching.

Extracting cached reports

Dear Experts,
We have setup reports to cache, everything works fine. :) We want to know
if there is an API to extract cached reports ourselves? How can we do this
and is it possible at all?
Thanks,
Bojan NikicOn Oct 4, 1:07 pm, bojannikic <bojanni...@.discussions.microsoft.com>
wrote:
> Dear Experts,
> We have setup reports to cache, everything works fine. :) We want to know
> if there is an API to extract cached reports ourselves? How can we do this
> and is it possible at all?
> Thanks,
> Bojan Nikic
As far as I know, the majority of this information resides in the
ReportServerTempDB in the ExecutionCache table. Hope this helps.
Regards,
Enrique Martinez
Sr. Software Consultant|||Yes it is there, but how do we extract this information into the report?
Thanks,
Bojan
"EMartinez" wrote:
> On Oct 4, 1:07 pm, bojannikic <bojanni...@.discussions.microsoft.com>
> wrote:
> > Dear Experts,
> >
> > We have setup reports to cache, everything works fine. :) We want to know
> > if there is an API to extract cached reports ourselves? How can we do this
> > and is it possible at all?
> >
> > Thanks,
> > Bojan Nikic
>
> As far as I know, the majority of this information resides in the
> ReportServerTempDB in the ExecutionCache table. Hope this helps.
> Regards,
> Enrique Martinez
> Sr. Software Consultant
>