Running SQL 2000 SP3 & Win Adv 2000
Came in this morning and one of my Merge subsctiptions has the
error....
'Failed to enumerate changes in the filtered articles.'
When I look at the last command, I see...
create table #belong_agent_-1933363311 (tablenick int NOT NULL, rowguid
uniqueidentifier NOT NULL,generation int NULL, lineage varbinary(255)
NULL, colv varbinary(2048) NULL)
Obviously the negative sign in '-1933363311' is the problem.
What caused this? How can I fix it?
Is this the problem?
TIA,
Larry...
That should help
http://support.microsoft.com/?id=814916
Regards,
Kestutis Adomavicius
Consultant
UAB "Baltic Software Solutions"
<lreames@.gmail.com> wrote in message news:1109617247.921045.165880@.z14g2000cwz.googlegr oups.com...
Running SQL 2000 SP3 & Win Adv 2000
Came in this morning and one of my Merge subsctiptions has the
error....
'Failed to enumerate changes in the filtered articles.'
When I look at the last command, I see...
create table #belong_agent_-1933363311 (tablenick int NOT NULL, rowguid
uniqueidentifier NOT NULL,generation int NULL, lineage varbinary(255)
NULL, colv varbinary(2048) NULL)
Obviously the negative sign in '-1933363311' is the problem.
What caused this? How can I fix it?
Is this the problem?
TIA,
Larry...
Showing posts with label win. Show all posts
Showing posts with label win. Show all posts
Friday, March 23, 2012
Wednesday, March 21, 2012
failed to connect to SQL Server's database!
Hi,
I've just installed SQL Server 2005 into Win SBS 2003 R2, everything went
fine and other instances (SHAREPOINT & SBSMONITORING) are working as well.
The only thing and the most important that should be working but not, is
application that uses SQL Server as it's main database. Before this, the
application used SQL Server 2000 and working fine.
Everytime users launch the application, there's this error message: "Error
in DataAccessLayer.DataAccess.CheckUserLogin. Login failed for user 'sa'."
Although I've allowed Windows Authentication & SQL Server authentication in
SQL Server 2005 logins settings, that error message will still appears and
restrict any users to log-in to the application.
That application uses a "DataAccessLayer.config" file that has this
parameters:
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<appSettings>
<add key="UseWebService" value="false"/>
<add key="DAL.DataService.DataService" value="http://companyweb"/>
<add key="DBCnnString" value="Persist Security Info=False;User
ID=sa;Password=;Initial Catalog=INVENTORY;Data Source=192.168.16.2"/>
<add key="server" value="ServerName"/>
<add key="database" value="INVENTORY"/>
<add key="uid" value="sa"/>
<add key="password" value=""/>
</appSettings>
</configuration>
What happened? Have anyone encountered the same symtomps/problem and know
how to work around it?
Please be noted, I attach this "INVENTORY" database into
ServerName\Database; I do not use instances for it.
Thank you, all help is appreciated.
ON the Security tab, change to [SQL Server and Windows Authentication].
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Dhow" <Dhow@.discussions.microsoft.com> wrote in message
news:9114C9D0-F787-41A2-B2A1-9B84FA635F1B@.microsoft.com...
> Hi,
> I've just installed SQL Server 2005 into Win SBS 2003 R2, everything went
> fine and other instances (SHAREPOINT & SBSMONITORING) are working as well.
> The only thing and the most important that should be working but not, is
> application that uses SQL Server as it's main database. Before this, the
> application used SQL Server 2000 and working fine.
> Everytime users launch the application, there's this error message: "Error
> in DataAccessLayer.DataAccess.CheckUserLogin. Login failed for user
> 'sa'."
> Although I've allowed Windows Authentication & SQL Server authentication
> in
> SQL Server 2005 logins settings, that error message will still appears and
> restrict any users to log-in to the application.
> That application uses a "DataAccessLayer.config" file that has this
> parameters:
> <?xml version="1.0" encoding="utf-8"?>
> <configuration>
> <appSettings>
> <add key="UseWebService" value="false"/>
> <add key="DAL.DataService.DataService" value="http://companyweb"/>
> <add key="DBCnnString" value="Persist Security Info=False;User
> ID=sa;Password=;Initial Catalog=INVENTORY;Data Source=192.168.16.2"/>
> <add key="server" value="ServerName"/>
> <add key="database" value="INVENTORY"/>
> <add key="uid" value="sa"/>
> <add key="password" value=""/>
> </appSettings>
> </configuration>
> What happened? Have anyone encountered the same symtomps/problem and know
> how to work around it?
> Please be noted, I attach this "INVENTORY" database into
> ServerName\Database; I do not use instances for it.
> Thank you, all help is appreciated.
|||And did you really install SQL 2005 without a password for the [sa] account?
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Dhow" <Dhow@.discussions.microsoft.com> wrote in message
news:9114C9D0-F787-41A2-B2A1-9B84FA635F1B@.microsoft.com...
> Hi,
> I've just installed SQL Server 2005 into Win SBS 2003 R2, everything went
> fine and other instances (SHAREPOINT & SBSMONITORING) are working as well.
> The only thing and the most important that should be working but not, is
> application that uses SQL Server as it's main database. Before this, the
> application used SQL Server 2000 and working fine.
> Everytime users launch the application, there's this error message: "Error
> in DataAccessLayer.DataAccess.CheckUserLogin. Login failed for user
> 'sa'."
> Although I've allowed Windows Authentication & SQL Server authentication
> in
> SQL Server 2005 logins settings, that error message will still appears and
> restrict any users to log-in to the application.
> That application uses a "DataAccessLayer.config" file that has this
> parameters:
> <?xml version="1.0" encoding="utf-8"?>
> <configuration>
> <appSettings>
> <add key="UseWebService" value="false"/>
> <add key="DAL.DataService.DataService" value="http://companyweb"/>
> <add key="DBCnnString" value="Persist Security Info=False;User
> ID=sa;Password=;Initial Catalog=INVENTORY;Data Source=192.168.16.2"/>
> <add key="server" value="ServerName"/>
> <add key="database" value="INVENTORY"/>
> <add key="uid" value="sa"/>
> <add key="password" value=""/>
> </appSettings>
> </configuration>
> What happened? Have anyone encountered the same symtomps/problem and know
> how to work around it?
> Please be noted, I attach this "INVENTORY" database into
> ServerName\Database; I do not use instances for it.
> Thank you, all help is appreciated.
|||Dhow wrote:
> Hi,
> I've just installed SQL Server 2005 into Win SBS 2003 R2, everything went
> fine and other instances (SHAREPOINT & SBSMONITORING) are working as well.
> The only thing and the most important that should be working but not, is
> application that uses SQL Server as it's main database. Before this, the
> application used SQL Server 2000 and working fine.
> Everytime users launch the application, there's this error message: "Error
> in DataAccessLayer.DataAccess.CheckUserLogin. Login failed for user 'sa'."
> Although I've allowed Windows Authentication & SQL Server authentication in
> SQL Server 2005 logins settings, that error message will still appears and
> restrict any users to log-in to the application.
> That application uses a "DataAccessLayer.config" file that has this
> parameters:
> <?xml version="1.0" encoding="utf-8"?>
> <configuration>
> <appSettings>
> <add key="UseWebService" value="false"/>
> <add key="DAL.DataService.DataService" value="http://companyweb"/>
> <add key="DBCnnString" value="Persist Security Info=False;User
> ID=sa;Password=;Initial Catalog=INVENTORY;Data Source=192.168.16.2"/>
> <add key="server" value="ServerName"/>
> <add key="database" value="INVENTORY"/>
> <add key="uid" value="sa"/>
> <add key="password" value=""/>
> </appSettings>
> </configuration>
> What happened? Have anyone encountered the same symtomps/problem and know
> how to work around it?
> Please be noted, I attach this "INVENTORY" database into
> ServerName\Database; I do not use instances for it.
> Thank you, all help is appreciated.
You are trying to connect to the server using the "sa" login, with no
password!!! You have two problems here:
1. Never, ever, purposely allow an application to connect as "sa", you
need to tightly control the use of this login.
2. If you purposely installed SQL Server with a blank password for
"sa", change it, now. Your server is wide open to anybody who chooses
to login as "sa".
Tracy McKibben
MCDBA
http://www.realsqlguy.com
|||Arnie,
When I installed the SQL Server 2005 for Default Database, I use Windows
Authentication and Local System.
Is there a way to know whether the [sa] has blank password or not?
Further notice: I tried to input [sa] password, and I use the same password
in "DataAccessLayer.config" under "Password=" value; but it still won't work.
The error message is still the same as before.
Any other suggestions perhaps?
Thanks!
"Arnie Rowland" wrote:
> And did you really install SQL 2005 without a password for the [sa] account?
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "Dhow" <Dhow@.discussions.microsoft.com> wrote in message
> news:9114C9D0-F787-41A2-B2A1-9B84FA635F1B@.microsoft.com...
>
>
|||Arnie,
When I installed the SQL Server 2005 for Default Database, I use Windows
Authentication and Local System.
Is there a way to know whether the [sa] has blank password or not?
Further notice: I tried to input [sa] password, and I use the same password
in "DataAccessLayer.config" under "Password=" value; but it still won't work.
The error message is still the same as before.
Any other suggestions perhaps?
Thanks!
"Arnie Rowland" wrote:
> And did you really install SQL 2005 without a password for the [sa] account?
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "Dhow" <Dhow@.discussions.microsoft.com> wrote in message
> news:9114C9D0-F787-41A2-B2A1-9B84FA635F1B@.microsoft.com...
>
>
|||Arnie,
When I installed the SQL Server 2005 for Default Database, I use Windows
Authentication and Local System.
Is there a way to know whether the [sa] has blank password or not?
Further notice: I tried to input [sa] password, and I use the same password
in "DataAccessLayer.config" under "Password=" value; but it still won't work.
The error message is still the same as before.
Any other suggestions perhaps?
Thanks!
"Arnie Rowland" wrote:
> And did you really install SQL 2005 without a password for the [sa] account?
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "Dhow" <Dhow@.discussions.microsoft.com> wrote in message
> news:9114C9D0-F787-41A2-B2A1-9B84FA635F1B@.microsoft.com...
>
>
|||Arnie,
When I installed the SQL Server 2005 for Default Database, I use Windows
Authentication and Local System.
Is there a way to know whether the [sa] has blank password or not?
Further notice: I tried to input [sa] password, and I use the same password
in "DataAccessLayer.config" under "Password=" value; but it still won't work.
The error message is still the same as before.
Any other suggestions perhaps?
Thanks!
"Arnie Rowland" wrote:
> And did you really install SQL 2005 without a password for the [sa] account?
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "Dhow" <Dhow@.discussions.microsoft.com> wrote in message
> news:9114C9D0-F787-41A2-B2A1-9B84FA635F1B@.microsoft.com...
>
>
|||Arnie,
When I installed the SQL Server 2005 for Default Database, I use Windows
Authentication and Local System.
Is there a way to know whether the [sa] has blank password or not?
Further notice: I tried to input [sa] password, and I use the same password
in "DataAccessLayer.config" under "Password=" value; but it still won't work.
The error message is still the same as before.
Any other suggestions perhaps?
Thanks!
"Arnie Rowland" wrote:
> And did you really install SQL 2005 without a password for the [sa] account?
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "Dhow" <Dhow@.discussions.microsoft.com> wrote in message
> news:9114C9D0-F787-41A2-B2A1-9B84FA635F1B@.microsoft.com...
>
>
|||Tracy,
I know I input blank password for [sa] user, but that was only for a tryout.
Later on after everything works fine, I'll input new password into it.
When I installed the SQL Server 2005 for Default Database, I use Windows
Authentication and Local System.
Is there a way to know whether the [sa] has blank password or not?
Further notice: I tried to input [sa] password, and I use the same password
in "DataAccessLayer.config" under "Password=" value; but it still won't work.
The error message is still the same as before.
Any other usefull sugesstions?
Thanks!
"Tracy McKibben" wrote:
> Dhow wrote:
> You are trying to connect to the server using the "sa" login, with no
> password!!! You have two problems here:
> 1. Never, ever, purposely allow an application to connect as "sa", you
> need to tightly control the use of this login.
> 2. If you purposely installed SQL Server with a blank password for
> "sa", change it, now. Your server is wide open to anybody who chooses
> to login as "sa".
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>
I've just installed SQL Server 2005 into Win SBS 2003 R2, everything went
fine and other instances (SHAREPOINT & SBSMONITORING) are working as well.
The only thing and the most important that should be working but not, is
application that uses SQL Server as it's main database. Before this, the
application used SQL Server 2000 and working fine.
Everytime users launch the application, there's this error message: "Error
in DataAccessLayer.DataAccess.CheckUserLogin. Login failed for user 'sa'."
Although I've allowed Windows Authentication & SQL Server authentication in
SQL Server 2005 logins settings, that error message will still appears and
restrict any users to log-in to the application.
That application uses a "DataAccessLayer.config" file that has this
parameters:
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<appSettings>
<add key="UseWebService" value="false"/>
<add key="DAL.DataService.DataService" value="http://companyweb"/>
<add key="DBCnnString" value="Persist Security Info=False;User
ID=sa;Password=;Initial Catalog=INVENTORY;Data Source=192.168.16.2"/>
<add key="server" value="ServerName"/>
<add key="database" value="INVENTORY"/>
<add key="uid" value="sa"/>
<add key="password" value=""/>
</appSettings>
</configuration>
What happened? Have anyone encountered the same symtomps/problem and know
how to work around it?
Please be noted, I attach this "INVENTORY" database into
ServerName\Database; I do not use instances for it.
Thank you, all help is appreciated.
ON the Security tab, change to [SQL Server and Windows Authentication].
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Dhow" <Dhow@.discussions.microsoft.com> wrote in message
news:9114C9D0-F787-41A2-B2A1-9B84FA635F1B@.microsoft.com...
> Hi,
> I've just installed SQL Server 2005 into Win SBS 2003 R2, everything went
> fine and other instances (SHAREPOINT & SBSMONITORING) are working as well.
> The only thing and the most important that should be working but not, is
> application that uses SQL Server as it's main database. Before this, the
> application used SQL Server 2000 and working fine.
> Everytime users launch the application, there's this error message: "Error
> in DataAccessLayer.DataAccess.CheckUserLogin. Login failed for user
> 'sa'."
> Although I've allowed Windows Authentication & SQL Server authentication
> in
> SQL Server 2005 logins settings, that error message will still appears and
> restrict any users to log-in to the application.
> That application uses a "DataAccessLayer.config" file that has this
> parameters:
> <?xml version="1.0" encoding="utf-8"?>
> <configuration>
> <appSettings>
> <add key="UseWebService" value="false"/>
> <add key="DAL.DataService.DataService" value="http://companyweb"/>
> <add key="DBCnnString" value="Persist Security Info=False;User
> ID=sa;Password=;Initial Catalog=INVENTORY;Data Source=192.168.16.2"/>
> <add key="server" value="ServerName"/>
> <add key="database" value="INVENTORY"/>
> <add key="uid" value="sa"/>
> <add key="password" value=""/>
> </appSettings>
> </configuration>
> What happened? Have anyone encountered the same symtomps/problem and know
> how to work around it?
> Please be noted, I attach this "INVENTORY" database into
> ServerName\Database; I do not use instances for it.
> Thank you, all help is appreciated.
|||And did you really install SQL 2005 without a password for the [sa] account?
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Dhow" <Dhow@.discussions.microsoft.com> wrote in message
news:9114C9D0-F787-41A2-B2A1-9B84FA635F1B@.microsoft.com...
> Hi,
> I've just installed SQL Server 2005 into Win SBS 2003 R2, everything went
> fine and other instances (SHAREPOINT & SBSMONITORING) are working as well.
> The only thing and the most important that should be working but not, is
> application that uses SQL Server as it's main database. Before this, the
> application used SQL Server 2000 and working fine.
> Everytime users launch the application, there's this error message: "Error
> in DataAccessLayer.DataAccess.CheckUserLogin. Login failed for user
> 'sa'."
> Although I've allowed Windows Authentication & SQL Server authentication
> in
> SQL Server 2005 logins settings, that error message will still appears and
> restrict any users to log-in to the application.
> That application uses a "DataAccessLayer.config" file that has this
> parameters:
> <?xml version="1.0" encoding="utf-8"?>
> <configuration>
> <appSettings>
> <add key="UseWebService" value="false"/>
> <add key="DAL.DataService.DataService" value="http://companyweb"/>
> <add key="DBCnnString" value="Persist Security Info=False;User
> ID=sa;Password=;Initial Catalog=INVENTORY;Data Source=192.168.16.2"/>
> <add key="server" value="ServerName"/>
> <add key="database" value="INVENTORY"/>
> <add key="uid" value="sa"/>
> <add key="password" value=""/>
> </appSettings>
> </configuration>
> What happened? Have anyone encountered the same symtomps/problem and know
> how to work around it?
> Please be noted, I attach this "INVENTORY" database into
> ServerName\Database; I do not use instances for it.
> Thank you, all help is appreciated.
|||Dhow wrote:
> Hi,
> I've just installed SQL Server 2005 into Win SBS 2003 R2, everything went
> fine and other instances (SHAREPOINT & SBSMONITORING) are working as well.
> The only thing and the most important that should be working but not, is
> application that uses SQL Server as it's main database. Before this, the
> application used SQL Server 2000 and working fine.
> Everytime users launch the application, there's this error message: "Error
> in DataAccessLayer.DataAccess.CheckUserLogin. Login failed for user 'sa'."
> Although I've allowed Windows Authentication & SQL Server authentication in
> SQL Server 2005 logins settings, that error message will still appears and
> restrict any users to log-in to the application.
> That application uses a "DataAccessLayer.config" file that has this
> parameters:
> <?xml version="1.0" encoding="utf-8"?>
> <configuration>
> <appSettings>
> <add key="UseWebService" value="false"/>
> <add key="DAL.DataService.DataService" value="http://companyweb"/>
> <add key="DBCnnString" value="Persist Security Info=False;User
> ID=sa;Password=;Initial Catalog=INVENTORY;Data Source=192.168.16.2"/>
> <add key="server" value="ServerName"/>
> <add key="database" value="INVENTORY"/>
> <add key="uid" value="sa"/>
> <add key="password" value=""/>
> </appSettings>
> </configuration>
> What happened? Have anyone encountered the same symtomps/problem and know
> how to work around it?
> Please be noted, I attach this "INVENTORY" database into
> ServerName\Database; I do not use instances for it.
> Thank you, all help is appreciated.
You are trying to connect to the server using the "sa" login, with no
password!!! You have two problems here:
1. Never, ever, purposely allow an application to connect as "sa", you
need to tightly control the use of this login.
2. If you purposely installed SQL Server with a blank password for
"sa", change it, now. Your server is wide open to anybody who chooses
to login as "sa".
Tracy McKibben
MCDBA
http://www.realsqlguy.com
|||Arnie,
When I installed the SQL Server 2005 for Default Database, I use Windows
Authentication and Local System.
Is there a way to know whether the [sa] has blank password or not?
Further notice: I tried to input [sa] password, and I use the same password
in "DataAccessLayer.config" under "Password=" value; but it still won't work.
The error message is still the same as before.
Any other suggestions perhaps?
Thanks!
"Arnie Rowland" wrote:
> And did you really install SQL 2005 without a password for the [sa] account?
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "Dhow" <Dhow@.discussions.microsoft.com> wrote in message
> news:9114C9D0-F787-41A2-B2A1-9B84FA635F1B@.microsoft.com...
>
>
|||Arnie,
When I installed the SQL Server 2005 for Default Database, I use Windows
Authentication and Local System.
Is there a way to know whether the [sa] has blank password or not?
Further notice: I tried to input [sa] password, and I use the same password
in "DataAccessLayer.config" under "Password=" value; but it still won't work.
The error message is still the same as before.
Any other suggestions perhaps?
Thanks!
"Arnie Rowland" wrote:
> And did you really install SQL 2005 without a password for the [sa] account?
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "Dhow" <Dhow@.discussions.microsoft.com> wrote in message
> news:9114C9D0-F787-41A2-B2A1-9B84FA635F1B@.microsoft.com...
>
>
|||Arnie,
When I installed the SQL Server 2005 for Default Database, I use Windows
Authentication and Local System.
Is there a way to know whether the [sa] has blank password or not?
Further notice: I tried to input [sa] password, and I use the same password
in "DataAccessLayer.config" under "Password=" value; but it still won't work.
The error message is still the same as before.
Any other suggestions perhaps?
Thanks!
"Arnie Rowland" wrote:
> And did you really install SQL 2005 without a password for the [sa] account?
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "Dhow" <Dhow@.discussions.microsoft.com> wrote in message
> news:9114C9D0-F787-41A2-B2A1-9B84FA635F1B@.microsoft.com...
>
>
|||Arnie,
When I installed the SQL Server 2005 for Default Database, I use Windows
Authentication and Local System.
Is there a way to know whether the [sa] has blank password or not?
Further notice: I tried to input [sa] password, and I use the same password
in "DataAccessLayer.config" under "Password=" value; but it still won't work.
The error message is still the same as before.
Any other suggestions perhaps?
Thanks!
"Arnie Rowland" wrote:
> And did you really install SQL 2005 without a password for the [sa] account?
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "Dhow" <Dhow@.discussions.microsoft.com> wrote in message
> news:9114C9D0-F787-41A2-B2A1-9B84FA635F1B@.microsoft.com...
>
>
|||Arnie,
When I installed the SQL Server 2005 for Default Database, I use Windows
Authentication and Local System.
Is there a way to know whether the [sa] has blank password or not?
Further notice: I tried to input [sa] password, and I use the same password
in "DataAccessLayer.config" under "Password=" value; but it still won't work.
The error message is still the same as before.
Any other suggestions perhaps?
Thanks!
"Arnie Rowland" wrote:
> And did you really install SQL 2005 without a password for the [sa] account?
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "Dhow" <Dhow@.discussions.microsoft.com> wrote in message
> news:9114C9D0-F787-41A2-B2A1-9B84FA635F1B@.microsoft.com...
>
>
|||Tracy,
I know I input blank password for [sa] user, but that was only for a tryout.
Later on after everything works fine, I'll input new password into it.
When I installed the SQL Server 2005 for Default Database, I use Windows
Authentication and Local System.
Is there a way to know whether the [sa] has blank password or not?
Further notice: I tried to input [sa] password, and I use the same password
in "DataAccessLayer.config" under "Password=" value; but it still won't work.
The error message is still the same as before.
Any other usefull sugesstions?
Thanks!
"Tracy McKibben" wrote:
> Dhow wrote:
> You are trying to connect to the server using the "sa" login, with no
> password!!! You have two problems here:
> 1. Never, ever, purposely allow an application to connect as "sa", you
> need to tightly control the use of this login.
> 2. If you purposely installed SQL Server with a blank password for
> "sa", change it, now. Your server is wide open to anybody who chooses
> to login as "sa".
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>
failed to connect to SQL Server's database!
Hi,
I've just installed SQL Server 2005 into Win SBS 2003 R2, everything went
fine and other instances (SHAREPOINT & SBSMONITORING) are working as well.
The only thing and the most important that should be working but not, is
application that uses SQL Server as it's main database. Before this, the
application used SQL Server 2000 and working fine.
Everytime users launch the application, there's this error message: "Error
in DataAccessLayer.DataAccess.CheckUserLogin. Login failed for user 'sa'."
Although I've allowed Windows Authentication & SQL Server authentication in
SQL Server 2005 logins settings, that error message will still appears and
restrict any users to log-in to the application.
That application uses a "DataAccessLayer.config" file that has this
parameters:
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<appSettings>
<add key="UseWebService" value="false"/>
<add key="DAL.DataService.DataService" value="http://companyweb"/>
<add key="DBCnnString" value="Persist Security Info=False;User
ID=sa;Password=;Initial Catalog=INVENTORY;Data Source=192.168.16.2"/>
<add key="server" value="ServerName"/>
<add key="database" value="INVENTORY"/>
<add key="uid" value="sa"/>
<add key="password" value=""/>
</appSettings>
</configuration>
What happened? Have anyone encountered the same symtomps/problem and know
how to work around it?
Please be noted, I attach this "INVENTORY" database into
ServerName\Database; I do not use instances for it.
Thank you, all help is appreciated.ON the Security tab, change to [SQL Server and Windows Authentication].
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Dhow" <Dhow@.discussions.microsoft.com> wrote in message
news:9114C9D0-F787-41A2-B2A1-9B84FA635F1B@.microsoft.com...
> Hi,
> I've just installed SQL Server 2005 into Win SBS 2003 R2, everything went
> fine and other instances (SHAREPOINT & SBSMONITORING) are working as well.
> The only thing and the most important that should be working but not, is
> application that uses SQL Server as it's main database. Before this, the
> application used SQL Server 2000 and working fine.
> Everytime users launch the application, there's this error message: "Error
> in DataAccessLayer.DataAccess.CheckUserLogin. Login failed for user
> 'sa'."
> Although I've allowed Windows Authentication & SQL Server authentication
> in
> SQL Server 2005 logins settings, that error message will still appears and
> restrict any users to log-in to the application.
> That application uses a "DataAccessLayer.config" file that has this
> parameters:
> <?xml version="1.0" encoding="utf-8"?>
> <configuration>
> <appSettings>
> <add key="UseWebService" value="false"/>
> <add key="DAL.DataService.DataService" value="http://companyweb"/>
> <add key="DBCnnString" value="Persist Security Info=False;User
> ID=sa;Password=;Initial Catalog=INVENTORY;Data Source=192.168.16.2"/>
> <add key="server" value="ServerName"/>
> <add key="database" value="INVENTORY"/>
> <add key="uid" value="sa"/>
> <add key="password" value=""/>
> </appSettings>
> </configuration>
> What happened? Have anyone encountered the same symtomps/problem and know
> how to work around it?
> Please be noted, I attach this "INVENTORY" database into
> ServerName\Database; I do not use instances for it.
> Thank you, all help is appreciated.|||And did you really install SQL 2005 without a password for the [sa] account?
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Dhow" <Dhow@.discussions.microsoft.com> wrote in message
news:9114C9D0-F787-41A2-B2A1-9B84FA635F1B@.microsoft.com...
> Hi,
> I've just installed SQL Server 2005 into Win SBS 2003 R2, everything went
> fine and other instances (SHAREPOINT & SBSMONITORING) are working as well.
> The only thing and the most important that should be working but not, is
> application that uses SQL Server as it's main database. Before this, the
> application used SQL Server 2000 and working fine.
> Everytime users launch the application, there's this error message: "Error
> in DataAccessLayer.DataAccess.CheckUserLogin. Login failed for user
> 'sa'."
> Although I've allowed Windows Authentication & SQL Server authentication
> in
> SQL Server 2005 logins settings, that error message will still appears and
> restrict any users to log-in to the application.
> That application uses a "DataAccessLayer.config" file that has this
> parameters:
> <?xml version="1.0" encoding="utf-8"?>
> <configuration>
> <appSettings>
> <add key="UseWebService" value="false"/>
> <add key="DAL.DataService.DataService" value="http://companyweb"/>
> <add key="DBCnnString" value="Persist Security Info=False;User
> ID=sa;Password=;Initial Catalog=INVENTORY;Data Source=192.168.16.2"/>
> <add key="server" value="ServerName"/>
> <add key="database" value="INVENTORY"/>
> <add key="uid" value="sa"/>
> <add key="password" value=""/>
> </appSettings>
> </configuration>
> What happened? Have anyone encountered the same symtomps/problem and know
> how to work around it?
> Please be noted, I attach this "INVENTORY" database into
> ServerName\Database; I do not use instances for it.
> Thank you, all help is appreciated.|||Dhow wrote:
> Hi,
> I've just installed SQL Server 2005 into Win SBS 2003 R2, everything went
> fine and other instances (SHAREPOINT & SBSMONITORING) are working as well.
> The only thing and the most important that should be working but not, is
> application that uses SQL Server as it's main database. Before this, the
> application used SQL Server 2000 and working fine.
> Everytime users launch the application, there's this error message: "Error
> in DataAccessLayer.DataAccess.CheckUserLogin. Login failed for user 'sa'."
> Although I've allowed Windows Authentication & SQL Server authentication in
> SQL Server 2005 logins settings, that error message will still appears and
> restrict any users to log-in to the application.
> That application uses a "DataAccessLayer.config" file that has this
> parameters:
> <?xml version="1.0" encoding="utf-8"?>
> <configuration>
> <appSettings>
> <add key="UseWebService" value="false"/>
> <add key="DAL.DataService.DataService" value="http://companyweb"/>
> <add key="DBCnnString" value="Persist Security Info=False;User
> ID=sa;Password=;Initial Catalog=INVENTORY;Data Source=192.168.16.2"/>
> <add key="server" value="ServerName"/>
> <add key="database" value="INVENTORY"/>
> <add key="uid" value="sa"/>
> <add key="password" value=""/>
> </appSettings>
> </configuration>
> What happened? Have anyone encountered the same symtomps/problem and know
> how to work around it?
> Please be noted, I attach this "INVENTORY" database into
> ServerName\Database; I do not use instances for it.
> Thank you, all help is appreciated.
You are trying to connect to the server using the "sa" login, with no
password!!! You have two problems here:
1. Never, ever, purposely allow an application to connect as "sa", you
need to tightly control the use of this login.
2. If you purposely installed SQL Server with a blank password for
"sa", change it, now. Your server is wide open to anybody who chooses
to login as "sa".
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Arnie,
When I installed the SQL Server 2005 for Default Database, I use Windows
Authentication and Local System.
Is there a way to know whether the [sa] has blank password or not?
Further notice: I tried to input [sa] password, and I use the same password
in "DataAccessLayer.config" under "Password=" value; but it still won't work.
The error message is still the same as before.
Any other suggestions perhaps?
Thanks!
"Arnie Rowland" wrote:
> And did you really install SQL 2005 without a password for the [sa] account?
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "Dhow" <Dhow@.discussions.microsoft.com> wrote in message
> news:9114C9D0-F787-41A2-B2A1-9B84FA635F1B@.microsoft.com...
> > Hi,
> > I've just installed SQL Server 2005 into Win SBS 2003 R2, everything went
> > fine and other instances (SHAREPOINT & SBSMONITORING) are working as well.
> > The only thing and the most important that should be working but not, is
> > application that uses SQL Server as it's main database. Before this, the
> > application used SQL Server 2000 and working fine.
> > Everytime users launch the application, there's this error message: "Error
> > in DataAccessLayer.DataAccess.CheckUserLogin. Login failed for user
> > 'sa'."
> > Although I've allowed Windows Authentication & SQL Server authentication
> > in
> > SQL Server 2005 logins settings, that error message will still appears and
> > restrict any users to log-in to the application.
> > That application uses a "DataAccessLayer.config" file that has this
> > parameters:
> >
> > <?xml version="1.0" encoding="utf-8"?>
> > <configuration>
> > <appSettings>
> > <add key="UseWebService" value="false"/>
> > <add key="DAL.DataService.DataService" value="http://companyweb"/>
> > <add key="DBCnnString" value="Persist Security Info=False;User
> > ID=sa;Password=;Initial Catalog=INVENTORY;Data Source=192.168.16.2"/>
> > <add key="server" value="ServerName"/>
> > <add key="database" value="INVENTORY"/>
> > <add key="uid" value="sa"/>
> > <add key="password" value=""/>
> > </appSettings>
> > </configuration>
> >
> > What happened? Have anyone encountered the same symtomps/problem and know
> > how to work around it?
> > Please be noted, I attach this "INVENTORY" database into
> > ServerName\Database; I do not use instances for it.
> > Thank you, all help is appreciated.
>
>|||Arnie,
When I installed the SQL Server 2005 for Default Database, I use Windows
Authentication and Local System.
Is there a way to know whether the [sa] has blank password or not?
Further notice: I tried to input [sa] password, and I use the same password
in "DataAccessLayer.config" under "Password=" value; but it still won't work.
The error message is still the same as before.
Any other suggestions perhaps?
Thanks!
"Arnie Rowland" wrote:
> And did you really install SQL 2005 without a password for the [sa] account?
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "Dhow" <Dhow@.discussions.microsoft.com> wrote in message
> news:9114C9D0-F787-41A2-B2A1-9B84FA635F1B@.microsoft.com...
> > Hi,
> > I've just installed SQL Server 2005 into Win SBS 2003 R2, everything went
> > fine and other instances (SHAREPOINT & SBSMONITORING) are working as well.
> > The only thing and the most important that should be working but not, is
> > application that uses SQL Server as it's main database. Before this, the
> > application used SQL Server 2000 and working fine.
> > Everytime users launch the application, there's this error message: "Error
> > in DataAccessLayer.DataAccess.CheckUserLogin. Login failed for user
> > 'sa'."
> > Although I've allowed Windows Authentication & SQL Server authentication
> > in
> > SQL Server 2005 logins settings, that error message will still appears and
> > restrict any users to log-in to the application.
> > That application uses a "DataAccessLayer.config" file that has this
> > parameters:
> >
> > <?xml version="1.0" encoding="utf-8"?>
> > <configuration>
> > <appSettings>
> > <add key="UseWebService" value="false"/>
> > <add key="DAL.DataService.DataService" value="http://companyweb"/>
> > <add key="DBCnnString" value="Persist Security Info=False;User
> > ID=sa;Password=;Initial Catalog=INVENTORY;Data Source=192.168.16.2"/>
> > <add key="server" value="ServerName"/>
> > <add key="database" value="INVENTORY"/>
> > <add key="uid" value="sa"/>
> > <add key="password" value=""/>
> > </appSettings>
> > </configuration>
> >
> > What happened? Have anyone encountered the same symtomps/problem and know
> > how to work around it?
> > Please be noted, I attach this "INVENTORY" database into
> > ServerName\Database; I do not use instances for it.
> > Thank you, all help is appreciated.
>
>|||Arnie,
When I installed the SQL Server 2005 for Default Database, I use Windows
Authentication and Local System.
Is there a way to know whether the [sa] has blank password or not?
Further notice: I tried to input [sa] password, and I use the same password
in "DataAccessLayer.config" under "Password=" value; but it still won't work.
The error message is still the same as before.
Any other suggestions perhaps?
Thanks!
"Arnie Rowland" wrote:
> And did you really install SQL 2005 without a password for the [sa] account?
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "Dhow" <Dhow@.discussions.microsoft.com> wrote in message
> news:9114C9D0-F787-41A2-B2A1-9B84FA635F1B@.microsoft.com...
> > Hi,
> > I've just installed SQL Server 2005 into Win SBS 2003 R2, everything went
> > fine and other instances (SHAREPOINT & SBSMONITORING) are working as well.
> > The only thing and the most important that should be working but not, is
> > application that uses SQL Server as it's main database. Before this, the
> > application used SQL Server 2000 and working fine.
> > Everytime users launch the application, there's this error message: "Error
> > in DataAccessLayer.DataAccess.CheckUserLogin. Login failed for user
> > 'sa'."
> > Although I've allowed Windows Authentication & SQL Server authentication
> > in
> > SQL Server 2005 logins settings, that error message will still appears and
> > restrict any users to log-in to the application.
> > That application uses a "DataAccessLayer.config" file that has this
> > parameters:
> >
> > <?xml version="1.0" encoding="utf-8"?>
> > <configuration>
> > <appSettings>
> > <add key="UseWebService" value="false"/>
> > <add key="DAL.DataService.DataService" value="http://companyweb"/>
> > <add key="DBCnnString" value="Persist Security Info=False;User
> > ID=sa;Password=;Initial Catalog=INVENTORY;Data Source=192.168.16.2"/>
> > <add key="server" value="ServerName"/>
> > <add key="database" value="INVENTORY"/>
> > <add key="uid" value="sa"/>
> > <add key="password" value=""/>
> > </appSettings>
> > </configuration>
> >
> > What happened? Have anyone encountered the same symtomps/problem and know
> > how to work around it?
> > Please be noted, I attach this "INVENTORY" database into
> > ServerName\Database; I do not use instances for it.
> > Thank you, all help is appreciated.
>
>|||Arnie,
When I installed the SQL Server 2005 for Default Database, I use Windows
Authentication and Local System.
Is there a way to know whether the [sa] has blank password or not?
Further notice: I tried to input [sa] password, and I use the same password
in "DataAccessLayer.config" under "Password=" value; but it still won't work.
The error message is still the same as before.
Any other suggestions perhaps?
Thanks!
"Arnie Rowland" wrote:
> And did you really install SQL 2005 without a password for the [sa] account?
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "Dhow" <Dhow@.discussions.microsoft.com> wrote in message
> news:9114C9D0-F787-41A2-B2A1-9B84FA635F1B@.microsoft.com...
> > Hi,
> > I've just installed SQL Server 2005 into Win SBS 2003 R2, everything went
> > fine and other instances (SHAREPOINT & SBSMONITORING) are working as well.
> > The only thing and the most important that should be working but not, is
> > application that uses SQL Server as it's main database. Before this, the
> > application used SQL Server 2000 and working fine.
> > Everytime users launch the application, there's this error message: "Error
> > in DataAccessLayer.DataAccess.CheckUserLogin. Login failed for user
> > 'sa'."
> > Although I've allowed Windows Authentication & SQL Server authentication
> > in
> > SQL Server 2005 logins settings, that error message will still appears and
> > restrict any users to log-in to the application.
> > That application uses a "DataAccessLayer.config" file that has this
> > parameters:
> >
> > <?xml version="1.0" encoding="utf-8"?>
> > <configuration>
> > <appSettings>
> > <add key="UseWebService" value="false"/>
> > <add key="DAL.DataService.DataService" value="http://companyweb"/>
> > <add key="DBCnnString" value="Persist Security Info=False;User
> > ID=sa;Password=;Initial Catalog=INVENTORY;Data Source=192.168.16.2"/>
> > <add key="server" value="ServerName"/>
> > <add key="database" value="INVENTORY"/>
> > <add key="uid" value="sa"/>
> > <add key="password" value=""/>
> > </appSettings>
> > </configuration>
> >
> > What happened? Have anyone encountered the same symtomps/problem and know
> > how to work around it?
> > Please be noted, I attach this "INVENTORY" database into
> > ServerName\Database; I do not use instances for it.
> > Thank you, all help is appreciated.
>
>|||Arnie,
When I installed the SQL Server 2005 for Default Database, I use Windows
Authentication and Local System.
Is there a way to know whether the [sa] has blank password or not?
Further notice: I tried to input [sa] password, and I use the same password
in "DataAccessLayer.config" under "Password=" value; but it still won't work.
The error message is still the same as before.
Any other suggestions perhaps?
Thanks!
"Arnie Rowland" wrote:
> And did you really install SQL 2005 without a password for the [sa] account?
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "Dhow" <Dhow@.discussions.microsoft.com> wrote in message
> news:9114C9D0-F787-41A2-B2A1-9B84FA635F1B@.microsoft.com...
> > Hi,
> > I've just installed SQL Server 2005 into Win SBS 2003 R2, everything went
> > fine and other instances (SHAREPOINT & SBSMONITORING) are working as well.
> > The only thing and the most important that should be working but not, is
> > application that uses SQL Server as it's main database. Before this, the
> > application used SQL Server 2000 and working fine.
> > Everytime users launch the application, there's this error message: "Error
> > in DataAccessLayer.DataAccess.CheckUserLogin. Login failed for user
> > 'sa'."
> > Although I've allowed Windows Authentication & SQL Server authentication
> > in
> > SQL Server 2005 logins settings, that error message will still appears and
> > restrict any users to log-in to the application.
> > That application uses a "DataAccessLayer.config" file that has this
> > parameters:
> >
> > <?xml version="1.0" encoding="utf-8"?>
> > <configuration>
> > <appSettings>
> > <add key="UseWebService" value="false"/>
> > <add key="DAL.DataService.DataService" value="http://companyweb"/>
> > <add key="DBCnnString" value="Persist Security Info=False;User
> > ID=sa;Password=;Initial Catalog=INVENTORY;Data Source=192.168.16.2"/>
> > <add key="server" value="ServerName"/>
> > <add key="database" value="INVENTORY"/>
> > <add key="uid" value="sa"/>
> > <add key="password" value=""/>
> > </appSettings>
> > </configuration>
> >
> > What happened? Have anyone encountered the same symtomps/problem and know
> > how to work around it?
> > Please be noted, I attach this "INVENTORY" database into
> > ServerName\Database; I do not use instances for it.
> > Thank you, all help is appreciated.
>
>|||Tracy,
I know I input blank password for [sa] user, but that was only for a tryout.
Later on after everything works fine, I'll input new password into it.
When I installed the SQL Server 2005 for Default Database, I use Windows
Authentication and Local System.
Is there a way to know whether the [sa] has blank password or not?
Further notice: I tried to input [sa] password, and I use the same password
in "DataAccessLayer.config" under "Password=" value; but it still won't work.
The error message is still the same as before.
Any other usefull sugesstions?
Thanks!
"Tracy McKibben" wrote:
> Dhow wrote:
> > Hi,
> > I've just installed SQL Server 2005 into Win SBS 2003 R2, everything went
> > fine and other instances (SHAREPOINT & SBSMONITORING) are working as well.
> > The only thing and the most important that should be working but not, is
> > application that uses SQL Server as it's main database. Before this, the
> > application used SQL Server 2000 and working fine.
> > Everytime users launch the application, there's this error message: "Error
> > in DataAccessLayer.DataAccess.CheckUserLogin. Login failed for user 'sa'."
> > Although I've allowed Windows Authentication & SQL Server authentication in
> > SQL Server 2005 logins settings, that error message will still appears and
> > restrict any users to log-in to the application.
> > That application uses a "DataAccessLayer.config" file that has this
> > parameters:
> >
> > <?xml version="1.0" encoding="utf-8"?>
> > <configuration>
> > <appSettings>
> > <add key="UseWebService" value="false"/>
> > <add key="DAL.DataService.DataService" value="http://companyweb"/>
> > <add key="DBCnnString" value="Persist Security Info=False;User
> > ID=sa;Password=;Initial Catalog=INVENTORY;Data Source=192.168.16.2"/>
> > <add key="server" value="ServerName"/>
> > <add key="database" value="INVENTORY"/>
> > <add key="uid" value="sa"/>
> > <add key="password" value=""/>
> > </appSettings>
> > </configuration>
> >
> > What happened? Have anyone encountered the same symtomps/problem and know
> > how to work around it?
> > Please be noted, I attach this "INVENTORY" database into
> > ServerName\Database; I do not use instances for it.
> > Thank you, all help is appreciated.
> You are trying to connect to the server using the "sa" login, with no
> password!!! You have two problems here:
> 1. Never, ever, purposely allow an application to connect as "sa", you
> need to tightly control the use of this login.
> 2. If you purposely installed SQL Server with a blank password for
> "sa", change it, now. Your server is wide open to anybody who chooses
> to login as "sa".
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>|||It seemed there's an error in MSTechNet website, everytime I tried to reply
to Arnie & Tracy, the reply window said there's a server error. So I kept
repeating it, and realize that there have been so many replies send, sorry.
I've just Detach the INVENTORY database from default database (MSSQLSERVER),
but the result is quite surprising: I can't logon again to default database
(MSSQLSERVER)!
I don't understand why I can't login again, the SQL Server 2005 only said
that there has been no activity at the other end & after that it said there's
been logon failure...
What happened?
I too tried to creat an Instance in SQL Server 2005 named with INVENTORY,
after the Detach process (like I've mentioned up above), it also can't be
connected again. The error message is the same as above. What really
happening here?
Maybe someone have same experience like mine and now hot to work around it?
Now everytime I launch SQL Server Management Studio, there is always
INVENTORY database engines instance, although I've uninstall it. Can I delete
it from database engines options?
Thanks!
I've just installed SQL Server 2005 into Win SBS 2003 R2, everything went
fine and other instances (SHAREPOINT & SBSMONITORING) are working as well.
The only thing and the most important that should be working but not, is
application that uses SQL Server as it's main database. Before this, the
application used SQL Server 2000 and working fine.
Everytime users launch the application, there's this error message: "Error
in DataAccessLayer.DataAccess.CheckUserLogin. Login failed for user 'sa'."
Although I've allowed Windows Authentication & SQL Server authentication in
SQL Server 2005 logins settings, that error message will still appears and
restrict any users to log-in to the application.
That application uses a "DataAccessLayer.config" file that has this
parameters:
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<appSettings>
<add key="UseWebService" value="false"/>
<add key="DAL.DataService.DataService" value="http://companyweb"/>
<add key="DBCnnString" value="Persist Security Info=False;User
ID=sa;Password=;Initial Catalog=INVENTORY;Data Source=192.168.16.2"/>
<add key="server" value="ServerName"/>
<add key="database" value="INVENTORY"/>
<add key="uid" value="sa"/>
<add key="password" value=""/>
</appSettings>
</configuration>
What happened? Have anyone encountered the same symtomps/problem and know
how to work around it?
Please be noted, I attach this "INVENTORY" database into
ServerName\Database; I do not use instances for it.
Thank you, all help is appreciated.ON the Security tab, change to [SQL Server and Windows Authentication].
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Dhow" <Dhow@.discussions.microsoft.com> wrote in message
news:9114C9D0-F787-41A2-B2A1-9B84FA635F1B@.microsoft.com...
> Hi,
> I've just installed SQL Server 2005 into Win SBS 2003 R2, everything went
> fine and other instances (SHAREPOINT & SBSMONITORING) are working as well.
> The only thing and the most important that should be working but not, is
> application that uses SQL Server as it's main database. Before this, the
> application used SQL Server 2000 and working fine.
> Everytime users launch the application, there's this error message: "Error
> in DataAccessLayer.DataAccess.CheckUserLogin. Login failed for user
> 'sa'."
> Although I've allowed Windows Authentication & SQL Server authentication
> in
> SQL Server 2005 logins settings, that error message will still appears and
> restrict any users to log-in to the application.
> That application uses a "DataAccessLayer.config" file that has this
> parameters:
> <?xml version="1.0" encoding="utf-8"?>
> <configuration>
> <appSettings>
> <add key="UseWebService" value="false"/>
> <add key="DAL.DataService.DataService" value="http://companyweb"/>
> <add key="DBCnnString" value="Persist Security Info=False;User
> ID=sa;Password=;Initial Catalog=INVENTORY;Data Source=192.168.16.2"/>
> <add key="server" value="ServerName"/>
> <add key="database" value="INVENTORY"/>
> <add key="uid" value="sa"/>
> <add key="password" value=""/>
> </appSettings>
> </configuration>
> What happened? Have anyone encountered the same symtomps/problem and know
> how to work around it?
> Please be noted, I attach this "INVENTORY" database into
> ServerName\Database; I do not use instances for it.
> Thank you, all help is appreciated.|||And did you really install SQL 2005 without a password for the [sa] account?
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Dhow" <Dhow@.discussions.microsoft.com> wrote in message
news:9114C9D0-F787-41A2-B2A1-9B84FA635F1B@.microsoft.com...
> Hi,
> I've just installed SQL Server 2005 into Win SBS 2003 R2, everything went
> fine and other instances (SHAREPOINT & SBSMONITORING) are working as well.
> The only thing and the most important that should be working but not, is
> application that uses SQL Server as it's main database. Before this, the
> application used SQL Server 2000 and working fine.
> Everytime users launch the application, there's this error message: "Error
> in DataAccessLayer.DataAccess.CheckUserLogin. Login failed for user
> 'sa'."
> Although I've allowed Windows Authentication & SQL Server authentication
> in
> SQL Server 2005 logins settings, that error message will still appears and
> restrict any users to log-in to the application.
> That application uses a "DataAccessLayer.config" file that has this
> parameters:
> <?xml version="1.0" encoding="utf-8"?>
> <configuration>
> <appSettings>
> <add key="UseWebService" value="false"/>
> <add key="DAL.DataService.DataService" value="http://companyweb"/>
> <add key="DBCnnString" value="Persist Security Info=False;User
> ID=sa;Password=;Initial Catalog=INVENTORY;Data Source=192.168.16.2"/>
> <add key="server" value="ServerName"/>
> <add key="database" value="INVENTORY"/>
> <add key="uid" value="sa"/>
> <add key="password" value=""/>
> </appSettings>
> </configuration>
> What happened? Have anyone encountered the same symtomps/problem and know
> how to work around it?
> Please be noted, I attach this "INVENTORY" database into
> ServerName\Database; I do not use instances for it.
> Thank you, all help is appreciated.|||Dhow wrote:
> Hi,
> I've just installed SQL Server 2005 into Win SBS 2003 R2, everything went
> fine and other instances (SHAREPOINT & SBSMONITORING) are working as well.
> The only thing and the most important that should be working but not, is
> application that uses SQL Server as it's main database. Before this, the
> application used SQL Server 2000 and working fine.
> Everytime users launch the application, there's this error message: "Error
> in DataAccessLayer.DataAccess.CheckUserLogin. Login failed for user 'sa'."
> Although I've allowed Windows Authentication & SQL Server authentication in
> SQL Server 2005 logins settings, that error message will still appears and
> restrict any users to log-in to the application.
> That application uses a "DataAccessLayer.config" file that has this
> parameters:
> <?xml version="1.0" encoding="utf-8"?>
> <configuration>
> <appSettings>
> <add key="UseWebService" value="false"/>
> <add key="DAL.DataService.DataService" value="http://companyweb"/>
> <add key="DBCnnString" value="Persist Security Info=False;User
> ID=sa;Password=;Initial Catalog=INVENTORY;Data Source=192.168.16.2"/>
> <add key="server" value="ServerName"/>
> <add key="database" value="INVENTORY"/>
> <add key="uid" value="sa"/>
> <add key="password" value=""/>
> </appSettings>
> </configuration>
> What happened? Have anyone encountered the same symtomps/problem and know
> how to work around it?
> Please be noted, I attach this "INVENTORY" database into
> ServerName\Database; I do not use instances for it.
> Thank you, all help is appreciated.
You are trying to connect to the server using the "sa" login, with no
password!!! You have two problems here:
1. Never, ever, purposely allow an application to connect as "sa", you
need to tightly control the use of this login.
2. If you purposely installed SQL Server with a blank password for
"sa", change it, now. Your server is wide open to anybody who chooses
to login as "sa".
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Arnie,
When I installed the SQL Server 2005 for Default Database, I use Windows
Authentication and Local System.
Is there a way to know whether the [sa] has blank password or not?
Further notice: I tried to input [sa] password, and I use the same password
in "DataAccessLayer.config" under "Password=" value; but it still won't work.
The error message is still the same as before.
Any other suggestions perhaps?
Thanks!
"Arnie Rowland" wrote:
> And did you really install SQL 2005 without a password for the [sa] account?
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "Dhow" <Dhow@.discussions.microsoft.com> wrote in message
> news:9114C9D0-F787-41A2-B2A1-9B84FA635F1B@.microsoft.com...
> > Hi,
> > I've just installed SQL Server 2005 into Win SBS 2003 R2, everything went
> > fine and other instances (SHAREPOINT & SBSMONITORING) are working as well.
> > The only thing and the most important that should be working but not, is
> > application that uses SQL Server as it's main database. Before this, the
> > application used SQL Server 2000 and working fine.
> > Everytime users launch the application, there's this error message: "Error
> > in DataAccessLayer.DataAccess.CheckUserLogin. Login failed for user
> > 'sa'."
> > Although I've allowed Windows Authentication & SQL Server authentication
> > in
> > SQL Server 2005 logins settings, that error message will still appears and
> > restrict any users to log-in to the application.
> > That application uses a "DataAccessLayer.config" file that has this
> > parameters:
> >
> > <?xml version="1.0" encoding="utf-8"?>
> > <configuration>
> > <appSettings>
> > <add key="UseWebService" value="false"/>
> > <add key="DAL.DataService.DataService" value="http://companyweb"/>
> > <add key="DBCnnString" value="Persist Security Info=False;User
> > ID=sa;Password=;Initial Catalog=INVENTORY;Data Source=192.168.16.2"/>
> > <add key="server" value="ServerName"/>
> > <add key="database" value="INVENTORY"/>
> > <add key="uid" value="sa"/>
> > <add key="password" value=""/>
> > </appSettings>
> > </configuration>
> >
> > What happened? Have anyone encountered the same symtomps/problem and know
> > how to work around it?
> > Please be noted, I attach this "INVENTORY" database into
> > ServerName\Database; I do not use instances for it.
> > Thank you, all help is appreciated.
>
>|||Arnie,
When I installed the SQL Server 2005 for Default Database, I use Windows
Authentication and Local System.
Is there a way to know whether the [sa] has blank password or not?
Further notice: I tried to input [sa] password, and I use the same password
in "DataAccessLayer.config" under "Password=" value; but it still won't work.
The error message is still the same as before.
Any other suggestions perhaps?
Thanks!
"Arnie Rowland" wrote:
> And did you really install SQL 2005 without a password for the [sa] account?
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "Dhow" <Dhow@.discussions.microsoft.com> wrote in message
> news:9114C9D0-F787-41A2-B2A1-9B84FA635F1B@.microsoft.com...
> > Hi,
> > I've just installed SQL Server 2005 into Win SBS 2003 R2, everything went
> > fine and other instances (SHAREPOINT & SBSMONITORING) are working as well.
> > The only thing and the most important that should be working but not, is
> > application that uses SQL Server as it's main database. Before this, the
> > application used SQL Server 2000 and working fine.
> > Everytime users launch the application, there's this error message: "Error
> > in DataAccessLayer.DataAccess.CheckUserLogin. Login failed for user
> > 'sa'."
> > Although I've allowed Windows Authentication & SQL Server authentication
> > in
> > SQL Server 2005 logins settings, that error message will still appears and
> > restrict any users to log-in to the application.
> > That application uses a "DataAccessLayer.config" file that has this
> > parameters:
> >
> > <?xml version="1.0" encoding="utf-8"?>
> > <configuration>
> > <appSettings>
> > <add key="UseWebService" value="false"/>
> > <add key="DAL.DataService.DataService" value="http://companyweb"/>
> > <add key="DBCnnString" value="Persist Security Info=False;User
> > ID=sa;Password=;Initial Catalog=INVENTORY;Data Source=192.168.16.2"/>
> > <add key="server" value="ServerName"/>
> > <add key="database" value="INVENTORY"/>
> > <add key="uid" value="sa"/>
> > <add key="password" value=""/>
> > </appSettings>
> > </configuration>
> >
> > What happened? Have anyone encountered the same symtomps/problem and know
> > how to work around it?
> > Please be noted, I attach this "INVENTORY" database into
> > ServerName\Database; I do not use instances for it.
> > Thank you, all help is appreciated.
>
>|||Arnie,
When I installed the SQL Server 2005 for Default Database, I use Windows
Authentication and Local System.
Is there a way to know whether the [sa] has blank password or not?
Further notice: I tried to input [sa] password, and I use the same password
in "DataAccessLayer.config" under "Password=" value; but it still won't work.
The error message is still the same as before.
Any other suggestions perhaps?
Thanks!
"Arnie Rowland" wrote:
> And did you really install SQL 2005 without a password for the [sa] account?
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "Dhow" <Dhow@.discussions.microsoft.com> wrote in message
> news:9114C9D0-F787-41A2-B2A1-9B84FA635F1B@.microsoft.com...
> > Hi,
> > I've just installed SQL Server 2005 into Win SBS 2003 R2, everything went
> > fine and other instances (SHAREPOINT & SBSMONITORING) are working as well.
> > The only thing and the most important that should be working but not, is
> > application that uses SQL Server as it's main database. Before this, the
> > application used SQL Server 2000 and working fine.
> > Everytime users launch the application, there's this error message: "Error
> > in DataAccessLayer.DataAccess.CheckUserLogin. Login failed for user
> > 'sa'."
> > Although I've allowed Windows Authentication & SQL Server authentication
> > in
> > SQL Server 2005 logins settings, that error message will still appears and
> > restrict any users to log-in to the application.
> > That application uses a "DataAccessLayer.config" file that has this
> > parameters:
> >
> > <?xml version="1.0" encoding="utf-8"?>
> > <configuration>
> > <appSettings>
> > <add key="UseWebService" value="false"/>
> > <add key="DAL.DataService.DataService" value="http://companyweb"/>
> > <add key="DBCnnString" value="Persist Security Info=False;User
> > ID=sa;Password=;Initial Catalog=INVENTORY;Data Source=192.168.16.2"/>
> > <add key="server" value="ServerName"/>
> > <add key="database" value="INVENTORY"/>
> > <add key="uid" value="sa"/>
> > <add key="password" value=""/>
> > </appSettings>
> > </configuration>
> >
> > What happened? Have anyone encountered the same symtomps/problem and know
> > how to work around it?
> > Please be noted, I attach this "INVENTORY" database into
> > ServerName\Database; I do not use instances for it.
> > Thank you, all help is appreciated.
>
>|||Arnie,
When I installed the SQL Server 2005 for Default Database, I use Windows
Authentication and Local System.
Is there a way to know whether the [sa] has blank password or not?
Further notice: I tried to input [sa] password, and I use the same password
in "DataAccessLayer.config" under "Password=" value; but it still won't work.
The error message is still the same as before.
Any other suggestions perhaps?
Thanks!
"Arnie Rowland" wrote:
> And did you really install SQL 2005 without a password for the [sa] account?
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "Dhow" <Dhow@.discussions.microsoft.com> wrote in message
> news:9114C9D0-F787-41A2-B2A1-9B84FA635F1B@.microsoft.com...
> > Hi,
> > I've just installed SQL Server 2005 into Win SBS 2003 R2, everything went
> > fine and other instances (SHAREPOINT & SBSMONITORING) are working as well.
> > The only thing and the most important that should be working but not, is
> > application that uses SQL Server as it's main database. Before this, the
> > application used SQL Server 2000 and working fine.
> > Everytime users launch the application, there's this error message: "Error
> > in DataAccessLayer.DataAccess.CheckUserLogin. Login failed for user
> > 'sa'."
> > Although I've allowed Windows Authentication & SQL Server authentication
> > in
> > SQL Server 2005 logins settings, that error message will still appears and
> > restrict any users to log-in to the application.
> > That application uses a "DataAccessLayer.config" file that has this
> > parameters:
> >
> > <?xml version="1.0" encoding="utf-8"?>
> > <configuration>
> > <appSettings>
> > <add key="UseWebService" value="false"/>
> > <add key="DAL.DataService.DataService" value="http://companyweb"/>
> > <add key="DBCnnString" value="Persist Security Info=False;User
> > ID=sa;Password=;Initial Catalog=INVENTORY;Data Source=192.168.16.2"/>
> > <add key="server" value="ServerName"/>
> > <add key="database" value="INVENTORY"/>
> > <add key="uid" value="sa"/>
> > <add key="password" value=""/>
> > </appSettings>
> > </configuration>
> >
> > What happened? Have anyone encountered the same symtomps/problem and know
> > how to work around it?
> > Please be noted, I attach this "INVENTORY" database into
> > ServerName\Database; I do not use instances for it.
> > Thank you, all help is appreciated.
>
>|||Arnie,
When I installed the SQL Server 2005 for Default Database, I use Windows
Authentication and Local System.
Is there a way to know whether the [sa] has blank password or not?
Further notice: I tried to input [sa] password, and I use the same password
in "DataAccessLayer.config" under "Password=" value; but it still won't work.
The error message is still the same as before.
Any other suggestions perhaps?
Thanks!
"Arnie Rowland" wrote:
> And did you really install SQL 2005 without a password for the [sa] account?
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "Dhow" <Dhow@.discussions.microsoft.com> wrote in message
> news:9114C9D0-F787-41A2-B2A1-9B84FA635F1B@.microsoft.com...
> > Hi,
> > I've just installed SQL Server 2005 into Win SBS 2003 R2, everything went
> > fine and other instances (SHAREPOINT & SBSMONITORING) are working as well.
> > The only thing and the most important that should be working but not, is
> > application that uses SQL Server as it's main database. Before this, the
> > application used SQL Server 2000 and working fine.
> > Everytime users launch the application, there's this error message: "Error
> > in DataAccessLayer.DataAccess.CheckUserLogin. Login failed for user
> > 'sa'."
> > Although I've allowed Windows Authentication & SQL Server authentication
> > in
> > SQL Server 2005 logins settings, that error message will still appears and
> > restrict any users to log-in to the application.
> > That application uses a "DataAccessLayer.config" file that has this
> > parameters:
> >
> > <?xml version="1.0" encoding="utf-8"?>
> > <configuration>
> > <appSettings>
> > <add key="UseWebService" value="false"/>
> > <add key="DAL.DataService.DataService" value="http://companyweb"/>
> > <add key="DBCnnString" value="Persist Security Info=False;User
> > ID=sa;Password=;Initial Catalog=INVENTORY;Data Source=192.168.16.2"/>
> > <add key="server" value="ServerName"/>
> > <add key="database" value="INVENTORY"/>
> > <add key="uid" value="sa"/>
> > <add key="password" value=""/>
> > </appSettings>
> > </configuration>
> >
> > What happened? Have anyone encountered the same symtomps/problem and know
> > how to work around it?
> > Please be noted, I attach this "INVENTORY" database into
> > ServerName\Database; I do not use instances for it.
> > Thank you, all help is appreciated.
>
>|||Tracy,
I know I input blank password for [sa] user, but that was only for a tryout.
Later on after everything works fine, I'll input new password into it.
When I installed the SQL Server 2005 for Default Database, I use Windows
Authentication and Local System.
Is there a way to know whether the [sa] has blank password or not?
Further notice: I tried to input [sa] password, and I use the same password
in "DataAccessLayer.config" under "Password=" value; but it still won't work.
The error message is still the same as before.
Any other usefull sugesstions?
Thanks!
"Tracy McKibben" wrote:
> Dhow wrote:
> > Hi,
> > I've just installed SQL Server 2005 into Win SBS 2003 R2, everything went
> > fine and other instances (SHAREPOINT & SBSMONITORING) are working as well.
> > The only thing and the most important that should be working but not, is
> > application that uses SQL Server as it's main database. Before this, the
> > application used SQL Server 2000 and working fine.
> > Everytime users launch the application, there's this error message: "Error
> > in DataAccessLayer.DataAccess.CheckUserLogin. Login failed for user 'sa'."
> > Although I've allowed Windows Authentication & SQL Server authentication in
> > SQL Server 2005 logins settings, that error message will still appears and
> > restrict any users to log-in to the application.
> > That application uses a "DataAccessLayer.config" file that has this
> > parameters:
> >
> > <?xml version="1.0" encoding="utf-8"?>
> > <configuration>
> > <appSettings>
> > <add key="UseWebService" value="false"/>
> > <add key="DAL.DataService.DataService" value="http://companyweb"/>
> > <add key="DBCnnString" value="Persist Security Info=False;User
> > ID=sa;Password=;Initial Catalog=INVENTORY;Data Source=192.168.16.2"/>
> > <add key="server" value="ServerName"/>
> > <add key="database" value="INVENTORY"/>
> > <add key="uid" value="sa"/>
> > <add key="password" value=""/>
> > </appSettings>
> > </configuration>
> >
> > What happened? Have anyone encountered the same symtomps/problem and know
> > how to work around it?
> > Please be noted, I attach this "INVENTORY" database into
> > ServerName\Database; I do not use instances for it.
> > Thank you, all help is appreciated.
> You are trying to connect to the server using the "sa" login, with no
> password!!! You have two problems here:
> 1. Never, ever, purposely allow an application to connect as "sa", you
> need to tightly control the use of this login.
> 2. If you purposely installed SQL Server with a blank password for
> "sa", change it, now. Your server is wide open to anybody who chooses
> to login as "sa".
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>|||It seemed there's an error in MSTechNet website, everytime I tried to reply
to Arnie & Tracy, the reply window said there's a server error. So I kept
repeating it, and realize that there have been so many replies send, sorry.
I've just Detach the INVENTORY database from default database (MSSQLSERVER),
but the result is quite surprising: I can't logon again to default database
(MSSQLSERVER)!
I don't understand why I can't login again, the SQL Server 2005 only said
that there has been no activity at the other end & after that it said there's
been logon failure...
What happened?
I too tried to creat an Instance in SQL Server 2005 named with INVENTORY,
after the Detach process (like I've mentioned up above), it also can't be
connected again. The error message is the same as above. What really
happening here?
Maybe someone have same experience like mine and now hot to work around it?
Now everytime I launch SQL Server Management Studio, there is always
INVENTORY database engines instance, although I've uninstall it. Can I delete
it from database engines options?
Thanks!
failed to connect to SQL Server's database!
Hi,
I've just installed SQL Server 2005 into Win SBS 2003 R2, everything went
fine and other instances (SHAREPOINT & SBSMONITORING) are working as well.
The only thing and the most important that should be working but not, is
application that uses SQL Server as it's main database. Before this, the
application used SQL Server 2000 and working fine.
Everytime users launch the application, there's this error message: "Error
in DataAccessLayer.DataAccess.CheckUserLogin. Login failed for user 'sa'."
Although I've allowed Windows Authentication & SQL Server authentication in
SQL Server 2005 logins settings, that error message will still appears and
restrict any users to log-in to the application.
That application uses a "DataAccessLayer.config" file that has this
parameters:
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<appSettings>
<add key="UseWebService" value="false"/>
<add key="DAL.DataService.DataService" value="http://companyweb"/>
<add key="DBCnnString" value="Persist Security Info=False;User
ID=sa;Password=;Initial Catalog=INVENTORY;Data Source=192.168.16.2"/>
<add key="server" value="ServerName"/>
<add key="database" value="INVENTORY"/>
<add key="uid" value="sa"/>
<add key="password" value=""/>
</appSettings>
</configuration>
What happened? Have anyone encountered the same symtomps/problem and know
how to work around it?
Please be noted, I attach this "INVENTORY" database into
ServerName\Database; I do not use instances for it.
Thank you, all help is appreciated.ON the Security tab, change to [SQL Server and Windows Authentication].
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Dhow" <Dhow@.discussions.microsoft.com> wrote in message
news:9114C9D0-F787-41A2-B2A1-9B84FA635F1B@.microsoft.com...
> Hi,
> I've just installed SQL Server 2005 into Win SBS 2003 R2, everything went
> fine and other instances (SHAREPOINT & SBSMONITORING) are working as well.
> The only thing and the most important that should be working but not, is
> application that uses SQL Server as it's main database. Before this, the
> application used SQL Server 2000 and working fine.
> Everytime users launch the application, there's this error message: "Error
> in DataAccessLayer.DataAccess.CheckUserLogin. Login failed for user
> 'sa'."
> Although I've allowed Windows Authentication & SQL Server authentication
> in
> SQL Server 2005 logins settings, that error message will still appears and
> restrict any users to log-in to the application.
> That application uses a "DataAccessLayer.config" file that has this
> parameters:
> <?xml version="1.0" encoding="utf-8"?>
> <configuration>
> <appSettings>
> <add key="UseWebService" value="false"/>
> <add key="DAL.DataService.DataService" value="http://companyweb"/>
> <add key="DBCnnString" value="Persist Security Info=False;User
> ID=sa;Password=;Initial Catalog=INVENTORY;Data Source=192.168.16.2"/>
> <add key="server" value="ServerName"/>
> <add key="database" value="INVENTORY"/>
> <add key="uid" value="sa"/>
> <add key="password" value=""/>
> </appSettings>
> </configuration>
> What happened? Have anyone encountered the same symtomps/problem and know
> how to work around it?
> Please be noted, I attach this "INVENTORY" database into
> ServerName\Database; I do not use instances for it.
> Thank you, all help is appreciated.|||And did you really install SQL 2005 without a password for the [sa] acco
unt?
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Dhow" <Dhow@.discussions.microsoft.com> wrote in message
news:9114C9D0-F787-41A2-B2A1-9B84FA635F1B@.microsoft.com...
> Hi,
> I've just installed SQL Server 2005 into Win SBS 2003 R2, everything went
> fine and other instances (SHAREPOINT & SBSMONITORING) are working as well.
> The only thing and the most important that should be working but not, is
> application that uses SQL Server as it's main database. Before this, the
> application used SQL Server 2000 and working fine.
> Everytime users launch the application, there's this error message: "Error
> in DataAccessLayer.DataAccess.CheckUserLogin. Login failed for user
> 'sa'."
> Although I've allowed Windows Authentication & SQL Server authentication
> in
> SQL Server 2005 logins settings, that error message will still appears and
> restrict any users to log-in to the application.
> That application uses a "DataAccessLayer.config" file that has this
> parameters:
> <?xml version="1.0" encoding="utf-8"?>
> <configuration>
> <appSettings>
> <add key="UseWebService" value="false"/>
> <add key="DAL.DataService.DataService" value="http://companyweb"/>
> <add key="DBCnnString" value="Persist Security Info=False;User
> ID=sa;Password=;Initial Catalog=INVENTORY;Data Source=192.168.16.2"/>
> <add key="server" value="ServerName"/>
> <add key="database" value="INVENTORY"/>
> <add key="uid" value="sa"/>
> <add key="password" value=""/>
> </appSettings>
> </configuration>
> What happened? Have anyone encountered the same symtomps/problem and know
> how to work around it?
> Please be noted, I attach this "INVENTORY" database into
> ServerName\Database; I do not use instances for it.
> Thank you, all help is appreciated.|||Dhow wrote:
> Hi,
> I've just installed SQL Server 2005 into Win SBS 2003 R2, everything went
> fine and other instances (SHAREPOINT & SBSMONITORING) are working as well.
> The only thing and the most important that should be working but not, is
> application that uses SQL Server as it's main database. Before this, the
> application used SQL Server 2000 and working fine.
> Everytime users launch the application, there's this error message: "Error
> in DataAccessLayer.DataAccess.CheckUserLogin. Login failed for user 'sa'.
"
> Although I've allowed Windows Authentication & SQL Server authentication i
n
> SQL Server 2005 logins settings, that error message will still appears and
> restrict any users to log-in to the application.
> That application uses a "DataAccessLayer.config" file that has this
> parameters:
> <?xml version="1.0" encoding="utf-8"?>
> <configuration>
> <appSettings>
> <add key="UseWebService" value="false"/>
> <add key="DAL.DataService.DataService" value="http://companyweb"/>
> <add key="DBCnnString" value="Persist Security Info=False;User
> ID=sa;Password=;Initial Catalog=INVENTORY;Data Source=192.168.16.2"/>
> <add key="server" value="ServerName"/>
> <add key="database" value="INVENTORY"/>
> <add key="uid" value="sa"/>
> <add key="password" value=""/>
> </appSettings>
> </configuration>
> What happened? Have anyone encountered the same symtomps/problem and know
> how to work around it?
> Please be noted, I attach this "INVENTORY" database into
> ServerName\Database; I do not use instances for it.
> Thank you, all help is appreciated.
You are trying to connect to the server using the "sa" login, with no
password!!! You have two problems here:
1. Never, ever, purposely allow an application to connect as "sa", you
need to tightly control the use of this login.
2. If you purposely installed SQL Server with a blank password for
"sa", change it, now. Your server is wide open to anybody who chooses
to login as "sa".
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Arnie,
When I installed the SQL Server 2005 for Default Database, I use Windows
Authentication and Local System.
Is there a way to know whether the [sa] has blank password or not?
Further notice: I tried to input [sa] password, and I use the same passw
ord
in "DataAccessLayer.config" under "Password=" value; but it still won't work
.
The error message is still the same as before.
Any other suggestions perhaps?
Thanks!
"Arnie Rowland" wrote:
> And did you really install SQL 2005 without a password for the [sa] ac
count?
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "Dhow" <Dhow@.discussions.microsoft.com> wrote in message
> news:9114C9D0-F787-41A2-B2A1-9B84FA635F1B@.microsoft.com...
>
>|||Arnie,
When I installed the SQL Server 2005 for Default Database, I use Windows
Authentication and Local System.
Is there a way to know whether the [sa] has blank password or not?
Further notice: I tried to input [sa] password, and I use the same passw
ord
in "DataAccessLayer.config" under "Password=" value; but it still won't work
.
The error message is still the same as before.
Any other suggestions perhaps?
Thanks!
"Arnie Rowland" wrote:
> And did you really install SQL 2005 without a password for the [sa] ac
count?
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "Dhow" <Dhow@.discussions.microsoft.com> wrote in message
> news:9114C9D0-F787-41A2-B2A1-9B84FA635F1B@.microsoft.com...
>
>|||Arnie,
When I installed the SQL Server 2005 for Default Database, I use Windows
Authentication and Local System.
Is there a way to know whether the [sa] has blank password or not?
Further notice: I tried to input [sa] password, and I use the same passw
ord
in "DataAccessLayer.config" under "Password=" value; but it still won't work
.
The error message is still the same as before.
Any other suggestions perhaps?
Thanks!
"Arnie Rowland" wrote:
> And did you really install SQL 2005 without a password for the [sa] ac
count?
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "Dhow" <Dhow@.discussions.microsoft.com> wrote in message
> news:9114C9D0-F787-41A2-B2A1-9B84FA635F1B@.microsoft.com...
>
>|||Arnie,
When I installed the SQL Server 2005 for Default Database, I use Windows
Authentication and Local System.
Is there a way to know whether the [sa] has blank password or not?
Further notice: I tried to input [sa] password, and I use the same passw
ord
in "DataAccessLayer.config" under "Password=" value; but it still won't work
.
The error message is still the same as before.
Any other suggestions perhaps?
Thanks!
"Arnie Rowland" wrote:
> And did you really install SQL 2005 without a password for the [sa] ac
count?
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "Dhow" <Dhow@.discussions.microsoft.com> wrote in message
> news:9114C9D0-F787-41A2-B2A1-9B84FA635F1B@.microsoft.com...
>
>|||Arnie,
When I installed the SQL Server 2005 for Default Database, I use Windows
Authentication and Local System.
Is there a way to know whether the [sa] has blank password or not?
Further notice: I tried to input [sa] password, and I use the same passw
ord
in "DataAccessLayer.config" under "Password=" value; but it still won't work
.
The error message is still the same as before.
Any other suggestions perhaps?
Thanks!
"Arnie Rowland" wrote:
> And did you really install SQL 2005 without a password for the [sa] ac
count?
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "Dhow" <Dhow@.discussions.microsoft.com> wrote in message
> news:9114C9D0-F787-41A2-B2A1-9B84FA635F1B@.microsoft.com...
>
>|||Tracy,
I know I input blank password for [sa] user, but that was only for a try
out.
Later on after everything works fine, I'll input new password into it.
When I installed the SQL Server 2005 for Default Database, I use Windows
Authentication and Local System.
Is there a way to know whether the [sa] has blank password or not?
Further notice: I tried to input [sa] password, and I use the same passw
ord
in "DataAccessLayer.config" under "Password=" value; but it still won't work
.
The error message is still the same as before.
Any other usefull sugesstions?
Thanks!
"Tracy McKibben" wrote:
> Dhow wrote:
> You are trying to connect to the server using the "sa" login, with no
> password!!! You have two problems here:
> 1. Never, ever, purposely allow an application to connect as "sa", you
> need to tightly control the use of this login.
> 2. If you purposely installed SQL Server with a blank password for
> "sa", change it, now. Your server is wide open to anybody who chooses
> to login as "sa".
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>
I've just installed SQL Server 2005 into Win SBS 2003 R2, everything went
fine and other instances (SHAREPOINT & SBSMONITORING) are working as well.
The only thing and the most important that should be working but not, is
application that uses SQL Server as it's main database. Before this, the
application used SQL Server 2000 and working fine.
Everytime users launch the application, there's this error message: "Error
in DataAccessLayer.DataAccess.CheckUserLogin. Login failed for user 'sa'."
Although I've allowed Windows Authentication & SQL Server authentication in
SQL Server 2005 logins settings, that error message will still appears and
restrict any users to log-in to the application.
That application uses a "DataAccessLayer.config" file that has this
parameters:
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<appSettings>
<add key="UseWebService" value="false"/>
<add key="DAL.DataService.DataService" value="http://companyweb"/>
<add key="DBCnnString" value="Persist Security Info=False;User
ID=sa;Password=;Initial Catalog=INVENTORY;Data Source=192.168.16.2"/>
<add key="server" value="ServerName"/>
<add key="database" value="INVENTORY"/>
<add key="uid" value="sa"/>
<add key="password" value=""/>
</appSettings>
</configuration>
What happened? Have anyone encountered the same symtomps/problem and know
how to work around it?
Please be noted, I attach this "INVENTORY" database into
ServerName\Database; I do not use instances for it.
Thank you, all help is appreciated.ON the Security tab, change to [SQL Server and Windows Authentication].
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Dhow" <Dhow@.discussions.microsoft.com> wrote in message
news:9114C9D0-F787-41A2-B2A1-9B84FA635F1B@.microsoft.com...
> Hi,
> I've just installed SQL Server 2005 into Win SBS 2003 R2, everything went
> fine and other instances (SHAREPOINT & SBSMONITORING) are working as well.
> The only thing and the most important that should be working but not, is
> application that uses SQL Server as it's main database. Before this, the
> application used SQL Server 2000 and working fine.
> Everytime users launch the application, there's this error message: "Error
> in DataAccessLayer.DataAccess.CheckUserLogin. Login failed for user
> 'sa'."
> Although I've allowed Windows Authentication & SQL Server authentication
> in
> SQL Server 2005 logins settings, that error message will still appears and
> restrict any users to log-in to the application.
> That application uses a "DataAccessLayer.config" file that has this
> parameters:
> <?xml version="1.0" encoding="utf-8"?>
> <configuration>
> <appSettings>
> <add key="UseWebService" value="false"/>
> <add key="DAL.DataService.DataService" value="http://companyweb"/>
> <add key="DBCnnString" value="Persist Security Info=False;User
> ID=sa;Password=;Initial Catalog=INVENTORY;Data Source=192.168.16.2"/>
> <add key="server" value="ServerName"/>
> <add key="database" value="INVENTORY"/>
> <add key="uid" value="sa"/>
> <add key="password" value=""/>
> </appSettings>
> </configuration>
> What happened? Have anyone encountered the same symtomps/problem and know
> how to work around it?
> Please be noted, I attach this "INVENTORY" database into
> ServerName\Database; I do not use instances for it.
> Thank you, all help is appreciated.|||And did you really install SQL 2005 without a password for the [sa] acco
unt?
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Dhow" <Dhow@.discussions.microsoft.com> wrote in message
news:9114C9D0-F787-41A2-B2A1-9B84FA635F1B@.microsoft.com...
> Hi,
> I've just installed SQL Server 2005 into Win SBS 2003 R2, everything went
> fine and other instances (SHAREPOINT & SBSMONITORING) are working as well.
> The only thing and the most important that should be working but not, is
> application that uses SQL Server as it's main database. Before this, the
> application used SQL Server 2000 and working fine.
> Everytime users launch the application, there's this error message: "Error
> in DataAccessLayer.DataAccess.CheckUserLogin. Login failed for user
> 'sa'."
> Although I've allowed Windows Authentication & SQL Server authentication
> in
> SQL Server 2005 logins settings, that error message will still appears and
> restrict any users to log-in to the application.
> That application uses a "DataAccessLayer.config" file that has this
> parameters:
> <?xml version="1.0" encoding="utf-8"?>
> <configuration>
> <appSettings>
> <add key="UseWebService" value="false"/>
> <add key="DAL.DataService.DataService" value="http://companyweb"/>
> <add key="DBCnnString" value="Persist Security Info=False;User
> ID=sa;Password=;Initial Catalog=INVENTORY;Data Source=192.168.16.2"/>
> <add key="server" value="ServerName"/>
> <add key="database" value="INVENTORY"/>
> <add key="uid" value="sa"/>
> <add key="password" value=""/>
> </appSettings>
> </configuration>
> What happened? Have anyone encountered the same symtomps/problem and know
> how to work around it?
> Please be noted, I attach this "INVENTORY" database into
> ServerName\Database; I do not use instances for it.
> Thank you, all help is appreciated.|||Dhow wrote:
> Hi,
> I've just installed SQL Server 2005 into Win SBS 2003 R2, everything went
> fine and other instances (SHAREPOINT & SBSMONITORING) are working as well.
> The only thing and the most important that should be working but not, is
> application that uses SQL Server as it's main database. Before this, the
> application used SQL Server 2000 and working fine.
> Everytime users launch the application, there's this error message: "Error
> in DataAccessLayer.DataAccess.CheckUserLogin. Login failed for user 'sa'.
"
> Although I've allowed Windows Authentication & SQL Server authentication i
n
> SQL Server 2005 logins settings, that error message will still appears and
> restrict any users to log-in to the application.
> That application uses a "DataAccessLayer.config" file that has this
> parameters:
> <?xml version="1.0" encoding="utf-8"?>
> <configuration>
> <appSettings>
> <add key="UseWebService" value="false"/>
> <add key="DAL.DataService.DataService" value="http://companyweb"/>
> <add key="DBCnnString" value="Persist Security Info=False;User
> ID=sa;Password=;Initial Catalog=INVENTORY;Data Source=192.168.16.2"/>
> <add key="server" value="ServerName"/>
> <add key="database" value="INVENTORY"/>
> <add key="uid" value="sa"/>
> <add key="password" value=""/>
> </appSettings>
> </configuration>
> What happened? Have anyone encountered the same symtomps/problem and know
> how to work around it?
> Please be noted, I attach this "INVENTORY" database into
> ServerName\Database; I do not use instances for it.
> Thank you, all help is appreciated.
You are trying to connect to the server using the "sa" login, with no
password!!! You have two problems here:
1. Never, ever, purposely allow an application to connect as "sa", you
need to tightly control the use of this login.
2. If you purposely installed SQL Server with a blank password for
"sa", change it, now. Your server is wide open to anybody who chooses
to login as "sa".
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Arnie,
When I installed the SQL Server 2005 for Default Database, I use Windows
Authentication and Local System.
Is there a way to know whether the [sa] has blank password or not?
Further notice: I tried to input [sa] password, and I use the same passw
ord
in "DataAccessLayer.config" under "Password=" value; but it still won't work
.
The error message is still the same as before.
Any other suggestions perhaps?
Thanks!
"Arnie Rowland" wrote:
> And did you really install SQL 2005 without a password for the [sa] ac
count?
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "Dhow" <Dhow@.discussions.microsoft.com> wrote in message
> news:9114C9D0-F787-41A2-B2A1-9B84FA635F1B@.microsoft.com...
>
>|||Arnie,
When I installed the SQL Server 2005 for Default Database, I use Windows
Authentication and Local System.
Is there a way to know whether the [sa] has blank password or not?
Further notice: I tried to input [sa] password, and I use the same passw
ord
in "DataAccessLayer.config" under "Password=" value; but it still won't work
.
The error message is still the same as before.
Any other suggestions perhaps?
Thanks!
"Arnie Rowland" wrote:
> And did you really install SQL 2005 without a password for the [sa] ac
count?
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "Dhow" <Dhow@.discussions.microsoft.com> wrote in message
> news:9114C9D0-F787-41A2-B2A1-9B84FA635F1B@.microsoft.com...
>
>|||Arnie,
When I installed the SQL Server 2005 for Default Database, I use Windows
Authentication and Local System.
Is there a way to know whether the [sa] has blank password or not?
Further notice: I tried to input [sa] password, and I use the same passw
ord
in "DataAccessLayer.config" under "Password=" value; but it still won't work
.
The error message is still the same as before.
Any other suggestions perhaps?
Thanks!
"Arnie Rowland" wrote:
> And did you really install SQL 2005 without a password for the [sa] ac
count?
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "Dhow" <Dhow@.discussions.microsoft.com> wrote in message
> news:9114C9D0-F787-41A2-B2A1-9B84FA635F1B@.microsoft.com...
>
>|||Arnie,
When I installed the SQL Server 2005 for Default Database, I use Windows
Authentication and Local System.
Is there a way to know whether the [sa] has blank password or not?
Further notice: I tried to input [sa] password, and I use the same passw
ord
in "DataAccessLayer.config" under "Password=" value; but it still won't work
.
The error message is still the same as before.
Any other suggestions perhaps?
Thanks!
"Arnie Rowland" wrote:
> And did you really install SQL 2005 without a password for the [sa] ac
count?
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "Dhow" <Dhow@.discussions.microsoft.com> wrote in message
> news:9114C9D0-F787-41A2-B2A1-9B84FA635F1B@.microsoft.com...
>
>|||Arnie,
When I installed the SQL Server 2005 for Default Database, I use Windows
Authentication and Local System.
Is there a way to know whether the [sa] has blank password or not?
Further notice: I tried to input [sa] password, and I use the same passw
ord
in "DataAccessLayer.config" under "Password=" value; but it still won't work
.
The error message is still the same as before.
Any other suggestions perhaps?
Thanks!
"Arnie Rowland" wrote:
> And did you really install SQL 2005 without a password for the [sa] ac
count?
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "Dhow" <Dhow@.discussions.microsoft.com> wrote in message
> news:9114C9D0-F787-41A2-B2A1-9B84FA635F1B@.microsoft.com...
>
>|||Tracy,
I know I input blank password for [sa] user, but that was only for a try
out.
Later on after everything works fine, I'll input new password into it.
When I installed the SQL Server 2005 for Default Database, I use Windows
Authentication and Local System.
Is there a way to know whether the [sa] has blank password or not?
Further notice: I tried to input [sa] password, and I use the same passw
ord
in "DataAccessLayer.config" under "Password=" value; but it still won't work
.
The error message is still the same as before.
Any other usefull sugesstions?
Thanks!
"Tracy McKibben" wrote:
> Dhow wrote:
> You are trying to connect to the server using the "sa" login, with no
> password!!! You have two problems here:
> 1. Never, ever, purposely allow an application to connect as "sa", you
> need to tightly control the use of this login.
> 2. If you purposely installed SQL Server with a blank password for
> "sa", change it, now. Your server is wide open to anybody who chooses
> to login as "sa".
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>
Monday, March 19, 2012
Failed install of SQL Server 2005 Developer Edition on Win XP Pro
I've tried installing SQL Server 2005 Developer Edition 3 times now, from 2 different CDs. I keep failing with the same error message: "SQL Server Setup Failed to compile the Managed Object Format (MOF) file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\etwcls.mof. To proceed, see "Troubleshooting an Installation of SQL Server 2005" or "How to: View SQL Server 2005 Setup Log Files" in SQL Server 2005 Setup Help documentation."
This is the bottom of the SQLSetup0001_<machine name>_SQL.log
Doing Action: Do_sqlMofcomp
PerfTime Start: Do_sqlMofcomp : Fri Jan 27 14:33:07 2006
<Func Name='InstallMOF'>
Failed to compile file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\etwcls.mof.
An error occured while processing item 1 defined on lines 16 - 18
Error occured in phase 3, Error number: 0x80041001
Compiler returned error 0x80041001
<EndFunc Name='InstallMOF' Return='-2147217407' GetLastError='183'>
Error Code: 0x80077349 (29513)
Windows Error Text:Source File Name: sqlca\sqlmofca.cpp
Compiler Timestamp: Tue Aug9 01:14:18 2005
Function Name: Do_sqlMofcomp
Source Line Number: 608
- Context --
Setting status of unmanaged components and removing unmanaged resources
Error Code: 29513
MSI (s) (40!00) [14:40:59:034]: Product: Microsoft SQL Server 2005 -- Error 29513. SQL Server Setup Failed to compile the Managed Object Format (MOF) file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\etwcls.mof. To proceed, see "Troubleshooting an Installation of SQL Server 2005" or "How to: View SQL Server 2005 Setup Log Files" in SQL Server 2005 Setup Help documentation.
Error 29513. SQL Server Setup Failed to compile the Managed Object Format (MOF) file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\etwcls.mof. To proceed, see "Troubleshooting an Installation of SQL Server 2005" or "How to: View SQL Server 2005 Setup Log Files" in SQL Server 2005 Setup Help documentation.
<Func Name='GetCAContext'>
<EndFunc Name='GetCAContext' Return='T' GetLastError='203'>
Doing Action: Do_sqlMofcomp
PerfTime Start: Do_sqlMofcomp : Fri Jan 27 14:40:59 2006
<Func Name='InstallMOF'>
Failed to compile file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\etwcls.mof.
An error occured while processing item 1 defined on lines 16 - 18
Error occured in phase 3, Error number: 0x80041001
Compiler returned error 0x80041001
<EndFunc Name='InstallMOF' Return='-2147217407' GetLastError='183'>
Error Code: 0x80077349 (29513)
Windows Error Text:Source File Name: sqlca\sqlmofca.cpp
Compiler Timestamp: Tue Aug9 01:14:18 2005
Function Name: Do_sqlMofcomp
Source Line Number: 608
- Context --
Setting status of unmanaged components and removing unmanaged resources
Error Code: 29513
I'm at a complete loss, but I am sure the error is something about the configuration with this computer. I have fond a couple of posts on other web sites where people have similar errors, but no feedback on the error or even ideas on what to look at.
ANY recommendations would be helpful!!
Thank you,
Jay A. Moritz
I had the same error. Turns out my WMI repository is corrupted.
Run the following in a batch file to rebuild the repository and fix the problem:
net stop winmgmt
c:
cd %systemroot%\system32\wbem
rd /S /Q repository
regsvr32 /s %systemroot%\system32\scecli.dll
regsvr32 /s %systemroot%\system32\userenv.dll
mofcomp cimwin32.mof
mofcomp cimwin32.mfl
mofcomp rsop.mof
mofcomp rsop.mfl
for /f %%s in ('dir /b /s *.dll') do regsvr32 /s %%s
for /f %%s in ('dir /b *.mof') do mofcomp %%s
for /f %%s in ('dir /b *.mfl') do mofcomp %%s
echo DONE reboot
pause
Hello, I'm having hte same issue...
How do I run in a batch?....Does this mean something is wrong with my XP....If I installed a new version of XP, would this fix the problem?
|||This is most likely caused by a corruption in WMI in your Windows Server. Try reinstalling WMI. There's information on how to do this at: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wmisdk/wmi/reinstalling_wmi.asp
Thanks,
Samuel Lester (MSFT)
Strange, that page looks to be down now. Here is a WMI diagnosis tool you can also try:
http://www.microsoft.com/downloads/details.aspx?familyid=d7ba3cd6-18d1-4d05-b11e-4c64192ae97d&displaylang=en
Thanks,
Sam Lester (MSFT)
I received the same error.
Thanks !!! this was useful for me !
Emil
|||
Would like to thank you. This solution worked for me.
Thanks
|||The WMI Diagnostic utility provided only unhelpful information. The batch file provided above fixed the WMI problem and allowed the SQL Server 2005 installation to complete under Vista.
To run the text as a batch file, just copy and paste it into notepad, save it somewhere with a .bat extension, and then run it from a command (DOS) window
Failed install of SQL Server 2005 Developer Edition on Win XP Pro
I've tried installing SQL Server 2005 Developer Edition 3 times now, from 2 different CDs. I keep failing with the same error message: "SQL Server Setup Failed to compile the Managed Object Format (MOF) file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\etwcls.mof. To proceed, see "Troubleshooting an Installation of SQL Server 2005" or "How to: View SQL Server 2005 Setup Log Files" in SQL Server 2005 Setup Help documentation."
This is the bottom of the SQLSetup0001_<machine name>_SQL.log
Doing Action: Do_sqlMofcomp
PerfTime Start: Do_sqlMofcomp : Fri Jan 27 14:33:07 2006
<Func Name='InstallMOF'>
Failed to compile file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\etwcls.mof.
An error occured while processing item 1 defined on lines 16 - 18
Error occured in phase 3, Error number: 0x80041001
Compiler returned error 0x80041001
<EndFunc Name='InstallMOF' Return='-2147217407' GetLastError='183'>
Error Code: 0x80077349 (29513)
Windows Error Text:Source File Name: sqlca\sqlmofca.cpp
Compiler Timestamp: Tue Aug9 01:14:18 2005
Function Name: Do_sqlMofcomp
Source Line Number: 608
- Context --
Setting status of unmanaged components and removing unmanaged resources
Error Code: 29513
MSI (s) (40!00) [14:40:59:034]: Product: Microsoft SQL Server 2005 -- Error 29513. SQL Server Setup Failed to compile the Managed Object Format (MOF) file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\etwcls.mof. To proceed, see "Troubleshooting an Installation of SQL Server 2005" or "How to: View SQL Server 2005 Setup Log Files" in SQL Server 2005 Setup Help documentation.
Error 29513. SQL Server Setup Failed to compile the Managed Object Format (MOF) file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\etwcls.mof. To proceed, see "Troubleshooting an Installation of SQL Server 2005" or "How to: View SQL Server 2005 Setup Log Files" in SQL Server 2005 Setup Help documentation.
<Func Name='GetCAContext'>
<EndFunc Name='GetCAContext' Return='T' GetLastError='203'>
Doing Action: Do_sqlMofcomp
PerfTime Start: Do_sqlMofcomp : Fri Jan 27 14:40:59 2006
<Func Name='InstallMOF'>
Failed to compile file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\etwcls.mof.
An error occured while processing item 1 defined on lines 16 - 18
Error occured in phase 3, Error number: 0x80041001
Compiler returned error 0x80041001
<EndFunc Name='InstallMOF' Return='-2147217407' GetLastError='183'>
Error Code: 0x80077349 (29513)
Windows Error Text:Source File Name: sqlca\sqlmofca.cpp
Compiler Timestamp: Tue Aug9 01:14:18 2005
Function Name: Do_sqlMofcomp
Source Line Number: 608
- Context --
Setting status of unmanaged components and removing unmanaged resources
Error Code: 29513
I'm at a complete loss, but I am sure the error is something about the configuration with this computer. I have fond a couple of posts on other web sites where people have similar errors, but no feedback on the error or even ideas on what to look at.
ANY recommendations would be helpful!!
Thank you,
Jay A. Moritz
I had the same error. Turns out my WMI repository is corrupted.
Run the following in a batch file to rebuild the repository and fix the problem:
net stop winmgmt
c:
cd %systemroot%\system32\wbem
rd /S /Q repository
regsvr32 /s %systemroot%\system32\scecli.dll
regsvr32 /s %systemroot%\system32\userenv.dll
mofcomp cimwin32.mof
mofcomp cimwin32.mfl
mofcomp rsop.mof
mofcomp rsop.mfl
for /f %%s in ('dir /b /s *.dll') do regsvr32 /s %%s
for /f %%s in ('dir /b *.mof') do mofcomp %%s
for /f %%s in ('dir /b *.mfl') do mofcomp %%s
echo DONE reboot
pause
Hello, I'm having hte same issue...
How do I run in a batch?....Does this mean something is wrong with my XP....If I installed a new version of XP, would this fix the problem?
|||This is most likely caused by a corruption in WMI in your Windows Server. Try reinstalling WMI. There's information on how to do this at: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wmisdk/wmi/reinstalling_wmi.asp
Thanks,
Samuel Lester (MSFT)
Strange, that page looks to be down now. Here is a WMI diagnosis tool you can also try:
http://www.microsoft.com/downloads/details.aspx?familyid=d7ba3cd6-18d1-4d05-b11e-4c64192ae97d&displaylang=en
Thanks,
Sam Lester (MSFT)
I received the same error.
Thanks !!! this was useful for me !
Emil
|||Would like to thank you. This solution worked for me.
Thanks
|||The WMI Diagnostic utility provided only unhelpful information. The batch file provided above fixed the WMI problem and allowed the SQL Server 2005 installation to complete under Vista.
To run the text as a batch file, just copy and paste it into notepad, save it somewhere with a .bat extension, and then run it from a command (DOS) window
Failed install of SQL Server 2005 Developer Edition on Win XP Pro
I've tried installing SQL Server 2005 Developer Edition 3 times now, from 2 different CDs. I keep failing with the same error message: "SQL Server Setup Failed to compile the Managed Object Format (MOF) file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\etwcls.mof. To proceed, see "Troubleshooting an Installation of SQL Server 2005" or "How to: View SQL Server 2005 Setup Log Files" in SQL Server 2005 Setup Help documentation."
This is the bottom of the SQLSetup0001_<machine name>_SQL.log
Doing Action: Do_sqlMofcomp
PerfTime Start: Do_sqlMofcomp : Fri Jan 27 14:33:07 2006
<Func Name='InstallMOF'>
Failed to compile file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\etwcls.mof.
An error occured while processing item 1 defined on lines 16 - 18
Error occured in phase 3, Error number: 0x80041001
Compiler returned error 0x80041001
<EndFunc Name='InstallMOF' Return='-2147217407' GetLastError='183'>
Error Code: 0x80077349 (29513)
Windows Error Text:Source File Name: sqlca\sqlmofca.cpp
Compiler Timestamp: Tue Aug9 01:14:18 2005
Function Name: Do_sqlMofcomp
Source Line Number: 608
- Context --
Setting status of unmanaged components and removing unmanaged resources
Error Code: 29513
MSI (s) (40!00) [14:40:59:034]: Product: Microsoft SQL Server 2005 -- Error 29513. SQL Server Setup Failed to compile the Managed Object Format (MOF) file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\etwcls.mof. To proceed, see "Troubleshooting an Installation of SQL Server 2005" or "How to: View SQL Server 2005 Setup Log Files" in SQL Server 2005 Setup Help documentation.
Error 29513. SQL Server Setup Failed to compile the Managed Object Format (MOF) file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\etwcls.mof. To proceed, see "Troubleshooting an Installation of SQL Server 2005" or "How to: View SQL Server 2005 Setup Log Files" in SQL Server 2005 Setup Help documentation.
<Func Name='GetCAContext'>
<EndFunc Name='GetCAContext' Return='T' GetLastError='203'>
Doing Action: Do_sqlMofcomp
PerfTime Start: Do_sqlMofcomp : Fri Jan 27 14:40:59 2006
<Func Name='InstallMOF'>
Failed to compile file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\etwcls.mof.
An error occured while processing item 1 defined on lines 16 - 18
Error occured in phase 3, Error number: 0x80041001
Compiler returned error 0x80041001
<EndFunc Name='InstallMOF' Return='-2147217407' GetLastError='183'>
Error Code: 0x80077349 (29513)
Windows Error Text:Source File Name: sqlca\sqlmofca.cpp
Compiler Timestamp: Tue Aug9 01:14:18 2005
Function Name: Do_sqlMofcomp
Source Line Number: 608
- Context --
Setting status of unmanaged components and removing unmanaged resources
Error Code: 29513
I'm at a complete loss, but I am sure the error is something about the configuration with this computer. I have fond a couple of posts on other web sites where people have similar errors, but no feedback on the error or even ideas on what to look at.
ANY recommendations would be helpful!!
Thank you,
Jay A. Moritz
I had the same error. Turns out my WMI repository is corrupted.
Run the following in a batch file to rebuild the repository and fix the problem:
net stop winmgmt
c:
cd %systemroot%\system32\wbem
rd /S /Q repository
regsvr32 /s %systemroot%\system32\scecli.dll
regsvr32 /s %systemroot%\system32\userenv.dll
mofcomp cimwin32.mof
mofcomp cimwin32.mfl
mofcomp rsop.mof
mofcomp rsop.mfl
for /f %%s in ('dir /b /s *.dll') do regsvr32 /s %%s
for /f %%s in ('dir /b *.mof') do mofcomp %%s
for /f %%s in ('dir /b *.mfl') do mofcomp %%s
echo DONE reboot
pause
Hello, I'm having hte same issue...
How do I run in a batch?....Does this mean something is wrong with my XP....If I installed a new version of XP, would this fix the problem?
|||This is most likely caused by a corruption in WMI in your Windows Server. Try reinstalling WMI. There's information on how to do this at: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wmisdk/wmi/reinstalling_wmi.asp
Thanks,
Samuel Lester (MSFT)
Strange, that page looks to be down now. Here is a WMI diagnosis tool you can also try:
http://www.microsoft.com/downloads/details.aspx?familyid=d7ba3cd6-18d1-4d05-b11e-4c64192ae97d&displaylang=en
Thanks,
Sam Lester (MSFT)
I received the same error.
Thanks !!! this was useful for me !
Emil
|||Would like to thank you. This solution worked for me.
Thanks
|||The WMI Diagnostic utility provided only unhelpful information. The batch file provided above fixed the WMI problem and allowed the SQL Server 2005 installation to complete under Vista.
To run the text as a batch file, just copy and paste it into notepad, save it somewhere with a .bat extension, and then run it from a command (DOS) window
Failed install of SQL Server 2005 Developer Edition on Win XP Pro
I've tried installing SQL Server 2005 Developer Edition 3 times now, from 2 different CDs. I keep failing with the same error message: "SQL Server Setup Failed to compile the Managed Object Format (MOF) file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\etwcls.mof. To proceed, see "Troubleshooting an Installation of SQL Server 2005" or "How to: View SQL Server 2005 Setup Log Files" in SQL Server 2005 Setup Help documentation."
This is the bottom of the SQLSetup0001_<machine name>_SQL.log
Doing Action: Do_sqlMofcomp
PerfTime Start: Do_sqlMofcomp : Fri Jan 27 14:33:07 2006
<Func Name='InstallMOF'>
Failed to compile file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\etwcls.mof.
An error occured while processing item 1 defined on lines 16 - 18
Error occured in phase 3, Error number: 0x80041001
Compiler returned error 0x80041001
<EndFunc Name='InstallMOF' Return='-2147217407' GetLastError='183'>
Error Code: 0x80077349 (29513)
Windows Error Text:Source File Name: sqlca\sqlmofca.cpp
Compiler Timestamp: Tue Aug9 01:14:18 2005
Function Name: Do_sqlMofcomp
Source Line Number: 608
- Context --
Setting status of unmanaged components and removing unmanaged resources
Error Code: 29513
MSI (s) (40!00) [14:40:59:034]: Product: Microsoft SQL Server 2005 -- Error 29513. SQL Server Setup Failed to compile the Managed Object Format (MOF) file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\etwcls.mof. To proceed, see "Troubleshooting an Installation of SQL Server 2005" or "How to: View SQL Server 2005 Setup Log Files" in SQL Server 2005 Setup Help documentation.
Error 29513. SQL Server Setup Failed to compile the Managed Object Format (MOF) file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\etwcls.mof. To proceed, see "Troubleshooting an Installation of SQL Server 2005" or "How to: View SQL Server 2005 Setup Log Files" in SQL Server 2005 Setup Help documentation.
<Func Name='GetCAContext'>
<EndFunc Name='GetCAContext' Return='T' GetLastError='203'>
Doing Action: Do_sqlMofcomp
PerfTime Start: Do_sqlMofcomp : Fri Jan 27 14:40:59 2006
<Func Name='InstallMOF'>
Failed to compile file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\etwcls.mof.
An error occured while processing item 1 defined on lines 16 - 18
Error occured in phase 3, Error number: 0x80041001
Compiler returned error 0x80041001
<EndFunc Name='InstallMOF' Return='-2147217407' GetLastError='183'>
Error Code: 0x80077349 (29513)
Windows Error Text:Source File Name: sqlca\sqlmofca.cpp
Compiler Timestamp: Tue Aug9 01:14:18 2005
Function Name: Do_sqlMofcomp
Source Line Number: 608
- Context --
Setting status of unmanaged components and removing unmanaged resources
Error Code: 29513
I'm at a complete loss, but I am sure the error is something about the configuration with this computer. I have fond a couple of posts on other web sites where people have similar errors, but no feedback on the error or even ideas on what to look at.
ANY recommendations would be helpful!!
Thank you,
Jay A. Moritz
I had the same error. Turns out my WMI repository is corrupted.
Run the following in a batch file to rebuild the repository and fix the problem:
net stop winmgmt
c:
cd %systemroot%\system32\wbem
rd /S /Q repository
regsvr32 /s %systemroot%\system32\scecli.dll
regsvr32 /s %systemroot%\system32\userenv.dll
mofcomp cimwin32.mof
mofcomp cimwin32.mfl
mofcomp rsop.mof
mofcomp rsop.mfl
for /f %%s in ('dir /b /s *.dll') do regsvr32 /s %%s
for /f %%s in ('dir /b *.mof') do mofcomp %%s
for /f %%s in ('dir /b *.mfl') do mofcomp %%s
echo DONE reboot
pause
Hello, I'm having hte same issue...
How do I run in a batch?....Does this mean something is wrong with my XP....If I installed a new version of XP, would this fix the problem?
|||This is most likely caused by a corruption in WMI in your Windows Server. Try reinstalling WMI. There's information on how to do this at: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wmisdk/wmi/reinstalling_wmi.asp
Thanks,
Samuel Lester (MSFT)
Strange, that page looks to be down now. Here is a WMI diagnosis tool you can also try:
http://www.microsoft.com/downloads/details.aspx?familyid=d7ba3cd6-18d1-4d05-b11e-4c64192ae97d&displaylang=en
Thanks,
Sam Lester (MSFT)
I received the same error.
Thanks !!! this was useful for me !
Emil
|||
Would like to thank you. This solution worked for me.
Thanks
|||The WMI Diagnostic utility provided only unhelpful information. The batch file provided above fixed the WMI problem and allowed the SQL Server 2005 installation to complete under Vista.
To run the text as a batch file, just copy and paste it into notepad, save it somewhere with a .bat extension, and then run it from a command (DOS) window
Failed install of SQL Server 2005 Developer Edition on Win XP Pro
I've tried installing SQL Server 2005 Developer Edition 3 times now, from 2 different CDs. I keep failing with the same error message: "SQL Server Setup Failed to compile the Managed Object Format (MOF) file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\etwcls.mof. To proceed, see "Troubleshooting an Installation of SQL Server 2005" or "How to: View SQL Server 2005 Setup Log Files" in SQL Server 2005 Setup Help documentation."
This is the bottom of the SQLSetup0001_<machine name>_SQL.log
Doing Action: Do_sqlMofcomp
PerfTime Start: Do_sqlMofcomp : Fri Jan 27 14:33:07 2006
<Func Name='InstallMOF'>
Failed to compile file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\etwcls.mof.
An error occured while processing item 1 defined on lines 16 - 18
Error occured in phase 3, Error number: 0x80041001
Compiler returned error 0x80041001
<EndFunc Name='InstallMOF' Return='-2147217407' GetLastError='183'>
Error Code: 0x80077349 (29513)
Windows Error Text:Source File Name: sqlca\sqlmofca.cpp
Compiler Timestamp: Tue Aug9 01:14:18 2005
Function Name: Do_sqlMofcomp
Source Line Number: 608
- Context --
Setting status of unmanaged components and removing unmanaged resources
Error Code: 29513
MSI (s) (40!00) [14:40:59:034]: Product: Microsoft SQL Server 2005 -- Error 29513. SQL Server Setup Failed to compile the Managed Object Format (MOF) file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\etwcls.mof. To proceed, see "Troubleshooting an Installation of SQL Server 2005" or "How to: View SQL Server 2005 Setup Log Files" in SQL Server 2005 Setup Help documentation.
Error 29513. SQL Server Setup Failed to compile the Managed Object Format (MOF) file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\etwcls.mof. To proceed, see "Troubleshooting an Installation of SQL Server 2005" or "How to: View SQL Server 2005 Setup Log Files" in SQL Server 2005 Setup Help documentation.
<Func Name='GetCAContext'>
<EndFunc Name='GetCAContext' Return='T' GetLastError='203'>
Doing Action: Do_sqlMofcomp
PerfTime Start: Do_sqlMofcomp : Fri Jan 27 14:40:59 2006
<Func Name='InstallMOF'>
Failed to compile file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\etwcls.mof.
An error occured while processing item 1 defined on lines 16 - 18
Error occured in phase 3, Error number: 0x80041001
Compiler returned error 0x80041001
<EndFunc Name='InstallMOF' Return='-2147217407' GetLastError='183'>
Error Code: 0x80077349 (29513)
Windows Error Text:Source File Name: sqlca\sqlmofca.cpp
Compiler Timestamp: Tue Aug9 01:14:18 2005
Function Name: Do_sqlMofcomp
Source Line Number: 608
- Context --
Setting status of unmanaged components and removing unmanaged resources
Error Code: 29513
I'm at a complete loss, but I am sure the error is something about the configuration with this computer. I have fond a couple of posts on other web sites where people have similar errors, but no feedback on the error or even ideas on what to look at.
ANY recommendations would be helpful!!
Thank you,
Jay A. Moritz
I had the same error. Turns out my WMI repository is corrupted.
Run the following in a batch file to rebuild the repository and fix the problem:
net stop winmgmt
c:
cd %systemroot%\system32\wbem
rd /S /Q repository
regsvr32 /s %systemroot%\system32\scecli.dll
regsvr32 /s %systemroot%\system32\userenv.dll
mofcomp cimwin32.mof
mofcomp cimwin32.mfl
mofcomp rsop.mof
mofcomp rsop.mfl
for /f %%s in ('dir /b /s *.dll') do regsvr32 /s %%s
for /f %%s in ('dir /b *.mof') do mofcomp %%s
for /f %%s in ('dir /b *.mfl') do mofcomp %%s
echo DONE reboot
pause
Hello, I'm having hte same issue...
How do I run in a batch?....Does this mean something is wrong with my XP....If I installed a new version of XP, would this fix the problem?
|||This is most likely caused by a corruption in WMI in your Windows Server. Try reinstalling WMI. There's information on how to do this at: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wmisdk/wmi/reinstalling_wmi.asp
Thanks,
Samuel Lester (MSFT)
Strange, that page looks to be down now. Here is a WMI diagnosis tool you can also try:
http://www.microsoft.com/downloads/details.aspx?familyid=d7ba3cd6-18d1-4d05-b11e-4c64192ae97d&displaylang=en
Thanks,
Sam Lester (MSFT)
I received the same error.
Thanks !!! this was useful for me !
Emil
|||
Would like to thank you. This solution worked for me.
Thanks
|||The WMI Diagnostic utility provided only unhelpful information. The batch file provided above fixed the WMI problem and allowed the SQL Server 2005 installation to complete under Vista.
To run the text as a batch file, just copy and paste it into notepad, save it somewhere with a .bat extension, and then run it from a command (DOS) window
Failed install of SQL Server 2005 Developer Edition on Win XP Pro
I've tried installing SQL Server 2005 Developer Edition 3 times now, from 2 different CDs. I keep failing with the same error message: "SQL Server Setup Failed to compile the Managed Object Format (MOF) file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\etwcls.mof. To proceed, see "Troubleshooting an Installation of SQL Server 2005" or "How to: View SQL Server 2005 Setup Log Files" in SQL Server 2005 Setup Help documentation."
This is the bottom of the SQLSetup0001_<machine name>_SQL.log
Doing Action: Do_sqlMofcomp
PerfTime Start: Do_sqlMofcomp : Fri Jan 27 14:33:07 2006
<Func Name='InstallMOF'>
Failed to compile file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\etwcls.mof.
An error occured while processing item 1 defined on lines 16 - 18
Error occured in phase 3, Error number: 0x80041001
Compiler returned error 0x80041001
<EndFunc Name='InstallMOF' Return='-2147217407' GetLastError='183'>
Error Code: 0x80077349 (29513)
Windows Error Text:Source File Name: sqlca\sqlmofca.cpp
Compiler Timestamp: Tue Aug9 01:14:18 2005
Function Name: Do_sqlMofcomp
Source Line Number: 608
- Context --
Setting status of unmanaged components and removing unmanaged resources
Error Code: 29513
MSI (s) (40!00) [14:40:59:034]: Product: Microsoft SQL Server 2005 -- Error 29513. SQL Server Setup Failed to compile the Managed Object Format (MOF) file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\etwcls.mof. To proceed, see "Troubleshooting an Installation of SQL Server 2005" or "How to: View SQL Server 2005 Setup Log Files" in SQL Server 2005 Setup Help documentation.
Error 29513. SQL Server Setup Failed to compile the Managed Object Format (MOF) file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\etwcls.mof. To proceed, see "Troubleshooting an Installation of SQL Server 2005" or "How to: View SQL Server 2005 Setup Log Files" in SQL Server 2005 Setup Help documentation.
<Func Name='GetCAContext'>
<EndFunc Name='GetCAContext' Return='T' GetLastError='203'>
Doing Action: Do_sqlMofcomp
PerfTime Start: Do_sqlMofcomp : Fri Jan 27 14:40:59 2006
<Func Name='InstallMOF'>
Failed to compile file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\etwcls.mof.
An error occured while processing item 1 defined on lines 16 - 18
Error occured in phase 3, Error number: 0x80041001
Compiler returned error 0x80041001
<EndFunc Name='InstallMOF' Return='-2147217407' GetLastError='183'>
Error Code: 0x80077349 (29513)
Windows Error Text:Source File Name: sqlca\sqlmofca.cpp
Compiler Timestamp: Tue Aug9 01:14:18 2005
Function Name: Do_sqlMofcomp
Source Line Number: 608
- Context --
Setting status of unmanaged components and removing unmanaged resources
Error Code: 29513
I'm at a complete loss, but I am sure the error is something about the configuration with this computer. I have fond a couple of posts on other web sites where people have similar errors, but no feedback on the error or even ideas on what to look at.
ANY recommendations would be helpful!!
Thank you,
Jay A. Moritz
I had the same error. Turns out my WMI repository is corrupted.
Run the following in a batch file to rebuild the repository and fix the problem:
net stop winmgmt
c:
cd %systemroot%\system32\wbem
rd /S /Q repository
regsvr32 /s %systemroot%\system32\scecli.dll
regsvr32 /s %systemroot%\system32\userenv.dll
mofcomp cimwin32.mof
mofcomp cimwin32.mfl
mofcomp rsop.mof
mofcomp rsop.mfl
for /f %%s in ('dir /b /s *.dll') do regsvr32 /s %%s
for /f %%s in ('dir /b *.mof') do mofcomp %%s
for /f %%s in ('dir /b *.mfl') do mofcomp %%s
echo DONE reboot
pause
Hello, I'm having hte same issue...
How do I run in a batch?....Does this mean something is wrong with my XP....If I installed a new version of XP, would this fix the problem?
|||This is most likely caused by a corruption in WMI in your Windows Server. Try reinstalling WMI. There's information on how to do this at: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wmisdk/wmi/reinstalling_wmi.asp
Thanks,
Samuel Lester (MSFT)
Strange, that page looks to be down now. Here is a WMI diagnosis tool you can also try:
http://www.microsoft.com/downloads/details.aspx?familyid=d7ba3cd6-18d1-4d05-b11e-4c64192ae97d&displaylang=en
Thanks,
Sam Lester (MSFT)
I received the same error.
Thanks !!! this was useful for me !
Emil
|||Would like to thank you. This solution worked for me.
Thanks
|||The WMI Diagnostic utility provided only unhelpful information. The batch file provided above fixed the WMI problem and allowed the SQL Server 2005 installation to complete under Vista.
To run the text as a batch file, just copy and paste it into notepad, save it somewhere with a .bat extension, and then run it from a command (DOS) window
Subscribe to:
Posts (Atom)