sir,
kindly solve the error.When I do a database updation in the
ejbcreate function the driver is working properly but when
I tried to use a user defined function I am thrown an the
exception listed below.This means that teh classpath
settings are fine .Probably the access writes are not
defined properly so I am posting you server.policy file
also just in case there is some problem.
=20
java.sql.SQLException: [Microsoft][SQLServer 2000 Driver
for JDBC]Can't start a
cloned connection while in manual transaction mode.
at
com.microsoft.jdbc.base.BaseExceptions.createExcep tion(Unknown
Source
)
at
com.microsoft.jdbc.base.BaseExceptions.getExceptio n(Unknown
Source)
at
com.microsoft.jdbc.base.BaseConnection.getImplConn ection(Unknown
Sour
ce)
at
com.microsoft.jdbc.base.BaseStatement.setupImplCon nection(Unknown
Sou
rce)
at com.microsoft.jdbc.base.BaseStatement.<init>(Unkno wn Source)
at
com.microsoft.jdbc.base.BasePreparedStatement.<ini t>(Unknown
Source)
at
com.microsoft.jdbc.base.BaseConnection.prepareStat ement(Unknown
Sourc
e)
at
com.microsoft.jdbc.base.BaseConnection.prepareStat ement(Unknown
Sourc
e)
at
com.sun.enterprise.resource.JdbcXAConnection$JdbcC onnection.prepareSt
atement(JdbcXAConnection.java:263)
at Loginsessionbean.checklogin(Loginsessionbean.java: 36)
at
Loginsessionbean_EJBObjectImpl.checklogin(Loginses sionbean_EJBObjectI
mpl.java:19)
at _Loginsessionbean_EJBObjectImpl_Tie._invoke(Unknow n Source)
at
com.sun.corba.ee.internal.POA.GenericPOAServerSC.d ispatchToServant(Ge
nericPOAServerSC.java:423)
at
com.sun.corba.ee.internal.POA.GenericPOAServerSC.i nternalDispatch(Gen
ericPOAServerSC.java:137)
at
com.sun.corba.ee.internal.POA.GenericPOAServerSC.d ispatch(GenericPOAS
erverSC.java:98)
at com.sun.corba.ee.internal.iiop.ORB.process(ORB.jav a:227)
at
com.sun.corba.ee.internal.iiop.LocalClientRequestI mpl.invoke(LocalCli
entRequestImpl.java:90)
at
com.sun.corba.ee.internal.POA.GenericPOAClientSC.i nvoke(GenericPOACli
entSC.java:142)
at
com.sun.corba.ee.internal.POA.GenericPOAClientSC.i nvoke(GenericPOACli
entSC.java:183)
at
org.omg.CORBA.portable.ObjectImpl._invoke(ObjectIm pl.java:297)
at _Loginsessionremote_Stub.checklogin(Unknown Source)
at Loginbean.getLogin(Loginbean.java:34)
at
javaproject.login._0005cjavaproject_0005clogin_000 5clogin_0002ejsplog
in_jsp_1._jspService(_0005cjavaproject_0005clogin_ 0005clogin_0002ejsplogi=
n_jsp_1
..java:140)
at
org.apache.jasper.runtime.HttpJspBase.service(Http JspBase.java:126)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:865)
at
org.apache.jasper.runtime.JspServlet$JspServletWra pper.service(JspSer
vlet.java:161)
at
org.apache.jasper.runtime.JspServlet.serviceJspFil e(JspServlet.java:2
47)
at
org.apache.jasper.runtime.JspServlet.service(JspSe rvlet.java:352)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:865)
at
org.apache.tomcat.core.ServiceInvocationHandler.me thod(ServletWrapper
..java:626)
at
org.apache.tomcat.core.ServletWrapper.handleInvoca tion(ServletWrapper
..java:534)
at
org.apache.tomcat.core.ServletWrapper.handleReques t(ServletWrapper.ja
va:378)
at
org.apache.tomcat.core.Context.handleRequest(Conte xt.java:644)
at
org.apache.tomcat.core.ContextManager.service(Cont extManager.java:440
)
at
org.apache.tomcat.service.http.HttpConnectionHandl er.processConnectio
n(HttpConnectionHandler.java:144)
at
org.apache.tomcat.service.TcpConnectionThread.run( TcpEndpoint.java:31
0)
at java.lang.Thread.run(Thread.java:484)
Loginsessionbean.java
import javax.ejb.*;
import java.util.*;
import java.sql.*;
import javax.sql.*;
import javax.naming.*;
import javax.transaction.*;
import java.rmi.RemoteException;
public class Loginsessionbean implements SessionBean
{
private Connection con;
public void ejbCreate() throws CreateException ,
RemoteException ,SQLException , NamingException
{
try
{
InitialContext ic =3D new InitialContext();
DataSource ds =3D
(DataSource)ic.lookup("java:comp/env/jdbc/master");
con =3D ds.getConnection();
}
catch(Exception ex)
{
throw new CreateException(ex.getMessage());
}
}
public String checklogin(String login,String password)
throws RemoteException , SQLException , NamingException ,
CreateException
{
String selectstatement=3D"select * from table1 where login =3D?
and password =3D ?";
ResultSet result;
try
{
PreparedStatement prep =3D con.prepareStatement(selectstatement);
prep.setString(1,login);
prep.setString(2,password);
result =3D prep.executeQuery();
if(result.next()=3D=3D true)
{
prep.close();
return(null);
}
}
catch(SQLException ex)
{
ex.printStackTrace();
}
return "login is correct";
}
public void ejbRemove(){}
public void ejbActivate(){}
public void ejbPassivate(){}
public void setSessionContext(SessionContext session){}
}
server.policy
// Standard extensions get all permissions by default
grant codeBase "file:${java.home}/lib/ext/-" {
permission java.security.AllPermission;
};
grant codeBase "file:${java.home}/../lib/tools.jar" {
permission java.security.AllPermission;
};
grant codeBase "file:${com.sun.enterprise.home}/lib/classes/" {
permission java.security.AllPermission;
};
// Drivers and other system classes should be stored in this
// code base.
grant codeBase "file:${com.sun.enterprise.home}/lib/system/-" {
permission java.security.AllPermission;
};
grant codeBase
"file:${com.sun.enterprise.home}/public_html/-" {
permission java.lang.RuntimePermission "loadLibrary.*";
permission java.lang.RuntimePermission
"accessClassInPackage.*";
permission java.lang.RuntimePermission "queuePrintJob";
permission java.lang.RuntimePermission "modifyThreadGroup";
permission java.io.FilePermission "<<ALL FILES>>",
"read,write";
permission java.net.SocketPermission "*", "connect";
// "standard" properies that can be read by anyone
permission java.util.PropertyPermission "*", "read";
// set the JSSE provider for lazy authentication of app.
clients.
permission java.security.SecurityPermission
"putProviderProperty.JSSE";
permission java.security.SecurityPermission
"insertProvider.JSSE";
};
grant codeBase "file:${com.sun.enterprise.home}/lib/j2ee.jar" {
permission java.security.AllPermission;
};
// default permissions granted to all domains
grant {
permission java.lang.RuntimePermission "queuePrintJob";
// Additional properties needed RI...
permission java.io.FilePermission "*", "read";
permission java.io.FilePermission
"${com.sun.enterprise.home}${file.separator}-", "read";
permission java.io.FilePermission
"${com.sun.enterprise.home}${file.separator}reposi tory${file.separator}-"=
,
"read,write,delete";
permission java.io.FilePermission
"${com.sun.enterprise.home}${file.separator}logs${ file.separator}-",
"read,write,delete";
permission java.io.FilePermission
"${java.io.tmpdir}${file.separator}-", "read,write,delete";
permission java.io.FilePermission
"${user.home}${file.separator}-", "read,write,delete";
// allows anyone to listen on un-privileged ports
permission java.net.SocketPermission "*:0-65535", "connect";
// "standard" properies that can be read by anyone
permission java.util.PropertyPermission "*", "read";
// A version of Merant driver needs this permission.
// permission java.io.FilePermission "<<ALL FILES>>", "read";
// permission java.lang.RuntimePermission "modifyThreadGroup";
};
// permissions granted to all domains
grant {
permission java.lang.RuntimePermission "modifyThread";
permission java.lang.RuntimePermission "modifyThreadGroup";
// DataSource access
permission java.io.FilePermission "<<ALL FILES>>","read,write";
permission java.util.PropertyPermission "java.naming.*",
"read,write";
// Adjust the server host specification for your environment
permission java.net.SocketPermission
"*.microsoft.com:0-65535", "connect";
};
rajat agrawal wrote:
> sir,
> kindly solve the error.When I do a database updation in the
> ejbcreate function the driver is working properly but when
> I tried to use a user defined function I am thrown an the
> exception listed below.This means that teh classpath
> settings are fine .Probably the access writes are not
> defined properly so I am posting you server.policy file
> also just in case there is some problem.
>
Hi. Add a property to the jdbc connection request: selectMethod=cursor
Joe Weinstein at BEA
>
> java.sql.SQLException: [Microsoft][SQLServer 2000 Driver
> for JDBC]Can't start a
> cloned connection while in manual transaction mode.
> at
> com.microsoft.jdbc.base.BaseExceptions.createExcep tion(Unknown
> Source
> )
> at
> com.microsoft.jdbc.base.BaseExceptions.getExceptio n(Unknown
> Source)
> at
> com.microsoft.jdbc.base.BaseConnection.getImplConn ection(Unknown
> Sour
> ce)
> at
> com.microsoft.jdbc.base.BaseStatement.setupImplCon nection(Unknown
> Sou
> rce)
> at com.microsoft.jdbc.base.BaseStatement.<init>(Unkno wn Source)
> at
> com.microsoft.jdbc.base.BasePreparedStatement.<ini t>(Unknown
> Source)
> at
> com.microsoft.jdbc.base.BaseConnection.prepareStat ement(Unknown
> Sourc
> e)
> at
> com.microsoft.jdbc.base.BaseConnection.prepareStat ement(Unknown
> Sourc
> e)
> at
> com.sun.enterprise.resource.JdbcXAConnection$JdbcC onnection.prepareSt
> atement(JdbcXAConnection.java:263)
> at Loginsessionbean.checklogin(Loginsessionbean.java: 36)
> at
> Loginsessionbean_EJBObjectImpl.checklogin(Loginses sionbean_EJBObjectI
> mpl.java:19)
> at _Loginsessionbean_EJBObjectImpl_Tie._invoke(Unknow n Source)
> at
> com.sun.corba.ee.internal.POA.GenericPOAServerSC.d ispatchToServant(Ge
> nericPOAServerSC.java:423)
> at
> com.sun.corba.ee.internal.POA.GenericPOAServerSC.i nternalDispatch(Gen
> ericPOAServerSC.java:137)
> at
> com.sun.corba.ee.internal.POA.GenericPOAServerSC.d ispatch(GenericPOAS
> erverSC.java:98)
> at com.sun.corba.ee.internal.iiop.ORB.process(ORB.jav a:227)
> at
> com.sun.corba.ee.internal.iiop.LocalClientRequestI mpl.invoke(LocalCli
> entRequestImpl.java:90)
> at
> com.sun.corba.ee.internal.POA.GenericPOAClientSC.i nvoke(GenericPOACli
> entSC.java:142)
> at
> com.sun.corba.ee.internal.POA.GenericPOAClientSC.i nvoke(GenericPOACli
> entSC.java:183)
> at
> org.omg.CORBA.portable.ObjectImpl._invoke(ObjectIm pl.java:297)
> at _Loginsessionremote_Stub.checklogin(Unknown Source)
> at Loginbean.getLogin(Loginbean.java:34)
> at
> javaproject.login._0005cjavaproject_0005clogin_000 5clogin_0002ejsplog
> in_jsp_1._jspService(_0005cjavaproject_0005clogin_ 0005clogin_0002ejsplogin_jsp_1
> .java:140)
> at
> org.apache.jasper.runtime.HttpJspBase.service(Http JspBase.java:126)
> at javax.servlet.http.HttpServlet.service(HttpServlet .java:865)
> at
> org.apache.jasper.runtime.JspServlet$JspServletWra pper.service(JspSer
> vlet.java:161)
> at
> org.apache.jasper.runtime.JspServlet.serviceJspFil e(JspServlet.java:2
> 47)
> at
> org.apache.jasper.runtime.JspServlet.service(JspSe rvlet.java:352)
> at javax.servlet.http.HttpServlet.service(HttpServlet .java:865)
> at
> org.apache.tomcat.core.ServiceInvocationHandler.me thod(ServletWrapper
> .java:626)
> at
> org.apache.tomcat.core.ServletWrapper.handleInvoca tion(ServletWrapper
> .java:534)
> at
> org.apache.tomcat.core.ServletWrapper.handleReques t(ServletWrapper.ja
> va:378)
> at
> org.apache.tomcat.core.Context.handleRequest(Conte xt.java:644)
> at
> org.apache.tomcat.core.ContextManager.service(Cont extManager.java:440
> )
> at
> org.apache.tomcat.service.http.HttpConnectionHandl er.processConnectio
> n(HttpConnectionHandler.java:144)
> at
> org.apache.tomcat.service.TcpConnectionThread.run( TcpEndpoint.java:31
> 0)
> at java.lang.Thread.run(Thread.java:484)
>
> Loginsessionbean.java
> import javax.ejb.*;
> import java.util.*;
> import java.sql.*;
> import javax.sql.*;
> import javax.naming.*;
> import javax.transaction.*;
> import java.rmi.RemoteException;
>
> public class Loginsessionbean implements SessionBean
> {
> private Connection con;
> public void ejbCreate() throws CreateException ,
> RemoteException ,SQLException , NamingException
> {
> try
> {
> InitialContext ic = new InitialContext();
> DataSource ds =
> (DataSource)ic.lookup("java:comp/env/jdbc/master");
> con = ds.getConnection();
> }
> catch(Exception ex)
> {
> throw new CreateException(ex.getMessage());
> }
> }
> public String checklogin(String login,String password)
> throws RemoteException , SQLException , NamingException ,
> CreateException
> {
> String selectstatement="select * from table1 where login =?
> and password = ?";
> ResultSet result;
> try
> {
> PreparedStatement prep = con.prepareStatement(selectstatement);
> prep.setString(1,login);
> prep.setString(2,password);
> result = prep.executeQuery();
> if(result.next()== true)
> {
> prep.close();
> return(null);
> }
> }
> catch(SQLException ex)
> {
> ex.printStackTrace();
> }
> return "login is correct";
> }
> public void ejbRemove(){}
> public void ejbActivate(){}
> public void ejbPassivate(){}
> public void setSessionContext(SessionContext session){}
> }
>
> server.policy
>
> // Standard extensions get all permissions by default
> grant codeBase "file:${java.home}/lib/ext/-" {
> permission java.security.AllPermission;
> };
> grant codeBase "file:${java.home}/../lib/tools.jar" {
> permission java.security.AllPermission;
> };
> grant codeBase "file:${com.sun.enterprise.home}/lib/classes/" {
> permission java.security.AllPermission;
> };
> // Drivers and other system classes should be stored in this
> // code base.
> grant codeBase "file:${com.sun.enterprise.home}/lib/system/-" {
> permission java.security.AllPermission;
> };
> grant codeBase
> "file:${com.sun.enterprise.home}/public_html/-" {
> permission java.lang.RuntimePermission "loadLibrary.*";
> permission java.lang.RuntimePermission
> "accessClassInPackage.*";
> permission java.lang.RuntimePermission "queuePrintJob";
> permission java.lang.RuntimePermission "modifyThreadGroup";
> permission java.io.FilePermission "<<ALL FILES>>",
> "read,write";
> permission java.net.SocketPermission "*", "connect";
> // "standard" properies that can be read by anyone
> permission java.util.PropertyPermission "*", "read";
> // set the JSSE provider for lazy authentication of app.
> clients.
> permission java.security.SecurityPermission
> "putProviderProperty.JSSE";
> permission java.security.SecurityPermission
> "insertProvider.JSSE";
> };
> grant codeBase "file:${com.sun.enterprise.home}/lib/j2ee.jar" {
> permission java.security.AllPermission;
> };
> // default permissions granted to all domains
> grant {
> permission java.lang.RuntimePermission "queuePrintJob";
> // Additional properties needed RI...
> permission java.io.FilePermission "*", "read";
> permission java.io.FilePermission
> "${com.sun.enterprise.home}${file.separator}-", "read";
> permission java.io.FilePermission
> "${com.sun.enterprise.home}${file.separator}reposi tory${file.separator}-",
> "read,write,delete";
> permission java.io.FilePermission
> "${com.sun.enterprise.home}${file.separator}logs${ file.separator}-",
> "read,write,delete";
> permission java.io.FilePermission
> "${java.io.tmpdir}${file.separator}-", "read,write,delete";
> permission java.io.FilePermission
> "${user.home}${file.separator}-", "read,write,delete";
> // allows anyone to listen on un-privileged ports
> permission java.net.SocketPermission "*:0-65535", "connect";
> // "standard" properies that can be read by anyone
> permission java.util.PropertyPermission "*", "read";
> // A version of Merant driver needs this permission.
> // permission java.io.FilePermission "<<ALL FILES>>", "read";
> // permission java.lang.RuntimePermission "modifyThreadGroup";
> };
> // permissions granted to all domains
> grant {
> permission java.lang.RuntimePermission "modifyThread";
> permission java.lang.RuntimePermission "modifyThreadGroup";
> // DataSource access
> permission java.io.FilePermission "<<ALL FILES>>","read,write";
> permission java.util.PropertyPermission "java.naming.*",
> "read,write";
> // Adjust the server host specification for your environment
> permission java.net.SocketPermission
> "*.microsoft.com:0-65535", "connect";
> };
|||Please see the below KB for detailed info:
313181 PRB: Cannot Start a Cloned Connection While in Manual Transaction
Mode
http://support.microsoft.com/?id=313181
Showing posts with label working. Show all posts
Showing posts with label working. Show all posts
Friday, March 30, 2012
Ive never been good with relationships
I'm having some trouble working out how to query some data. Rather than explain up front, here's some examples of what I want to achieve:
*******************************************************
I've got a structure which looks vaguely like this:
[ANCESTORS]
Grandparent
Parent
Child
If limit by grandparents, then I only get the lineage for that particular grandparent. I.e.:
SELECT *
FROM [ANCESTORS]
(some sortof joins here )
Where Grandparent.Name ='Cybill'
This would return all of the children of 'Cybill' and their children. Now, if I use the following query:
SELECT *
FROM [ANCESTORS]
(some sortof joins here )
Where Child.Name ='Jean'
This would return Jean's parents + the parents of Jean's parents (Jean's grandparents).
Likewise, if I enter:
SELECT *
FROM [ANCESTORS]
(some sortof joins here )
Where Parent.Name ='Ron'
Then I would get Ron's parents and also his children.
*******************************************************
So, as you can see, at first it appears that I'm after a LEFT JOIN - meaning that the grandparents don't need to have child records to be returned, but, then it turns out that I need INNER JOINS - to limit grandparents when I choose children.
Can anybody see my dilemma here?
Mark-up ASP.net posts here
MarkItUp.com... no. I don't. I've done something like this before with someone, and we didn't go about that method. :(
What's the problem with doing inner joins?|||Because, with Inner JOINs I am relying upon the existance of children to be able to return the grandparents.|||I actually have one table "Ancestors" and also a separate linking table which contains the relationships:
[Ancestors] ( id int, Name varchar )
[Relationships] ( id, fkid )
What I need to be able to do is to write a single query which can span "up to 7" lines of descendency, that is:
Great-Great-Great-Grandparent
Great-Great-Grandparent
Great-Great-Grandparent
Great-Grandparent
Grandparent
Parent
Child
I just have absolutely no idea how to write a single sql query which could filter on one or more levels but ensure referential integrity down the line. In other words, I can specify a child which would trace up the tree in a single line, or, specify a Great-Great-Great-Grandparent which would span out from a single point and would show all the way down to leaf nodes regardless of which level they finished at.|||Can we use a UDF? :-)|||Yes, I'm using SqlServer 2K.
I have finally tuned the stored procedure "program" enough to get my - previously 14 hour (give or take 100 milliseconds) - query down to sub-20 seconds. This is good enough to ship to the client so, I'm going to go with what I have for now.|||20 seconds? I'm still not believing that to be good enough. :) but if it's good enough for the client, it's good enough I guess.
If you're using any temp tables or what not, try indexing them before you apply data to them. I trimmed a procedure that executed in 12 seconds to 2.|||KraGiE, I agree, 20 seconds is a long time to wait, but, it's working so that's a much better position than I had 2 days ago.
I do have # temp tables, about 12 of them actually (more on that later), and my final optimization was to add indexes and optimization hints in the appropriate places, this reduced a 2 minute 20 second query to sub 30 seconds.
As for the 12 temp tables, this, to me was a fair indicator that the schema of the database was wrong to begin with so now, I 'm actually pushing to have the db schema altered too. I'm hoping that this will give me enough of a foothold to be able to achieve the necessary remaining improvements|||Personally, I'm a big fan of int based look up tables. :) Well, in cases like this, I'm fond of them because you can branch them out as far as you want without having just 'add a new field'.
I also think loops are my best friend when used properly.
What I meant by the indexes (if this is what you're doing already, then I'm a redundant moron) is ...
|||Yeh, that's pretty much what I'm doing already re: the indexes ( although who am I to call you a redundant moron :P ) except that I create the index only after population and, therefore also set the fill factor to 100% - but, for the purposes of an illustration, yes, that's pretty much what I do.|||awesome. In some cases, I'll put the index in before I start populating if the data's going to be enormous. It sets a bit faster from my experience.
SET NOCOUNT ONCREATE TABLE #TempTable
(
tableID int IDENTITY,
TableField varchar(50)
SomeOtherVar int
)
GOCREATE INDEX idx_Temp
ON #TempTable ( tableID )
GOINSERT INTO #TempTable
SELECT
TableID,
TableField,
SomeOtherVar
FROM
RealTable
-- WHERE Your CriteriaGO
-- Do Other Calculations
TRUNCATE TABLE #TempTable
DROP INDEX idx_Temp
DROP TABLE #TempTableGO
-- Yes Terri, I space my sql in procedures and QA this way normally, and I'm just lazy when I post here. :)
I've been told that SQL Server replication is buggy and unreliable
Hi, I've recently been told that SQL Server replication is buggy and unreliable. I find this very hard to believe. I'm working with a subcontractor in another state that is hosting a large DB for us. I want to replicate a read-only copy of the DB over
the internetl to our local site. They also tell me that it is difficult to recover when there is a problem with replication. I again find this hard to believe. The worst case it to re-snapshot.
I've been working with SQL Server since 2002, but not replication. I've found SQL Server to be very reliable and nice to work with.
I would greatly appreciate honest feedback.
Thanks very much,
Griff
Griff,
I've used it for 4 years and found it to be robust. I teach replication to
financial staff in London and it is widely used by insurance companies and
banks, which might make you feel more confident about its usefulness.
To be honest, almost always what I initially thought was a limitation in the
technology actually turned out to be me using the wrong implementation, or
not being aware of existing workarounds.
For someone getting started, BOL (and Hilary's upcoming books) should
provide the foundation needed to make correct choices. For troubleshooting
I'd advise anyone starting out to implement replication in as many different
ways as possible, see when you've broken it and then research this newsgroup
thoroughly.
HTH,
Paul Ibison
Also, I keep a scratchpad of errors/solutions I've seen, or read about and
tested at www.replicationanswers.com.
|||Griff,
I've used it for 4 years and found it to be robust. I teach replication to
financial staff in London and it is widely used by insurance companies and
banks, which might make you feel more confident about its usefulness.
To be honest, almost always what I initially thought was a limitation in the
technology actually turned out to be me using the wrong implementation, or
not being aware of existing workarounds.
For someone getting started, BOL (and Hilary's upcoming books) should
provide the foundation needed to make correct choices. For troubleshooting
I'd advise anyone starting out to implement replication in as many different
ways as possible, see when you've broken it and then research this newsgroup
thoroughly.
HTH,
Paul Ibison
Also, I keep a scratchpad of errors/solutions I've seen, or read about and
tested at www.replicationanswers.com.
|||Replication is not buggy per se.
the problem with replication is that it is depenedent on often reliable
links. Sometimes a LAN connection which is good enough for day to day use,
will turn out to be too unreliable or unstable for replication.
Replication is resilient to many errors, but not a poor connection.
Its akin to someone taking a gravel road and complaining about the car.
Another problem with replication is that it is a complex product that few
dba's really understand well.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:eI8AqChXEHA.384@.TK2MSFTNGP10.phx.gbl...
> Griff,
> I've used it for 4 years and found it to be robust. I teach replication to
> financial staff in London and it is widely used by insurance companies and
> banks, which might make you feel more confident about its usefulness.
> To be honest, almost always what I initially thought was a limitation in
the
> technology actually turned out to be me using the wrong implementation, or
> not being aware of existing workarounds.
> For someone getting started, BOL (and Hilary's upcoming books) should
> provide the foundation needed to make correct choices. For troubleshooting
> I'd advise anyone starting out to implement replication in as many
different
> ways as possible, see when you've broken it and then research this
newsgroup
> thoroughly.
> HTH,
> Paul Ibison
> Also, I keep a scratchpad of errors/solutions I've seen, or read about and
> tested at www.replicationanswers.com.
>
|||Replication is not buggy per se.
the problem with replication is that it is depenedent on often reliable
links. Sometimes a LAN connection which is good enough for day to day use,
will turn out to be too unreliable or unstable for replication.
Replication is resilient to many errors, but not a poor connection.
Its akin to someone taking a gravel road and complaining about the car.
Another problem with replication is that it is a complex product that few
dba's really understand well.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:eI8AqChXEHA.384@.TK2MSFTNGP10.phx.gbl...
> Griff,
> I've used it for 4 years and found it to be robust. I teach replication to
> financial staff in London and it is widely used by insurance companies and
> banks, which might make you feel more confident about its usefulness.
> To be honest, almost always what I initially thought was a limitation in
the
> technology actually turned out to be me using the wrong implementation, or
> not being aware of existing workarounds.
> For someone getting started, BOL (and Hilary's upcoming books) should
> provide the foundation needed to make correct choices. For troubleshooting
> I'd advise anyone starting out to implement replication in as many
different
> ways as possible, see when you've broken it and then research this
newsgroup
> thoroughly.
> HTH,
> Paul Ibison
> Also, I keep a scratchpad of errors/solutions I've seen, or read about and
> tested at www.replicationanswers.com.
>
the internetl to our local site. They also tell me that it is difficult to recover when there is a problem with replication. I again find this hard to believe. The worst case it to re-snapshot.
I've been working with SQL Server since 2002, but not replication. I've found SQL Server to be very reliable and nice to work with.
I would greatly appreciate honest feedback.
Thanks very much,
Griff
Griff,
I've used it for 4 years and found it to be robust. I teach replication to
financial staff in London and it is widely used by insurance companies and
banks, which might make you feel more confident about its usefulness.
To be honest, almost always what I initially thought was a limitation in the
technology actually turned out to be me using the wrong implementation, or
not being aware of existing workarounds.
For someone getting started, BOL (and Hilary's upcoming books) should
provide the foundation needed to make correct choices. For troubleshooting
I'd advise anyone starting out to implement replication in as many different
ways as possible, see when you've broken it and then research this newsgroup
thoroughly.
HTH,
Paul Ibison
Also, I keep a scratchpad of errors/solutions I've seen, or read about and
tested at www.replicationanswers.com.
|||Griff,
I've used it for 4 years and found it to be robust. I teach replication to
financial staff in London and it is widely used by insurance companies and
banks, which might make you feel more confident about its usefulness.
To be honest, almost always what I initially thought was a limitation in the
technology actually turned out to be me using the wrong implementation, or
not being aware of existing workarounds.
For someone getting started, BOL (and Hilary's upcoming books) should
provide the foundation needed to make correct choices. For troubleshooting
I'd advise anyone starting out to implement replication in as many different
ways as possible, see when you've broken it and then research this newsgroup
thoroughly.
HTH,
Paul Ibison
Also, I keep a scratchpad of errors/solutions I've seen, or read about and
tested at www.replicationanswers.com.
|||Replication is not buggy per se.
the problem with replication is that it is depenedent on often reliable
links. Sometimes a LAN connection which is good enough for day to day use,
will turn out to be too unreliable or unstable for replication.
Replication is resilient to many errors, but not a poor connection.
Its akin to someone taking a gravel road and complaining about the car.
Another problem with replication is that it is a complex product that few
dba's really understand well.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:eI8AqChXEHA.384@.TK2MSFTNGP10.phx.gbl...
> Griff,
> I've used it for 4 years and found it to be robust. I teach replication to
> financial staff in London and it is widely used by insurance companies and
> banks, which might make you feel more confident about its usefulness.
> To be honest, almost always what I initially thought was a limitation in
the
> technology actually turned out to be me using the wrong implementation, or
> not being aware of existing workarounds.
> For someone getting started, BOL (and Hilary's upcoming books) should
> provide the foundation needed to make correct choices. For troubleshooting
> I'd advise anyone starting out to implement replication in as many
different
> ways as possible, see when you've broken it and then research this
newsgroup
> thoroughly.
> HTH,
> Paul Ibison
> Also, I keep a scratchpad of errors/solutions I've seen, or read about and
> tested at www.replicationanswers.com.
>
|||Replication is not buggy per se.
the problem with replication is that it is depenedent on often reliable
links. Sometimes a LAN connection which is good enough for day to day use,
will turn out to be too unreliable or unstable for replication.
Replication is resilient to many errors, but not a poor connection.
Its akin to someone taking a gravel road and complaining about the car.
Another problem with replication is that it is a complex product that few
dba's really understand well.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:eI8AqChXEHA.384@.TK2MSFTNGP10.phx.gbl...
> Griff,
> I've used it for 4 years and found it to be robust. I teach replication to
> financial staff in London and it is widely used by insurance companies and
> banks, which might make you feel more confident about its usefulness.
> To be honest, almost always what I initially thought was a limitation in
the
> technology actually turned out to be me using the wrong implementation, or
> not being aware of existing workarounds.
> For someone getting started, BOL (and Hilary's upcoming books) should
> provide the foundation needed to make correct choices. For troubleshooting
> I'd advise anyone starting out to implement replication in as many
different
> ways as possible, see when you've broken it and then research this
newsgroup
> thoroughly.
> HTH,
> Paul Ibison
> Also, I keep a scratchpad of errors/solutions I've seen, or read about and
> tested at www.replicationanswers.com.
>
Monday, March 26, 2012
Iterate through a list of files with bcp
I have a folder full of date-stamped files: 010101.txt, 010201.txt,
010301.txt, etc.
I have a working bcp command that points to a specific file.
declare @.bcpCommand varchar(1000)
select @.bcpCommand = 'BCP "Import.dbo.NAV" in
"d:\folder\010101.txt" -c -T -t, -S "SERVER1\SERVER1"'
EXEC master.dbo.xp_cmdshell @.bcpCommand
How can I script the bcp command so it will import all files between say
010101 and 120105? Complicating factor; there are gaps in the sequence. Can
the script continue even if it doesn't find a file?
Alternatively, if it was possible to issue the bcp command against all files
in a folder no matter what the filename, that would work also.
This is a one-time data load with SQL Server 2000/SP4
Thanks to anyone who could help.For sake of simplicity, write a cursor script & get it off. Here is a quick
try:
DECLARE @.cmd VARCHAR(500), @.c VARCHAR(500)
CREATE TABLE #t ( c VARCHAR( 500 ) NOT NULL )
INSERT #t EXEC master.dbo.xp_cmdshell 'DIR d:\folder\*.txt /B'
DECLARE c CURSOR FOR SELECT f FROM #t
OPEN c
FETCH NEXT FROM c INTO @.c
WHILE @.@.FETCH_STATUS = 0
BEGIN
SET @.cmd = 'BCP "Import.dbo.NAV" in "d:\folder\' + @.c + '" -c -T -t, -S
"SERVER1\SERVER1"'
EXEC master.dbo.xp_cmdshell @.cmd
FETCH NEXT FROM c
END
CLOSE c
DEALLOCATE c
DROP TABLE #t ;
Anithsql
010301.txt, etc.
I have a working bcp command that points to a specific file.
declare @.bcpCommand varchar(1000)
select @.bcpCommand = 'BCP "Import.dbo.NAV" in
"d:\folder\010101.txt" -c -T -t, -S "SERVER1\SERVER1"'
EXEC master.dbo.xp_cmdshell @.bcpCommand
How can I script the bcp command so it will import all files between say
010101 and 120105? Complicating factor; there are gaps in the sequence. Can
the script continue even if it doesn't find a file?
Alternatively, if it was possible to issue the bcp command against all files
in a folder no matter what the filename, that would work also.
This is a one-time data load with SQL Server 2000/SP4
Thanks to anyone who could help.For sake of simplicity, write a cursor script & get it off. Here is a quick
try:
DECLARE @.cmd VARCHAR(500), @.c VARCHAR(500)
CREATE TABLE #t ( c VARCHAR( 500 ) NOT NULL )
INSERT #t EXEC master.dbo.xp_cmdshell 'DIR d:\folder\*.txt /B'
DECLARE c CURSOR FOR SELECT f FROM #t
OPEN c
FETCH NEXT FROM c INTO @.c
WHILE @.@.FETCH_STATUS = 0
BEGIN
SET @.cmd = 'BCP "Import.dbo.NAV" in "d:\folder\' + @.c + '" -c -T -t, -S
"SERVER1\SERVER1"'
EXEC master.dbo.xp_cmdshell @.cmd
FETCH NEXT FROM c
END
CLOSE c
DEALLOCATE c
DROP TABLE #t ;
Anithsql
Item not linked to dataset, and "table1" issue
Hi--
I have a report project in VS (2003). I have a report in that project that was working properly. I copied objects from that report to a new one and created a new dataset for the new report (under it's Data tab). Though both datasets (for each of the reports) seem healthy, i.e., they produce data when run, I am now experiencing the following problems:
1. In both reports, the datasets seem to be unlinked, somehow. I know this by right clicking on a field of the report, going to expressions, then selecting the Fields node. Instead of listing fields, as used to be the case, it now says "Report item not linked to a dataset."
2. If I attempt to preview either of the reports, I get an error that reads, "The table 'table1' refers to an invalid dataset name 'MedMgmt.' MedMgmt is the dataset name of the first report. I changed it to another name, but I still get the same message.
I have clicked and right-clicked everywhere and have not found a way to re-link the dataset to the report. Why Reporting Services can't figure out that the dataset in the report's Data tab is the dataset to link to is a point of deep annoyance, but whatever... If anyone can please help me solve these problems, I would be very grateful! Thank you!
I have exactly the same problem. Only way around it (for me) so far has been to build the report all over and let the wizard link it, then copy the elements 1 by 1 from original... real pain...
There's GOT to be a better way?
|||I think i know what it is. What is this object you are looking to link? If its a table, List, or Matrix : Right click the object (make sure the whole object is selected and click properties. if properties slides out Scroll down to "Dataset Name", there should be a drop down which all the datasets in your report. Select the one you are grabbing you attributes from. The reason your getting that error is, the object is linked to dataset names from your other report (since you copied them over). So you need to change the dataset names for each object. This is why it shows the name of your dataset from your other report.
IF the properties box opens up for the table/matrix/list , then you should see (3 textboxes down) "Dataset Name". if its empty or has something in it...i would click the dropdown anyways, and make sure the right dataset it selected.
I hope this helps!
Item not linked to dataset, and "table1" issue
Hi--
I have a report project in VS (2003). I have a report in that project that was working properly. I copied objects from that report to a new one and created a new dataset for the new report (under it's Data tab). Though both datasets (for each of the reports) seem healthy, i.e., they produce data when run, I am now experiencing the following problems:
1. In both reports, the datasets seem to be unlinked, somehow. I know this by right clicking on a field of the report, going to expressions, then selecting the Fields node. Instead of listing fields, as used to be the case, it now says "Report item not linked to a dataset."
2. If I attempt to preview either of the reports, I get an error that reads, "The table 'table1' refers to an invalid dataset name 'MedMgmt.' MedMgmt is the dataset name of the first report. I changed it to another name, but I still get the same message.
I have clicked and right-clicked everywhere and have not found a way to re-link the dataset to the report. Why Reporting Services can't figure out that the dataset in the report's Data tab is the dataset to link to is a point of deep annoyance, but whatever... If anyone can please help me solve these problems, I would be very grateful! Thank you!
I have exactly the same problem. Only way around it (for me) so far has been to build the report all over and let the wizard link it, then copy the elements 1 by 1 from original... real pain...
There's GOT to be a better way?
|||I think i know what it is. What is this object you are looking to link? If its a table, List, or Matrix : Right click the object (make sure the whole object is selected and click properties. if properties slides out Scroll down to "Dataset Name", there should be a drop down which all the datasets in your report. Select the one you are grabbing you attributes from. The reason your getting that error is, the object is linked to dataset names from your other report (since you copied them over). So you need to change the dataset names for each object. This is why it shows the name of your dataset from your other report.
IF the properties box opens up for the table/matrix/list , then you should see (3 textboxes down) "Dataset Name". if its empty or has something in it...i would click the dropdown anyways, and make sure the right dataset it selected.
I hope this helps!
Wednesday, March 21, 2012
issues with pull subscriptions
I have set up a pull subscription and nothing seems to come through although everything seems set up correctly. Push subscriptions are working just fine. Any thoughts why push subscriptions work and pull subscriptions do not?Is this transactional or merge? If it is transactional, have you rerun snapshot?|||
Hi Li
How do I re-run the snapshot?
Eytan
|||Please spend some time reading/learning Replication, then come back with any issues/questions. http://msdn2.microsoft.com/en-us/library/ms151734.aspx.
Monday, March 19, 2012
Issues on setting the table visibility using an expression
Hi team,
I'm working on Reporting service 2005. When I give an expression for visibility of a table in a report based on a parameter, the contents are coming in a single page and it is not based on the interactive size of the report. I want the data to be coming on different pages based on the interactive size of the page. If the visibility is set directly it works. Could you please help me to solve this issue?
Thanks in advance,
Minu
Hello,
I couldnt resolve this issue. Can you please tell whether its a known issue in reporting service?
Thanks,
Minu
Monday, March 12, 2012
Issue working with symmetric key for encryption
Please be gentle...I am very new to working with SQL.
I have the need to encrypt my columns in SQL 2005. I have created a symmetric key 'SecureKey' as well as a secure certificate 'SecureCert'
I have ran the script to create the key and the certificate successfully. When I run "select * sys.symmetic_keys;" the key shows up...when I run "select * sys.certificates;" the cert shows up.
Here is my issue, in the security folder under my database, these two things do not show up in the appropriate folders. Also when I run my encryption scripts, I am getting an error of
"msg 15151, Level 16, State 1, Line 3
cannot find the symmetric key 'SecureKey', because it does not exist or you do not have permission"
Am I missing something?
Thanks
Did you open the symmetric key before you encrypt data? If the symmetric key is not opened you wont be able to work with it ... anyway here's how it's supposed to be done: (I'm in work so i cant test if code is true but if something is screwed up go to this site:
http://blogs.msdn.com/lcris/search.aspx?q=encryption+sql+server+2005&p=1
this is where i got most of info when i started)
create database demo;
use demo;
-- create the database master key
--since you created certificate already then master key must be set already
create master key encryption by password = 'Pufd&s@.))%';
-- create a simple employee table
create table t_employees (id int primary key, name varchar(300), salary varbinary(300));
-- create a certificate to protect the symmetric key that will encrypt the data
-- the certificate will be encrypted by the database master key
create certificate cert_sk_admin with subject = 'Certificate for accessing symmetric keys - for use by admin';
-- create a key to protect the employee sensitive data, in this case - the salary
create symmetric key sk_employees with algorithm = triple_des encryption by certificate cert_sk_admin;
-- open the key so that we can use it
open symmetric key sk_employees decryption by certificate cert_sk_admin;
-- verify key was opened
select * from sys.openkeys;
-- insert some data
-- we will use the id as an authenticator value to tie the salary to the employee id
insert into t_employees(id, name,salary) values ( 1,'Alice Smith', encryptbykey(key_guid('sk_employees'), '$200000'));
insert into t_employees(id,name,salary) values (2, 'Bob Jones', encryptbykey(key_guid('sk_employees'), '$100000'));
-- see the result; salary is encrypted
select * from t_employees;
-- create a view to automatically do the decryption
-- note that when decrypting we specify that the id should be used as authenticator
create view v_employees as select id, name, convert(varchar(10), decryptbykey(salary)) as salary from t_employees;
-- create another view for charles that will automatically open the key using his certificate and do the decryption
create view v_employees_auto as select id, name, convert(varchar(10), decryptbykeyautocert(cert_id('cert_sk_charles'), salary)) as salary from t_employees;
-- see the result, the decrypted data is available
select * from v_employees;
-- now close the key
close all symmetric keys;
-- verify key was closed
select * from sys.openkeys;
-- use the view that will automatically open the key
select * from v_employees_auto;
-- note that the key is also automatically closed by the above query
-- it is only opened for the duration of the query
select * from sys.openkeys;
Something I have recently learned: if you are testing as a low privileged user, then you must grant privileges to that use to see the key and cert. Something like:
GRANT CONTROL ON CERTIFICATE::[cert_SecretTable_SecretData_Key] TO [user_low_priv]
GRANT VIEW DEFINITION ON SYMMETRIC KEY::[SecretTable_SecretData_Key] TO [user_low_priv]
I have read it is better to use a view, but am having some problems of my own...
this snippet is from
http://blogs.technet.com/keithcombs/archive/2005/11/24/415079.aspx
|||Thanks for the replies...I now have the key and cert where they belong and they have started working...after I installed SP2.
NOW, I have issues with my decryption. I have ran my scripts to encrypt the data and it is working. I also ran the script to decrypt, and it worked once. I have tried to repeat the process, but with no luck... when I run the decrypt scipt it returns nothing...not a null or anything. I don't understand.
Here is my encryption
I open the key and the certificate
SELECT * FROM dbo.database
GO
UPDATE database
SET Value = EncryptByKey(Key_GUID('KeyName'), Value);
GO
close symmetric key KeyName;
Now to decrypt
SELECT Value
AS 'Encrypted Value',
CONVERT(varchar, DecryptByKey(Value))
AS 'Decrypted Value'
FROM database;
CLOSE SYMMETRIC KEY KeyName;
|||Hi, it looks like you are closing your symmetric key after the encryption, which is good practice. To perform the decryption, however, you will need to re-open your symmetric key. Thus before you perform your SELECT, you should once again run the OPEN SYMMETRIC KEY ... statement.
Please let us know if you run into any trouble with this and we will try to answer any questions you have.
Thanks,
Sung
|||Sung,
Thanks for the reply...I am sorry, I just forgot to put that part of the script in there. I am opening and closing the Key on the decrypt also.
Ron
|||In:
SELECT Value
AS 'Encrypted Value',
CONVERT(varchar, DecryptByKey(Value))
AS 'Decrypted Value'
FROM database;
you need to specifi length of varchar like this:
CONVERT(varchar(50), DecryptByKey(Value))
or something...
Issue with SSIS Package Configurations in SqlServer
Hello everyone,
I am working on a SSIS project and I am facing an issue for getting the configuration settings of the package, once it is deployed and executed from SQL Server agent.
The package uses two configuration types: (listed bellow in the order they are appeared in the configuration editor)
Config1 - Xml configuration file - for storing the database connection string.
Config2 - SQL Server - for storing some user defined variables. It uses the same database as specified in Config1.
Everything works fine and the package uses the database configuration values as defined in Config2, if I execute it from Visual Studio,
However, the package doesn’t get the configuration settings from the database when I try to execute it as a SQL Agent job.
There aren’t any errors and the package executes all tasks successfully, using the connection object Config1 (the same we use to get the config parameters from the database) and the default values of the user defined variables.
It works ok, if I change Config2 to be of type XML configuration file.
There could be two problems:
1. SQL server agent doesn’t read the configuration from the database and I am not quite sure how to set this. In Agent/ Job step properties screen/ Configurations tab I can only browse for a config file. I can also use the command window and /CONFIGFILE option to specify xml file, but how to use it in a case of a database configuration? Is there a /CONFIGDATABSE option or /CONFIGFILE works with database connection as well. I tried with /CONFIGFILE and database connection, but it doesn’t seem to work.
2. SQL server agent doesn’t get the configurations in the specified order. In my case,
it could try to read Config2 first, but at that moment it doesn’t have the database connection from Config1 and it fails. Again, I am not sure how to set the sequence.
Thanks in advance for your comments.
ITHave you specified a full path for Config1?|||Yes, I specified the full path for Config1. I used the configuration tab to select the file and in the command line window it shows the full path.
The package itself uses the connection from Config1 for the data flow tasks and they work without any issues.
|||Hi,
What kind of user defined variables are you fetching from the database?
Can you try storing them in package level variables by using a Script Task?
Regards,
B@.ns
|||I think you can discard option 2. The package configurations should be processed in the order in which they are stored.
It sounds like a permissions problem with the SQl Server Agent account.
Have you tried profiling (SQL Profiler) the package execution to see if it is generating any SQL errors trying to read the configuration table? If the package fails to read the configuration, it only raises a warning, not an error, so it is not always obvious when a configuration fails to load.
|||I couldn’t find any errors or warnings during the package execution.
Moreover the same connection is used for all data flow tasks inside the package and the SSIS logging (it uses SSIS log provider for SQL) and all of them work without any issues.
As a workaround I can add a SQL script to read those variables from the database, but this will duplicate the configuration functionality.
The idea was to use the existing SSIS database configuration feature instead of building a similar one from scratch.
|||Are you changig the path of the Conf1 in Agent, different than one you have when building the package?|||I.T.See if you this blog spot can help you identifying the issue:
http://rafael-salas.blogspot.com/2007/01/ssis-package-configurations-using-sql.html
It uses an environment variable instead of a file|||
Hi Rafael,
I checked your blog (actually this was one of the first materials I found when I started exploring the issue a week ago), but in our case we have some system restrictions for using environment variables.
In your example you mentioned also that you used it successfully with XML file.
I would like to ask you if you were to deploy it and execute it as a SQL agent job?
Thanks,
IT
|||Yes, I did, and as far as I remember it worked ok. The only problems I can remember are stupid things like the XML file was not accessible for the account running the SS Agent; not updating the connection string properly withing the XML file (hence trying to connect to the wrong instance), etc. But most of the times, the package logging will tell you if something is wrong with any of the configurations and even shows the order in which the configurations were applied.|||Rafael,
I would like to ask you if you remember how you set the sql configuration in the SQL Agent job. Did you do something special for this?
I couldn’t see any available options to set explicitly the configuration as SQL server (the UI allows only to browse and select config file).
The package logging is set to log all events and it doesn’t show any errors during the execution.
You mentioned also that the package logging can tell the order of the configuration, but I couldn’t see that kind of information. Is there a special custom event for this?
Thanks,
IT
|||I just ran some tests using XML and Table configurations (in that order) and works fine in BIDS and as an agent job.
I didn't have to do any special thing in the job step (CmdExec); just to a command like:
DTEXEC /FILE "{path}\Configurations demo 2.dtsx" /MAXCONCURRENT " -1 " /CHECKPOINTING OFF /REPORTING EWCDI
But what I could notice is that the messages about package configurations are not shown in te progress tab; I recently updated to SP2, and I wonder if that has been changed. I dind't even received any warning when I deliberated removed the xml config file...not even in the package logging|||
I. T. wrote:
I couldn’t find any errors or warnings during the package execution.
This is normal behaviour in my experience. I didn't get any warnings or errors either.
Issue with SSIS Package Configurations in SqlServer
Hello everyone,
I am working on a SSIS project and I am facing an issue for getting the configuration settings of the package, once it is deployed and executed from SQL Server agent.
The package uses two configuration types: (listed bellow in the order they are appeared in the configuration editor)
Config1 - Xml configuration file - for storing the database connection string.
Config2 - SQL Server - for storing some user defined variables. It uses the same database as specified in Config1.
Everything works fine and the package uses the database configuration values as defined in Config2, if I execute it from Visual Studio,
However, the package doesn’t get the configuration settings from the database when I try to execute it as a SQL Agent job.
There aren’t any errors and the package executes all tasks successfully, using the connection object Config1 (the same we use to get the config parameters from the database) and the default values of the user defined variables.
It works ok, if I change Config2 to be of type XML configuration file.
There could be two problems:
1. SQL server agent doesn’t read the configuration from the database and I am not quite sure how to set this. In Agent/ Job step properties screen/ Configurations tab I can only browse for a config file. I can also use the command window and /CONFIGFILE option to specify xml file, but how to use it in a case of a database configuration? Is there a /CONFIGDATABSE option or /CONFIGFILE works with database connection as well. I tried with /CONFIGFILE and database connection, but it doesn’t seem to work.
2. SQL server agent doesn’t get the configurations in the specified order. In my case,
it could try to read Config2 first, but at that moment it doesn’t have the database connection from Config1 and it fails. Again, I am not sure how to set the sequence.
Thanks in advance for your comments.
ITHave you specified a full path for Config1?|||Yes, I specified the full path for Config1. I used the configuration tab to select the file and in the command line window it shows the full path.
The package itself uses the connection from Config1 for the data flow tasks and they work without any issues.
|||Hi,
What kind of user defined variables are you fetching from the database?
Can you try storing them in package level variables by using a Script Task?
Regards,
B@.ns
|||I think you can discard option 2. The package configurations should be processed in the order in which they are stored.
It sounds like a permissions problem with the SQl Server Agent account.
Have you tried profiling (SQL Profiler) the package execution to see if it is generating any SQL errors trying to read the configuration table? If the package fails to read the configuration, it only raises a warning, not an error, so it is not always obvious when a configuration fails to load.
|||I couldn’t find any errors or warnings during the package execution.
Moreover the same connection is used for all data flow tasks inside the package and the SSIS logging (it uses SSIS log provider for SQL) and all of them work without any issues.
As a workaround I can add a SQL script to read those variables from the database, but this will duplicate the configuration functionality.
The idea was to use the existing SSIS database configuration feature instead of building a similar one from scratch.
|||Are you changig the path of the Conf1 in Agent, different than one you have when building the package?|||I.T.See if you this blog spot can help you identifying the issue:
http://rafael-salas.blogspot.com/2007/01/ssis-package-configurations-using-sql.html
It uses an environment variable instead of a file|||
Hi Rafael,
I checked your blog (actually this was one of the first materials I found when I started exploring the issue a week ago), but in our case we have some system restrictions for using environment variables.
In your example you mentioned also that you used it successfully with XML file.
I would like to ask you if you were to deploy it and execute it as a SQL agent job?
Thanks,
IT
|||Yes, I did, and as far as I remember it worked ok. The only problems I can remember are stupid things like the XML file was not accessible for the account running the SS Agent; not updating the connection string properly withing the XML file (hence trying to connect to the wrong instance), etc. But most of the times, the package logging will tell you if something is wrong with any of the configurations and even shows the order in which the configurations were applied.|||Rafael,
I would like to ask you if you remember how you set the sql configuration in the SQL Agent job. Did you do something special for this?
I couldn’t see any available options to set explicitly the configuration as SQL server (the UI allows only to browse and select config file).
The package logging is set to log all events and it doesn’t show any errors during the execution.
You mentioned also that the package logging can tell the order of the configuration, but I couldn’t see that kind of information. Is there a special custom event for this?
Thanks,
IT
|||I just ran some tests using XML and Table configurations (in that order) and works fine in BIDS and as an agent job.
I didn't have to do any special thing in the job step (CmdExec); just to a command like:
DTEXEC /FILE "{path}\Configurations demo 2.dtsx" /MAXCONCURRENT " -1 " /CHECKPOINTING OFF /REPORTING EWCDI
But what I could notice is that the messages about package configurations are not shown in te progress tab; I recently updated to SP2, and I wonder if that has been changed. I dind't even received any warning when I deliberated removed the xml config file...not even in the package logging|||
I couldn’t find any errors or warnings during the package execution.
This is normal behaviour in my experience. I didn't get any warnings or errors either.
Issue with SSIS Package Configurations in SqlServer
Hello everyone,
I am working on a SSIS project and I am facing an issue for getting the configuration settings of the package, once it is deployed and executed from SQL Server agent.
The package uses two configuration types: (listed bellow in the order they are appeared in the configuration editor)
Config1 - Xml configuration file - for storing the database connection string.
Config2 - SQL Server - for storing some user defined variables. It uses the same database as specified in Config1.
Everything works fine and the package uses the database configuration values as defined in Config2, if I execute it from Visual Studio,
However, the package doesn’t get the configuration settings from the database when I try to execute it as a SQL Agent job.
There aren’t any errors and the package executes all tasks successfully, using the connection object Config1 (the same we use to get the config parameters from the database) and the default values of the user defined variables.
It works ok, if I change Config2 to be of type XML configuration file.
There could be two problems:
1. SQL server agent doesn’t read the configuration from the database and I am not quite sure how to set this. In Agent/ Job step properties screen/ Configurations tab I can only browse for a config file. I can also use the command window and /CONFIGFILE option to specify xml file, but how to use it in a case of a database configuration? Is there a /CONFIGDATABSE option or /CONFIGFILE works with database connection as well. I tried with /CONFIGFILE and database connection, but it doesn’t seem to work.
2. SQL server agent doesn’t get the configurations in the specified order. In my case,
it could try to read Config2 first, but at that moment it doesn’t have the database connection from Config1 and it fails. Again, I am not sure how to set the sequence.
Thanks in advance for your comments.
ITHave you specified a full path for Config1?|||Yes, I specified the full path for Config1. I used the configuration tab to select the file and in the command line window it shows the full path.
The package itself uses the connection from Config1 for the data flow tasks and they work without any issues.
|||Hi,
What kind of user defined variables are you fetching from the database?
Can you try storing them in package level variables by using a Script Task?
Regards,
B@.ns
|||I think you can discard option 2. The package configurations should be processed in the order in which they are stored.
It sounds like a permissions problem with the SQl Server Agent account.
Have you tried profiling (SQL Profiler) the package execution to see if it is generating any SQL errors trying to read the configuration table? If the package fails to read the configuration, it only raises a warning, not an error, so it is not always obvious when a configuration fails to load.
|||I couldn’t find any errors or warnings during the package execution.
Moreover the same connection is used for all data flow tasks inside the package and the SSIS logging (it uses SSIS log provider for SQL) and all of them work without any issues.
As a workaround I can add a SQL script to read those variables from the database, but this will duplicate the configuration functionality.
The idea was to use the existing SSIS database configuration feature instead of building a similar one from scratch.
|||Are you changig the path of the Conf1 in Agent, different than one you have when building the package?|||I.T.See if you this blog spot can help you identifying the issue:
http://rafael-salas.blogspot.com/2007/01/ssis-package-configurations-using-sql.html
It uses an environment variable instead of a file|||
Hi Rafael,
I checked your blog (actually this was one of the first materials I found when I started exploring the issue a week ago), but in our case we have some system restrictions for using environment variables.
In your example you mentioned also that you used it successfully with XML file.
I would like to ask you if you were to deploy it and execute it as a SQL agent job?
Thanks,
IT
|||Yes, I did, and as far as I remember it worked ok. The only problems I can remember are stupid things like the XML file was not accessible for the account running the SS Agent; not updating the connection string properly withing the XML file (hence trying to connect to the wrong instance), etc. But most of the times, the package logging will tell you if something is wrong with any of the configurations and even shows the order in which the configurations were applied.|||Rafael,
I would like to ask you if you remember how you set the sql configuration in the SQL Agent job. Did you do something special for this?
I couldn’t see any available options to set explicitly the configuration as SQL server (the UI allows only to browse and select config file).
The package logging is set to log all events and it doesn’t show any errors during the execution.
You mentioned also that the package logging can tell the order of the configuration, but I couldn’t see that kind of information. Is there a special custom event for this?
Thanks,
IT
|||I just ran some tests using XML and Table configurations (in that order) and works fine in BIDS and as an agent job.
I didn't have to do any special thing in the job step (CmdExec); just to a command like:
DTEXEC /FILE "{path}\Configurations demo 2.dtsx" /MAXCONCURRENT " -1 " /CHECKPOINTING OFF /REPORTING EWCDI
But what I could notice is that the messages about package configurations are not shown in te progress tab; I recently updated to SP2, and I wonder if that has been changed. I dind't even received any warning when I deliberated removed the xml config file...not even in the package logging|||
I couldn’t find any errors or warnings during the package execution.
This is normal behaviour in my experience. I didn't get any warnings or errors either.
Issue with SSIS Package Configurations in SqlServer
Hello everyone,
I am working on a SSIS project and I am facing an issue for getting the configuration settings of the package, once it is deployed and executed from SQL Server agent.
The package uses two configuration types: (listed bellow in the order they are appeared in the configuration editor)
Config1 - Xml configuration file - for storing the database connection string.
Config2 - SQL Server - for storing some user defined variables. It uses the same database as specified in Config1.
Everything works fine and the package uses the database configuration values as defined in Config2, if I execute it from Visual Studio,
However, the package doesn’t get the configuration settings from the database when I try to execute it as a SQL Agent job.
There aren’t any errors and the package executes all tasks successfully, using the connection object Config1 (the same we use to get the config parameters from the database) and the default values of the user defined variables.
It works ok, if I change Config2 to be of type XML configuration file.
There could be two problems:
1. SQL server agent doesn’t read the configuration from the database and I am not quite sure how to set this. In Agent/ Job step properties screen/ Configurations tab I can only browse for a config file. I can also use the command window and /CONFIGFILE option to specify xml file, but how to use it in a case of a database configuration? Is there a /CONFIGDATABSE option or /CONFIGFILE works with database connection as well. I tried with /CONFIGFILE and database connection, but it doesn’t seem to work.
2. SQL server agent doesn’t get the configurations in the specified order. In my case,
it could try to read Config2 first, but at that moment it doesn’t have the database connection from Config1 and it fails. Again, I am not sure how to set the sequence.
Thanks in advance for your comments.
ITHave you specified a full path for Config1?|||Yes, I specified the full path for Config1. I used the configuration tab to select the file and in the command line window it shows the full path.
The package itself uses the connection from Config1 for the data flow tasks and they work without any issues.
|||Hi,
What kind of user defined variables are you fetching from the database?
Can you try storing them in package level variables by using a Script Task?
Regards,
B@.ns
|||I think you can discard option 2. The package configurations should be processed in the order in which they are stored.
It sounds like a permissions problem with the SQl Server Agent account.
Have you tried profiling (SQL Profiler) the package execution to see if it is generating any SQL errors trying to read the configuration table? If the package fails to read the configuration, it only raises a warning, not an error, so it is not always obvious when a configuration fails to load.
|||I couldn’t find any errors or warnings during the package execution.
Moreover the same connection is used for all data flow tasks inside the package and the SSIS logging (it uses SSIS log provider for SQL) and all of them work without any issues.
As a workaround I can add a SQL script to read those variables from the database, but this will duplicate the configuration functionality.
The idea was to use the existing SSIS database configuration feature instead of building a similar one from scratch.
|||Are you changig the path of the Conf1 in Agent, different than one you have when building the package?|||I.T.See if you this blog spot can help you identifying the issue:
http://rafael-salas.blogspot.com/2007/01/ssis-package-configurations-using-sql.html
It uses an environment variable instead of a file|||
Hi Rafael,
I checked your blog (actually this was one of the first materials I found when I started exploring the issue a week ago), but in our case we have some system restrictions for using environment variables.
In your example you mentioned also that you used it successfully with XML file.
I would like to ask you if you were to deploy it and execute it as a SQL agent job?
Thanks,
IT
|||Yes, I did, and as far as I remember it worked ok. The only problems I can remember are stupid things like the XML file was not accessible for the account running the SS Agent; not updating the connection string properly withing the XML file (hence trying to connect to the wrong instance), etc. But most of the times, the package logging will tell you if something is wrong with any of the configurations and even shows the order in which the configurations were applied.|||Rafael,
I would like to ask you if you remember how you set the sql configuration in the SQL Agent job. Did you do something special for this?
I couldn’t see any available options to set explicitly the configuration as SQL server (the UI allows only to browse and select config file).
The package logging is set to log all events and it doesn’t show any errors during the execution.
You mentioned also that the package logging can tell the order of the configuration, but I couldn’t see that kind of information. Is there a special custom event for this?
Thanks,
IT
|||I just ran some tests using XML and Table configurations (in that order) and works fine in BIDS and as an agent job.
I didn't have to do any special thing in the job step (CmdExec); just to a command like:
DTEXEC /FILE "{path}\Configurations demo 2.dtsx" /MAXCONCURRENT " -1 " /CHECKPOINTING OFF /REPORTING EWCDI
But what I could notice is that the messages about package configurations are not shown in te progress tab; I recently updated to SP2, and I wonder if that has been changed. I dind't even received any warning when I deliberated removed the xml config file...not even in the package logging|||
I couldn’t find any errors or warnings during the package execution.
This is normal behaviour in my experience. I didn't get any warnings or errors either.
Issue with SQL 2000 SP4
I am Ravi, working for Envision Financial systems India Pvt ltd and we are organization partner for Microsoft.
We have an Install error while installing cumulative hotfix KB916287 on SQL 2000 SP4 2000.80.2039.0
Downloaded file name and links are as below,
SQL 2000 SP4:
http://www.microsoft.com/downloads/details.aspx?FamilyID=8e2dfc8d-c20e-4446-99a9-b7f0213f8bc5&DisplayLang=en
File name: SQL2000-KB884525-SP4-x86-ENU.EXE
Cumulative hotfix KB916287:
http://www.microsoft.com/downloads/details.aspx?FamilyID=9c9ab140-bdee-44df-b7a3-e6849297754a&DisplayLang=en
File name: SQL2000-KB916287-v8.00.2187-x86x64-ENU.exe
Install error:"KB916287 falied to install"
Please let me know, if any one come accross thi sissue.
Thanks
ravi
Can you provide more information, preferably setup logs as there can be many reasons for the failure and the information you have called out above is insufficient to scope it down.
Thx
Ajay
|||You can goto your machine's %windir%\hotfix\ folder, there should have your SQL 2000 SP4 installation logs. Parse through the logs, and search for things like "fatal error", "failure", or "value 3", phrases to see if anything is wrong.
Jin
|||Hello,
We had the same problem...
Instal first the hotfix 2174 (KB911023) and after the hotfix 2187 (KB916287)... and no more problem.
@.+
PJD
|||Hi.
i cannot also upgrade to 8.00.2187 from 8.00.2039
SQL2000-KB916287-v8.00.2187-x86-ENU
i installed SP4 but i can not install SP4 HOTFIX.
this is the log file
[SQL2000-KB916287-v8.00.2187-x86-ENU.log]
0.688: ================================================================================
0.688: 2007/02/26 11:03:37.142 (local)
0.688: d:\62458212d0e03022ee0e5c\i386\update\update.exe (version 6.2.24.0)
1.110: SQL DLL: Windows Version Information:
1.110: SQL DLL: Type: WinNT/2000/XP
1.110: SQL DLL: Version: 5.1 SP 2 ("Service Pack 2")
1.110: SQL DLL: Terminal Services: No
1.110: SQL DLL: MUI Enabled: No
1.110: SQL DLL: User Name: GamzeErsoz
1.110: SQL DLL: Successfully opened registry key: SOFTWARE\Microsoft\Windows\CurrentVersion
1.110: SQL DLL: Successfully read registry key: CommonFilesDir, string value = C:\Program Files\Common Files
1.110: SQL DLL: Successfully opened registry key: SOFTWARE\Microsoft\Windows\CurrentVersion
1.110: SQL DLL: Successfully read registry key: ProgramFilesDir, string value = C:\Program Files
1.141: SQL DLL: Enumerating applicable product instances
1.141: SQL DLL: Attempting to discover local product instances
1.141: SQL DLL: Attempting to discover local named product instances
1.141: SQL DLL: Successfully opened registry key: Software\Microsoft\Microsoft SQL Server
1.141: SQL DLL: Failed to open registry key: Instance Names
1.141: SQL DLL: Successfully read registry key: InstalledInstances
1.141: SQL DLL: Multi-string values:
1.141: SQL DLL: Successfully read registry key: InstalledInstances
1.141: SQL DLL: Multi-string values:
1.141: SQL DLL: MSSQLSERVER
1.141: SQL DLL: Investigating product instance MSSQLSERVER
1.141: SQL DLL: Failed to open registry key: Software\Microsoft\Microsoft SQL Server\MSSQLSERVER\Setup
1.141: SQL DLL: Failed to find instance path for product instance MSSQLSERVER
1.141: SQL DLL: Found 0 local named product instance(s)
1.141: SQL DLL: Attempting to discover the local default product instance
1.141: SQL DLL: Investigating product instance MSSQLServer
1.141: SQL DLL: Successfully opened registry key: Software\Microsoft\MSSQLServer\Setup
1.141: SQL DLL: Successfully read registry key: SQLPath, string value = C:\Program Files\Microsoft SQL Server\MSSQL
1.141: SQL DLL: Found following instance path for product instance MSSQLServer: C:\Program Files\Microsoft SQL Server\MSSQL
1.141: SQL DLL: Allocating instance for MSSQLServer
1.141: SQL DLL: Checking key file for product instance MSSQLServer
1.141: SQL DLL: Found following key file for product instance MSSQLServer: C:\Program Files\Microsoft SQL Server\MSSQL\Binn\SQLServr.exe
1.141: SQL DLL: Determining LCID for product instance MSSQLServer
1.469: SQL DLL: Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL\Binn\SQLServr.exe
1.469: SQL DLL: Found following LCID for product instance MSSQLServer: 1033
1.469: SQL DLL: Determining GDR branching Hotfix for product instance MSSQLServer
1.469: SQL DLL: Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL\Binn\SQLServr.exe
1.469: SQL DLL: No GDR branch Hotfix found for product instance MSSQLServer
1.469: SQL DLL: Determining SKU for product instance MSSQLServer
1.500: SQL DLL: Loaded SQLBoot library
1.500: SQL DLL: Found following SKU for product instance MSSQLServer: DEVELOPER
1.500: SQL DLL: Determining major version for product instance MSSQLServer
1.500: SQL DLL: Successfully opened registry key: Software\Microsoft\MSSQLServer\MSSQLServer\CurrentVersion
1.500: SQL DLL: Successfully read registry key: CurrentVersion, string value = 8.00.194
1.500: SQL DLL: Found following major version for product instance MSSQLServer: 8
1.500: SQL DLL: Determining QFE level for product instance MSSQLServer
1.516: SQL DLL: Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL\Binn\SQLServr.exe
1.516: SQL DLL: Found following QFE level for product instance MSSQLServer: 2039
1.516: SQL DLL: Determining SP level via registry for product instance MSSQLServer
1.516: SQL DLL: Successfully opened registry key: Software\Microsoft\MSSQLServer\MSSQLServer\CurrentVersion
1.516: SQL DLL: Successfully read registry key: CSDVersionNumber, DWORD value = 0
1.516: SQL DLL: Found following SP level for product instance MSSQLServer: 4
1.516: SQL DLL: Determining registry info for product instance MSSQLServer
1.516: SQL DLL: Successfully opened registry key: Software\Microsoft\MSSQLServer
1.516: SQL DLL: Successfully opened registry key: Setup
1.516: SQL DLL: Successfully read registry key: SQLDataRoot, string value = C:\Program Files\Microsoft SQL Server\MSSQL
1.516: SQL DLL: Failed to read registry key: ProductCode
1.516: SQL DLL: Successfully opened registry key: Software\Microsoft\MSSQLServer
1.516: SQL DLL: Failed to open registry key: Cluster
1.516: SQL DLL: Found local default product instance
1.516: SQL DLL: Found 1 local product instance(s)
1.516: SQL DLL: Product discovery successfully completed during the install process for MSSQLServer
1.516: SQL DLL: SP Level check successfully completed during the install process for MSSQLServer
1.516: SQL DLL: Product language check successfully completed during the install process for MSSQLServer
1.516: SQL DLL: Product version check successfully completed during the install process for MSSQLServer
2.157: SQL DLL: Successfully opened registry key: SOFTWARE\Microsoft\Windows\CurrentVersion
2.157: SQL DLL: Successfully read registry key: CommonFilesDir, string value = C:\Program Files\Common Files
2.157: SQL DLL: Successfully opened registry key: SOFTWARE\Microsoft\Windows\CurrentVersion
2.157: SQL DLL: Successfully read registry key: ProgramFilesDir, string value = C:\Program Files
2.157: SQL DLL: Baseline build check completed during the install process
2.172: SQL DLL: Command-line instance name check completed during the install process
2.188: SQL DLL: Attempting to discover local product instances
2.188: SQL DLL: Investigating product instance SQLTools
2.188: SQL DLL: Successfully opened registry key: Software\Microsoft\Microsoft SQL Server\80\Tools\ClientSetup
2.188: SQL DLL: Successfully read registry key: SQLPath, string value = C:\Program Files\Microsoft SQL Server\80\Tools
2.188: SQL DLL: Found following instance path for product instance SQLTools: C:\Program Files\Microsoft SQL Server\80
2.188: SQL DLL: Allocating instance for SQLTools
2.188: SQL DLL: Checking key file for product instance SQLTools
2.219: SQL DLL: Found following key file for product instance SQLTools: C:\Program Files\Microsoft SQL Server\80\Tools\Binn\osql.exe
2.219: SQL DLL: Determining LCID for product instance SQLTools
2.266: SQL DLL: Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\80\Tools\Binn\osql.exe
2.266: SQL DLL: Found following LCID for product instance SQLTools: 1033
2.266: SQL DLL: Determining GDR branching Hotfix for product instance SQLTools
2.266: SQL DLL: Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\80\Tools\Binn\osql.exe
2.266: SQL DLL: No GDR branch Hotfix found for product instance SQLTools
2.266: SQL DLL: Determining SKU for product instance SQLTools
2.266: SQL DLL: Failed to load SQLBoot library
2.266: SQL DLL: Determining major version for product instance SQLTools
2.266: SQL DLL: Successfully opened registry key: Software\Microsoft\Microsoft SQL Server\80\Tools\ClientSetup\CurrentVersion
2.266: SQL DLL: Successfully read registry key: CurrentVersion, string value = 8.00.194
2.266: SQL DLL: Found following major version for product instance SQLTools: 8
2.266: SQL DLL: Determining QFE level for product instance SQLTools
2.266: SQL DLL: Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\80\Tools\Binn\osql.exe
2.266: SQL DLL: Found following QFE level for product instance SQLTools: 2039
2.266: SQL DLL: Determining SP level via registry for product instance SQLTools
2.266: SQL DLL: Successfully opened registry key: Software\Microsoft\Microsoft SQL Server\80\Tools\ClientSetup\CurrentVersion
2.266: SQL DLL: Failed to read registry key: CSDVersionNumber
2.266: SQL DLL: Found following SP level for product instance SQLTools: RTM
2.266: SQL DLL: Determining SP level via key file for product instance SQLTools
2.266: SQL DLL: Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\80\Tools\Binn\osql.exe
2.266: SQL DLL: Found following SP level for product instance SQLTools: 4
2.266: SQL DLL: Found 1 local product instance(s)
2.266: SQL DLL: Product discovery successfully completed during the install process for SQLTools
2.266: SQL DLL: SP Level check successfully completed during the install process for SQLTools
2.266: SQL DLL: Product language check successfully completed during the install process for SQLTools
2.266: SQL DLL: Product version check successfully completed during the install process for SQLTools
2.375: SQL DLL: Successfully opened registry key: SOFTWARE\Microsoft\Windows\CurrentVersion
2.375: SQL DLL: Successfully read registry key: CommonFilesDir, string value = C:\Program Files\Common Files
2.375: SQL DLL: Successfully opened registry key: SOFTWARE\Microsoft\Windows\CurrentVersion
2.375: SQL DLL: Successfully read registry key: ProgramFilesDir, string value = C:\Program Files
2.375: SQL DLL: Command-line instance name check completed during the install process
2.391: SQL DLL: Adding product instance MSSQLServer to uninstall state list
2.391: SQL DLL: Adding product instance SQLTools to uninstall state list
2.391: SQL DLL: There were 2 product instances added to the uninstall state list
2.391: SQL DLL: InitializeCustomizationDLL() returned 0
2.407: Hotfix started with following command line: -ER
2.532: SQL DLL: Entered callback DefineInstallCustomUI()
2.532: SQL DLL: Adding custom UI for attended mode
2.532: SQL DLL: DefineInstallCustomUI() returned 0
2.532: CreateUserInterface: DefineInstallCustomUI returned 0x0
2.578: SQL DLL: Entered callback BeginInstallation()
2.578: SQL DLL: Skipping authentication checks since running in attended mode
2.578: SQL DLL: BeginInstallation() returned 0
4.891: In Function TestVolatileFlag, line 11873, RegOpenKeyEx failed with error 0x2
4.891: In Function TestVolatileFlag, line 11905, RegOpenKeyEx failed with error 0x2
4.891: DoInstallation: CleanPFR failed: 0x2
4.938: SetProductTypes: InfProductBuildType=BuildType.Sel
4.938: SetAltOsLoaderPath: No section uses DirId 65701; done.
4.985: IncludeDirectoryIdFromInfSection: No DirId found for: DontRemoveOnUninst.DirId
4.985: SQL DLL: Successfully opened registry key: SOFTWARE\Microsoft\Windows\CurrentVersion
4.985: SQL DLL: Successfully read registry key: ProgramFilesDir, string value = C:\Program Files
4.985: SQL DLL: DynamicStringProgramDirectory returned C:\Program Files
4.985: SQL DLL: DynamicStringSystemDirectory returned C:\WINDOWS\system32
4.985: SQL DLL: DynamicStringInstancePath returned C:\Program Files\Microsoft SQL Server\MSSQL
4.985: SQL DLL: DynamicStringInstanceBinnResourcesLCIDPath returned C:\Program Files\Microsoft SQL Server\MSSQL\Binn\Resources\1033
5.063: DoInstallation: FetchSourceURL for d:\62458212d0e03022ee0e5c\i386\update\update.inf failed
5.078: LoadFileQueues: UpdSpGetSourceFileLocation for halaacpi.dll failed: 0xe0000102
5.078: BuildCabinetManifest: update.url absent
5.094: Starting AnalyzeComponents
5.094: AnalyzePhaseZero used 0 ticks
5.094: No c:\windows\INF\updtblk.inf file.
5.094: OEM file scan used 0 ticks
6.985: AnalyzePhaseOne: used 1891 ticks
6.985: AnalyzeComponents: Hotpatch analysis disabled; skipping.
6.985: AnalyzeComponents: Hotpatching is disabled.
7.000: AnalyzePhaseTwo used 15 ticks
7.000: AnalyzePhaseThree used 0 ticks
7.000: AnalyzePhaseFive used 0 ticks
7.000: AnalyzePhaseSix used 0 ticks
7.000: AnalyzeComponents used 1906 ticks
7.000: Downloading 0 files
7.000: bPatchMode = FALSE
7.016: Inventory complete: ReturnStatus=0, 1953 ticks
16.438: SQL DLL: Authenticating user using SAPWD
16.438: SQL DLL: SQL Service MSSQLServer was previously running, ready for authentication
16.469: SQL DLL: SQL Agent Service SQLSERVERAGENT was not previously running
16.610: SQL DLL: User authentication was successful
16.610: CreateUninstall = 1,Directory = C:\WINDOWS\$SQLUninstallSQL2000-KB916287-v8.00.2187-x86-ENU$
16.610: SQL DLL: Entered callback ConfirmInstallation()
16.610: SQL DLL: Enumerating active product instances
16.610: SQL DLL: Adding product instance MSSQLServer to execution list
16.610: SQL DLL: Adding SQL password command line switch for product instance MSSQLServer
16.610: SQL DLL: There were 1 product instances added to the execution list
16.610: SQL DLL: Adding product QFE level to ARP registry
16.610: SQL DLL: Adding product QFE level to ARP registry
16.610: SQL DLL: ConfirmInstallation() returned 0
16.610: Num Ticks for invent : 11547
16.625: Allocation size of drive C: is 4096 bytes, free space = 7220940800 bytes
16.735: AnalyzeDiskUsage: Skipping EstimateDiskUsageForUninstall.
16.735: Drive C: free 6886MB req: 17MB w/uninstall: NOT CALCULATED.
16.735: CabinetBuild complete
16.735: Num Ticks for Cabinet build : 125
16.735: SQL DLL: Entered callback BeforeInstallOps()
16.735: SQL DLL: BeforeInstallOps() returned 0
0.063: ================================================================================
0.063: 2007/02/26 11:03:53.485 (local)
0.063: d:\62458212d0e03022ee0e5c\i386\update\update.exe (version 6.2.24.0)
0.094: SQL DLL: Windows Version Information:
0.094: SQL DLL: Type: WinNT/2000/XP
0.094: SQL DLL: Version: 5.1 SP 2 ("Service Pack 2")
0.094: SQL DLL: Terminal Services: No
0.094: SQL DLL: MUI Enabled: No
0.109: SQL DLL: User Name: GamzeErsoz
0.109: SQL DLL: Successfully opened registry key: SOFTWARE\Microsoft\Windows\CurrentVersion
0.109: SQL DLL: Successfully read registry key: CommonFilesDir, string value = C:\Program Files\Common Files
0.109: SQL DLL: Successfully opened registry key: SOFTWARE\Microsoft\Windows\CurrentVersion
0.109: SQL DLL: Successfully read registry key: ProgramFilesDir, string value = C:\Program Files
0.125: SQL DLL: Enumerating applicable product instances
0.125: SQL DLL: Attempting to discover local product instances
0.125: SQL DLL: Attempting to discover local named product instances
0.125: SQL DLL: Successfully opened registry key: Software\Microsoft\Microsoft SQL Server
0.125: SQL DLL: Failed to open registry key: Instance Names
0.125: SQL DLL: Successfully read registry key: InstalledInstances
0.125: SQL DLL: Multi-string values:
0.125: SQL DLL: Successfully read registry key: InstalledInstances
0.125: SQL DLL: Multi-string values:
0.125: SQL DLL: MSSQLSERVER
0.125: SQL DLL: Investigating product instance MSSQLSERVER
0.125: SQL DLL: Failed to open registry key: Software\Microsoft\Microsoft SQL Server\MSSQLSERVER\Setup
0.125: SQL DLL: Failed to find instance path for product instance MSSQLSERVER
0.125: SQL DLL: Found 0 local named product instance(s)
0.125: SQL DLL: Attempting to discover the local default product instance
0.125: SQL DLL: Investigating product instance MSSQLServer
0.125: SQL DLL: Successfully opened registry key: Software\Microsoft\MSSQLServer\Setup
0.125: SQL DLL: Successfully read registry key: SQLPath, string value = C:\Program Files\Microsoft SQL Server\MSSQL
0.125: SQL DLL: Found following instance path for product instance MSSQLServer: C:\Program Files\Microsoft SQL Server\MSSQL
0.125: SQL DLL: Allocating instance for MSSQLServer
0.125: SQL DLL: Checking key file for product instance MSSQLServer
0.125: SQL DLL: Found following key file for product instance MSSQLServer: C:\Program Files\Microsoft SQL Server\MSSQL\Binn\SQLServr.exe
0.125: SQL DLL: Determining LCID for product instance MSSQLServer
0.125: SQL DLL: Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL\Binn\SQLServr.exe
0.125: SQL DLL: Found following LCID for product instance MSSQLServer: 1033
0.125: SQL DLL: Determining GDR branching Hotfix for product instance MSSQLServer
0.141: SQL DLL: Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL\Binn\SQLServr.exe
0.141: SQL DLL: No GDR branch Hotfix found for product instance MSSQLServer
0.141: SQL DLL: Determining SKU for product instance MSSQLServer
0.141: SQL DLL: Loaded SQLBoot library
0.141: SQL DLL: Found following SKU for product instance MSSQLServer: DEVELOPER
0.141: SQL DLL: Determining major version for product instance MSSQLServer
0.141: SQL DLL: Successfully opened registry key: Software\Microsoft\MSSQLServer\MSSQLServer\CurrentVersion
0.141: SQL DLL: Successfully read registry key: CurrentVersion, string value = 8.00.194
0.141: SQL DLL: Found following major version for product instance MSSQLServer: 8
0.141: SQL DLL: Determining QFE level for product instance MSSQLServer
0.141: SQL DLL: Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL\Binn\SQLServr.exe
0.141: SQL DLL: Found following QFE level for product instance MSSQLServer: 2039
0.141: SQL DLL: Determining SP level via registry for product instance MSSQLServer
0.141: SQL DLL: Successfully opened registry key: Software\Microsoft\MSSQLServer\MSSQLServer\CurrentVersion
0.141: SQL DLL: Successfully read registry key: CSDVersionNumber, DWORD value = 0
0.141: SQL DLL: Found following SP level for product instance MSSQLServer: 4
0.141: SQL DLL: Determining registry info for product instance MSSQLServer
0.141: SQL DLL: Successfully opened registry key: Software\Microsoft\MSSQLServer
0.141: SQL DLL: Successfully opened registry key: Setup
0.141: SQL DLL: Successfully read registry key: SQLDataRoot, string value = C:\Program Files\Microsoft SQL Server\MSSQL
0.141: SQL DLL: Failed to read registry key: ProductCode
0.141: SQL DLL: Successfully opened registry key: Software\Microsoft\MSSQLServer
0.141: SQL DLL: Failed to open registry key: Cluster
0.141: SQL DLL: Found local default product instance
0.141: SQL DLL: Found 1 local product instance(s)
0.141: SQL DLL: Product discovery successfully completed during the install process for MSSQLServer
0.141: SQL DLL: SP Level check successfully completed during the install process for MSSQLServer
0.141: SQL DLL: Product language check successfully completed during the install process for MSSQLServer
0.141: SQL DLL: Product version check successfully completed during the install process for MSSQLServer
0.297: SQL DLL: Successfully opened registry key: SOFTWARE\Microsoft\Windows\CurrentVersion
0.297: SQL DLL: Successfully read registry key: CommonFilesDir, string value = C:\Program Files\Common Files
0.297: SQL DLL: Successfully opened registry key: SOFTWARE\Microsoft\Windows\CurrentVersion
0.297: SQL DLL: Successfully read registry key: ProgramFilesDir, string value = C:\Program Files
0.297: SQL DLL: Baseline build check completed during the install process
0.297: SQL DLL: Command-line instance name check completed during the install process
0.313: SQL DLL: Attempting to discover local product instances
0.313: SQL DLL: Investigating product instance SQLTools
0.313: SQL DLL: Successfully opened registry key: Software\Microsoft\Microsoft SQL Server\80\Tools\ClientSetup
0.313: SQL DLL: Successfully read registry key: SQLPath, string value = C:\Program Files\Microsoft SQL Server\80\Tools
0.313: SQL DLL: Found following instance path for product instance SQLTools: C:\Program Files\Microsoft SQL Server\80
0.313: SQL DLL: Allocating instance for SQLTools
0.313: SQL DLL: Checking key file for product instance SQLTools
0.313: SQL DLL: Found following key file for product instance SQLTools: C:\Program Files\Microsoft SQL Server\80\Tools\Binn\osql.exe
0.313: SQL DLL: Determining LCID for product instance SQLTools
0.313: SQL DLL: Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\80\Tools\Binn\osql.exe
0.313: SQL DLL: Found following LCID for product instance SQLTools: 1033
0.313: SQL DLL: Determining GDR branching Hotfix for product instance SQLTools
0.313: SQL DLL: Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\80\Tools\Binn\osql.exe
0.313: SQL DLL: No GDR branch Hotfix found for product instance SQLTools
0.313: SQL DLL: Determining SKU for product instance SQLTools
0.313: SQL DLL: Failed to load SQLBoot library
0.313: SQL DLL: Determining major version for product instance SQLTools
0.313: SQL DLL: Successfully opened registry key: Software\Microsoft\Microsoft SQL Server\80\Tools\ClientSetup\CurrentVersion
0.313: SQL DLL: Successfully read registry key: CurrentVersion, string value = 8.00.194
0.313: SQL DLL: Found following major version for product instance SQLTools: 8
0.313: SQL DLL: Determining QFE level for product instance SQLTools
0.313: SQL DLL: Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\80\Tools\Binn\osql.exe
0.313: SQL DLL: Found following QFE level for product instance SQLTools: 2039
0.313: SQL DLL: Determining SP level via registry for product instance SQLTools
0.313: SQL DLL: Successfully opened registry key: Software\Microsoft\Microsoft SQL Server\80\Tools\ClientSetup\CurrentVersion
0.313: SQL DLL: Failed to read registry key: CSDVersionNumber
0.313: SQL DLL: Found following SP level for product instance SQLTools: RTM
0.313: SQL DLL: Determining SP level via key file for product instance SQLTools
0.313: SQL DLL: Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\80\Tools\Binn\osql.exe
0.313: SQL DLL: Found following SP level for product instance SQLTools: 4
0.313: SQL DLL: Found 1 local product instance(s)
0.313: SQL DLL: Product discovery successfully completed during the install process for SQLTools
0.313: SQL DLL: SP Level check successfully completed during the install process for SQLTools
0.313: SQL DLL: Product language check successfully completed during the install process for SQLTools
0.313: SQL DLL: Product version check successfully completed during the install process for SQLTools
0.375: SQL DLL: Successfully opened registry key: SOFTWARE\Microsoft\Windows\CurrentVersion
0.375: SQL DLL: Successfully read registry key: CommonFilesDir, string value = C:\Program Files\Common Files
0.375: SQL DLL: Successfully opened registry key: SOFTWARE\Microsoft\Windows\CurrentVersion
0.375: SQL DLL: Successfully read registry key: ProgramFilesDir, string value = C:\Program Files
0.391: SQL DLL: The product instance name SQLTools does not match those specified to update.
0.391: SQL DLL: Command-line instance name check completed during the install process
0.391: SQL DLL: Adding product instance MSSQLServer to uninstall state list
0.391: SQL DLL: Adding product instance SQLTools to uninstall state list
0.391: SQL DLL: There were 2 product instances added to the uninstall state list
0.391: SQL DLL: InitializeCustomizationDLL() returned 0
0.391: Hotfix started with following command line: /Quiet /NoRestart /ER /InstName:MSSQLSERVER /sapwd
0.391: SQL DLL: Entered callback BeginInstallation()
0.422: SQL DLL: Skipping authentication checks since /instname command line switch has been provided
0.422: SQL DLL: BeginInstallation() returned 0
0.500: In Function TestVolatileFlag, line 11873, RegOpenKeyEx failed with error 0x2
0.500: In Function TestVolatileFlag, line 11905, RegOpenKeyEx failed with error 0x2
0.500: DoInstallation: CleanPFR failed: 0x2
0.500: SetProductTypes: InfProductBuildType=BuildType.Sel
0.500: SetAltOsLoaderPath: No section uses DirId 65701; done.
0.500: IncludeDirectoryIdFromInfSection: No DirId found for: DontRemoveOnUninst.DirId
0.516: SQL DLL: Successfully opened registry key: SOFTWARE\Microsoft\Windows\CurrentVersion
0.516: SQL DLL: Successfully read registry key: ProgramFilesDir, string value = C:\Program Files
0.516: SQL DLL: DynamicStringProgramDirectory returned C:\Program Files
0.516: SQL DLL: DynamicStringSystemDirectory returned C:\WINDOWS\system32
0.516: SQL DLL: DynamicStringInstancePath returned C:\Program Files\Microsoft SQL Server\MSSQL
0.516: SQL DLL: DynamicStringInstanceBinnResourcesLCIDPath returned C:\Program Files\Microsoft SQL Server\MSSQL\Binn\Resources\1033
0.516: DoInstallation: FetchSourceURL for d:\62458212d0e03022ee0e5c\i386\update\update.inf failed
0.516: CreateUninstall = 1,Directory = C:\WINDOWS\$SQLUninstallSQL2000-KB916287-v8.00.2187-x86-ENU$
0.516: LoadFileQueues: UpdSpGetSourceFileLocation for halaacpi.dll failed: 0xe0000102
0.516: BuildCabinetManifest: update.url absent
0.516: Starting AnalyzeComponents
0.516: AnalyzePhaseZero used 0 ticks
0.516: No c:\windows\INF\updtblk.inf file.
0.516: OEM file scan used 0 ticks
0.531: AnalyzePhaseOne: used 15 ticks
0.531: AnalyzeComponents: Hotpatch analysis disabled; skipping.
0.531: AnalyzeComponents: Hotpatching is disabled.
0.531: AnalyzePhaseTwo used 0 ticks
0.531: AnalyzePhaseThree used 0 ticks
0.531: AnalyzePhaseFive used 0 ticks
0.531: AnalyzePhaseSix used 0 ticks
0.531: AnalyzeComponents used 15 ticks
0.531: Downloading 0 files
0.531: bPatchMode = FALSE
0.531: Inventory complete: ReturnStatus=0, 15 ticks
0.531: SQL DLL: Entered callback ConfirmInstallation()
0.531: SQL DLL: Adding product QFE level to ARP registry
0.531: SQL DLL: Adding product QFE level to ARP registry
0.531: SQL DLL: Stopping non-clustered services
0.547: SQL DLL: Stopping service SQLSERVERAGENT
0.547: SQL DLL: Attempting to stop service: SQLSERVERAGENT
0.563: SQL DLL: Successfully stopped service: SQLSERVERAGENT
0.563: SQL DLL: Stopping service MSSQLServer
0.563: SQL DLL: Attempting to stop service: MSSQLServer
3.625: SQL DLL: Successfully stopped service: MSSQLServer
3.625: SQL DLL: Installing clustered product instances
3.625: SQL DLL: Stopping cluster services
3.625: SQL DLL: ConfirmInstallation() returned 0
3.625: Num Ticks for invent : 3109
3.625: Allocation size of drive C: is 4096 bytes, free space = 7220924416 bytes
3.641: AnalyzeDiskUsage: Skipping EstimateDiskUsageForUninstall.
3.641: Drive C: free 6886MB req: 17MB w/uninstall: NOT CALCULATED.
3.641: CabinetBuild complete
3.641: Num Ticks for Cabinet build : 16
3.641: SQL DLL: Entered callback BeforeInstallOps()
3.641: SQL DLL: BeforeInstallOps() returned 0
3.641: SQL DLL: DynamicStringInstanceName returned MSSQLServer
3.641: ProcessDynamicStrings: CustomFunction for DynamicStringInstanceName returned MSSQLServer
3.641: ProcessDynamicStrings: all %InstanceName% replaced with MSSQLServer.
3.641: SQL DLL: DynamicStringInstanceLCID returned 1033
3.641: ProcessDynamicStrings: CustomFunction for DynamicStringInstanceLCID returned 1033
3.641: ProcessDynamicStrings: all %LCID% replaced with 1033.
3.641: SQL DLL: DynamicStringInstanceLCIDName returned ENU
3.641: ProcessDynamicStrings: CustomFunction for DynamicStringInstanceLCIDName returned ENU
3.641: ProcessDynamicStrings: all %LCIDName% replaced with ENU.
3.641: SQL DLL: DynamicStringUserAccount returned GamzeErsoz
3.641: ProcessDynamicStrings: CustomFunction for DynamicStringUserAccount returned GamzeErsoz
3.656: ProcessDynamicStrings: all %UserName% replaced with GamzeErsoz.
3.656: ProcessDynamicStrings: CustomFunction for DynamicStringTimestamp returned (null)
3.656: SQL DLL: DynamicStringProductName returned SQLServerClient
3.656: ProcessDynamicStrings: CustomFunction for DynamicStringProductName returned SQLServerClient
3.656: ProcessDynamicStrings: all %ProductName% replaced with SQLServerClient.
3.656: SQL DLL: DynamicStringLegalProductName returned SQL Server 2000
3.656: ProcessDynamicStrings: CustomFunction for DynamicStringLegalProductName returned SQL Server 2000
3.656: ProcessDynamicStrings: all %LegalProductName% replaced with SQL Server 2000.
3.656: SQL DLL: DynamicStringProductDescription returned SQL Server 2000
3.656: ProcessDynamicStrings: CustomFunction for DynamicStringProductDescription returned SQL Server 2000
3.656: ProcessDynamicStrings: all %ProductDescription% replaced with SQL Server 2000.
3.656: SQL DLL: DynamicStringProductDetails returned
3.656: ProcessDynamicStrings: CustomFunction for DynamicStringProductDetails returned (null)
3.656: SQL DLL: DynamicStringProductVersion returned 8
3.656: ProcessDynamicStrings: CustomFunction for DynamicStringProductVersion returned 8
3.656: ProcessDynamicStrings: all %ProductVersion% replaced with 8.
3.656: SQL DLL: DynamicStringProductSPLevel returned SP4
3.656: ProcessDynamicStrings: CustomFunction for DynamicStringProductSPLevel returned SP4
3.656: ProcessDynamicStrings: all %ProductSPLevel% replaced with SP4.
3.656: SQL DLL: DynamicStringProductLCID returned 1033
3.656: ProcessDynamicStrings: CustomFunction for DynamicStringProductLCID returned 1033
3.656: ProcessDynamicStrings: all %ProductLCID% replaced with 1033.
3.656: SQL DLL: DynamicStringProductSKU returned
3.656: ProcessDynamicStrings: CustomFunction for DynamicStringProductSKU returned (null)
3.656: SQL DLL: DynamicStringProductKBArticle returned KB916287
3.656: ProcessDynamicStrings: CustomFunction for DynamicStringProductKBArticle returned KB916287
3.656: ProcessDynamicStrings: all %ProductKBArticle% replaced with KB916287.
3.656: SQL DLL: DynamicStringProductBuild returned 2187
3.656: ProcessDynamicStrings: CustomFunction for DynamicStringProductBuild returned 2187
3.656: ProcessDynamicStrings: all %ProductBuild% replaced with 2187.
4.203: FileInUse:: Detection disabled.
5.203: LoadFileQueues: UpdSpGetSourceFileLocation for halaacpi.dll failed: 0xe0000102
10.391: SQL DLL: Entered callback ArchivingComplete()
10.391: SQL DLL: ArchivingComplete() returned 0
10.391: Num Ticks for Backup : 6750
10.516: Num Ticks for creating uninst inf : 125
10.531: Registering Uninstall Program for -> KB916287(ENU), KB916287(ENU) , 0x0
10.578: LoadFileQueues: UpdSpGetSourceFileLocation for halaacpi.dll failed: 0xe0000102
18.234: System Restore Point set.
19.094: PFE2: Not avoiding Per File Exceptions.
19.234: Copied file: C:\WINDOWS\$SQLUninstallSQL2000-KB916287-v8.00.2187-x86-ENU$\spuninst\SQLSTPCustomDLL.dll
19.766: Copied file: C:\WINDOWS\$SQLUninstallSQL2000-KB916287-v8.00.2187-x86-ENU$\spuninst\SQLSTPCustomDLL.rll
19.891: Copied file: C:\WINDOWS\$SQLUninstallSQL2000-KB916287-v8.00.2187-x86-ENU$\spuninst\SQLSE.rll
20.094: Copied file: C:\WINDOWS\$SQLUninstallSQL2000-KB916287-v8.00.2187-x86-ENU$\spuninst\OSQL.exe
20.266: Copied file: C:\WINDOWS\$SQLUninstallSQL2000-KB916287-v8.00.2187-x86-ENU$\files\80sp4-tools.sql
20.391: Copied file: C:\WINDOWS\$SQLUninstallSQL2000-KB916287-v8.00.2187-x86-ENU$\files\replmerg.sql
20.719: Copied file: C:\WINDOWS\$SQLUninstallSQL2000-KB916287-v8.00.2187-x86-ENU$\files\repltran.sql
21.156: Copied file: C:\WINDOWS\$SQLUninstallSQL2000-KB916287-v8.00.2187-x86-ENU$\files\sp4_serv_qfe.sql
21.250: Copied file: C:\Program Files\Microsoft SQL Server\80\Tools\Binn\dtsui.dll
21.922: Copied file: C:\Program Files\Microsoft SQL Server\80\Tools\Binn\osql.exe
22.016: Copied file: C:\Program Files\Microsoft SQL Server\80\Tools\Binn\pfclnt80.dll
22.297: Copied file (delayed): C:\Program Files\Microsoft SQL Server\80\Tools\Binn\SET7B.tmp
22.359: Copied file: C:\Program Files\Microsoft SQL Server\80\Tools\Binn\semexec.dll
22.609: Copied file: C:\Program Files\Microsoft SQL Server\80\Tools\Binn\sqldmo.dll
23.141: Copied file: C:\Program Files\Microsoft SQL Server\80\Tools\Binn\stardds.dll
23.266: Copied file: C:\Program Files\Microsoft SQL Server\80\Tools\Binn\svrnetcn.dll
23.359: Copied file: C:\Program Files\Microsoft SQL Server\80\COM\impprov.dll
23.438: Copied file: C:\Program Files\Microsoft SQL Server\80\COM\msgprox.dll
23.531: Copied file: C:\Program Files\Microsoft SQL Server\80\COM\replmerg.exe
23.641: Copied file: C:\Program Files\Microsoft SQL Server\80\COM\replprov.dll
23.719: Copied file: C:\Program Files\Microsoft SQL Server\80\COM\replrec.dll
24.063: Copied file: C:\Program Files\Microsoft SQL Server\80\COM\replsub.dll
24.266: Copied file: C:\WINDOWS\system32\msrpjt40.dll
24.391: Copied file: C:\WINDOWS\system32\ntwdblib.dll
24.563: Copied file: C:\Program Files\Microsoft SQL Server\MSSQL\Binn\mssdi98.dll
24.844: Copied file: C:\Program Files\Microsoft SQL Server\MSSQL\Binn\odsole70.dll
25.172: Copied file: C:\Program Files\Microsoft SQL Server\MSSQL\Binn\sqlagent.exe
25.281: Copied file: C:\Program Files\Microsoft SQL Server\MSSQL\Binn\sqldiag.exe
25.391: Copied file: C:\Program Files\Microsoft SQL Server\MSSQL\Binn\sqlservr.exe
26.656: Copied file: C:\Program Files\Microsoft SQL Server\MSSQL\Binn\sqlsort.dll
26.797: Copied file: C:\Program Files\Microsoft SQL Server\MSSQL\Binn\ums.dll
26.906: Copied file: C:\Program Files\Microsoft SQL Server\MSSQL\Install\procsyst.sql
26.984: Copied file: C:\Program Files\Microsoft SQL Server\MSSQL\Install\replmerg.sql
27.125: Copied file: C:\Program Files\Microsoft SQL Server\MSSQL\Install\repltran.sql
27.234: Copied file: C:\Program Files\Microsoft SQL Server\MSSQL\Binn\Dll\ums.pdb
27.297: Copied file: C:\Program Files\Microsoft SQL Server\MSSQL\Binn\Resources\1033\sqlevn70.rll
27.359: DoInstallation: Installing assemblies with source root path: d:\62458212d0e03022ee0e5c\i386\
27.359: SQL DLL: Entered callback CopyingComplete()
27.359: SQL DLL: Installing scripts
27.359: SQL DLL: Attempting to start service: MSSQLServer
32.250: SQL DLL: Successfully started service: MSSQLServer
32.250: SQL DLL: Waiting for SQL NT Service to open event sqlserverRecComplete to confirm that database connections are possible
32.922: SQL DLL: SQL NT Service has signaled event sqlserverRecComplete which confirms that database connections are possible
32.922: SQL DLL: Attempting to run script: replmerg.sql
32.922: SQL DLL: Attempting to run script: d:\62458212d0e03022ee0e5c\i386\Files\replmerg.sql
32.922: SQL DLL: Validating OSQL connections using SAPWD
33.281: SQL DLL: Pre-script OSQL connection failed - continuing to wait for SQL service to become responsive to connection requests
38.750: SQL DLL: Pre-script OSQL connection failed - continuing to wait for SQL service to become responsive to connection requests
43.891: SQL DLL: Pre-script OSQL connection failed - continuing to wait for SQL service to become responsive to connection requests
49.172: SQL DLL: Pre-script OSQL connection failed - continuing to wait for SQL service to become responsive to connection requests
54.328: SQL DLL: Pre-script OSQL connection failed - continuing to wait for SQL service to become responsive to connection requests
59.469: SQL DLL: Pre-script OSQL connection failed - continuing to wait for SQL service to become responsive to connection requests
64.672: SQL DLL: Pre-script OSQL connection failed - continuing to wait for SQL service to become responsive to connection requests
69.875: SQL DLL: Pre-script OSQL connection failed - continuing to wait for SQL service to become responsive to connection requests
75.031: SQL DLL: Pre-script OSQL connection failed - continuing to wait for SQL service to become responsive to connection requests
80.484: SQL DLL: Pre-script OSQL connection failed - continuing to wait for SQL service to become responsive to connection requests
85.641: SQL DLL: Pre-script OSQL connection failed - continuing to wait for SQL service to become responsive to connection requests
90.734: SQL DLL: Pre-script OSQL connection failed - continuing to wait for SQL service to become responsive to connection requests
95.828: SQL DLL: Pre-script OSQL connection failed - continuing to wait for SQL service to become responsive to connection requests
101.313: SQL DLL: Pre-script OSQL connection failed - continuing to wait for SQL service to become responsive to connection requests
106.406: SQL DLL: Pre-script OSQL connection failed - continuing to wait for SQL service to become responsive to connection requests
111.500: SQL DLL: Pre-script OSQL connection failed - continuing to wait for SQL service to become responsive to connection requests
117.000: SQL DLL: Pre-script OSQL connection failed - continuing to wait for SQL service to become responsive to connection requests
122.141: SQL DLL: Pre-script OSQL connection failed - continuing to wait for SQL service to become responsive to connection requests
127.453: SQL DLL: Pre-script OSQL connection failed - continuing to wait for SQL service to become responsive to connection requests
132.563: SQL DLL: Pre-script OSQL connection failed - continuing to wait for SQL service to become responsive to connection requests
137.688: SQL DLL: Pre-script OSQL connection failed - continuing to wait for SQL service to become responsive to connection requests
142.813: SQL DLL: Pre-script OSQL connection failed - continuing to wait for SQL service to become responsive to connection requests
147.938: SQL DLL: Pre-script OSQL connection failed - continuing to wait for SQL service to become responsive to connection requests
153.094: SQL DLL: Pre-script OSQL connection failed - continuing to wait for SQL service to become responsive to connection requests
158.219: SQL DLL: Pre-script OSQL connection failed - continuing to wait for SQL service to become responsive to connection requests
163.516: SQL DLL: Pre-script OSQL connection failed - continuing to wait for SQL service to become responsive to connection requests
168.938: SQL DLL: Pre-script OSQL connection failed - continuing to wait for SQL service to become responsive to connection requests
174.031: SQL DLL: Pre-script OSQL connection failed - continuing to wait for SQL service to become responsive to connection requests
179.156: SQL DLL: Pre-script OSQL connection failed - continuing to wait for SQL service to become responsive to connection requests
184.250: SQL DLL: Pre-script OSQL connection failed - continuing to wait for SQL service to become responsive to connection requests
189.641: SQL DLL: Pre-script OSQL connection failed - continuing to wait for SQL service to become responsive to connection requests
194.781: SQL DLL: Pre-script OSQL connection failed - continuing to wait for SQL service to become responsive to connection requests
199.906: SQL DLL: Pre-script OSQL connection failed - continuing to wait for SQL service to become responsive to connection requests
205.063: SQL DLL: Pre-script OSQL connection failed - continuing to wait for SQL service to become responsive to connection requests
210.172: SQL DLL: Pre-script OSQL connection failed - continuing to wait for SQL service to become responsive to connection requests
215.266: SQL DLL: Pre-script OSQL connection failed - continuing to wait for SQL service to become responsive to connection requests
220.391: SQL DLL: Pre-script OSQL connection failed - continuing to wait for SQL service to become responsive to connection requests
225.531: SQL DLL: Pre-script OSQL connection failed - continuing to wait for SQL service to become responsive to connection requests
230.641: SQL DLL: Pre-script OSQL connection failed - continuing to wait for SQL service to become responsive to connection requests
235.766: SQL DLL: Pre-script OSQL connection failed - continuing to wait for SQL service to become responsive to connection requests
240.953: SQL DLL: Pre-script OSQL connection failed - continuing to wait for SQL service to become responsive to connection requests
246.109: SQL DLL: Pre-script OSQL connection failed - continuing to wait for SQL service to become responsive to connection requests
251.266: SQL DLL: Pre-script OSQL connection failed - continuing to wait for SQL service to become responsive to connection requests
256.438: SQL DLL: Pre-script OSQL connection failed - continuing to wait for SQL service to become responsive to connection requests
261.547: SQL DLL: Pre-script OSQL connection failed - continuing to wait for SQL service to become responsive to connection requests
266.688: SQL DLL: Pre-script OSQL connection failed - continuing to wait for SQL service to become responsive to connection requests
271.828: SQL DLL: Pre-script OSQL connection failed - continuing to wait for SQL service to become responsive to connection requests
276.922: SQL DLL: Pre-script OSQL connection failed - continuing to wait for SQL service to become responsive to connection requests
282.047: SQL DLL: Pre-script OSQL connection failed - continuing to wait for SQL service to become responsive to connection requests
287.250: SQL DLL: Pre-script OSQL connection failed - continuing to wait for SQL service to become responsive to connection requests
292.297: SQL DLL: Pre-script OSQL connection failed - continuing to wait for SQL service to become responsive to connection requests
297.813: SQL DLL: Pre-script OSQL connection failed - continuing to wait for SQL service to become responsive to connection requests
302.922: SQL DLL: Pre-script OSQL connection failed - continuing to wait for SQL service to become responsive to connection requests
308.078: SQL DLL: Pre-script OSQL connection failed - continuing to wait for SQL service to become responsive to connection requests
313.172: SQL DLL: Pre-script OSQL connection failed - continuing to wait for SQL service to become responsive to connection requests
318.313: SQL DLL: Pre-script OSQL connection failed - continuing to wait for SQL service to become responsive to connection requests
323.500: SQL DLL: Pre-script OSQL connection failed - continuing to wait for SQL service to become responsive to connection requests
328.609: SQL DLL: Pre-script OSQL connection failed - continuing to wait for SQL service to become responsive to connection requests
333.703: SQL DLL: Pre-script OSQL connection failed - continuing to wait for SQL service to become responsive to connection requests
338.859: SQL DLL: Pre-script OSQL connection failed - continuing to wait for SQL service to become responsive to connection requests
343.891: SQL DLL: The following exception occurred: SQL Server not responsive prior to running script Date: 02/26/2007 11:09:37.440 File: \depot\sqlvault\setupmain\setup\sqlse\sqlsedll\copyengine.cpp Line: 1251
343.891: SQL DLL: The following unexpected error occurred:
SQL Server not responsive prior to running script
343.891: SQL DLL: SQL Server not responsive prior to running script
344.141: SQL DLL: CopyingComplete() returned 11017
344.141: DoInstallation: CustomizeCall failed : 0x2b09
345.016: SQL DLL: Entered callback EndInstallation()
345.016: SQL DLL: EndInstallation() returned 0
345.016: SQL DLL: Entered callback FailedInstallation()
345.016: SQL DLL: FailedInstallation() returned 0
345.047: An invalid or inconsistent flowspec was found in the QOS structure.
345.047: KB916287(ENU) installation did not complete.
Select 'OK' to undo the changes that have been made.
345.047: Starting process: C:\WINDOWS\$SQLUninstallSQL2000-KB916287-v8.00.2187-x86-ENU$\spuninst\spuninst.exe /~ -q -z
359.406: Software Update Rollback has completed with return code 0xbc2. This rollback requires a reboot.
359.406: KB916287(ENU) installation did not complete.
SQL has been partially updated and may not work properly.
359.406: Update.exe extended error code = 0x2b09
376.578: ================================================================================
376.578: 2007/02/26 11:09:53.235 (local)
376.578: d:\62458212d0e03022ee0e5c\i386\update\update.exe (version 6.2.24.0)
376.578: SpawnInstancesForInstall: InstRetVal1 = 0x2b09
376.578: SQL DLL: Entered callback FailedInstallation()
376.578: SQL DLL: Instance Status Summary
376.578: SQL DLL: Instance Status: MSSQLServer - Failure
376.578: SQL DLL: Instance Status: SQLTools - Success
376.625: SQL DLL: FailedInstallation() returned 11017
376.625: DoInstallation: FailedInstallation Failed: 0x2b09
439.907: Message displayed to the user: An error in updating your system has occurred.
439.907: User Input: OK
579.547: RebootNecessary = 1,WizardInput = 0 , DontReboot = 1, ForceRestart = 0
|||
Hi
Did you manage to resolve this issue as I have exactlly the same issue when install this patch (2187). The Sql group propertise are saying that it is SP4 2187.
I am just concerned that the databases have not been up graded.
Any help that you can offer would greatly received.
Regards
Stephen
Subscribe to:
Posts (Atom)