Sunday, March 11, 2012
Error: %1 is not a valid Win32 application
This morning I tried to start my MSDE instance like I do everyday. But,
sadly, an error message raised, telling me that '%1 is not a valid Win32
application'.
At this point, as I didn't have anything important at this instance, I
removed the program through the control panel, and reinstalled it. But, when
it was finishing, it raised another error: "The installer could not
configure the server. Read the server's and installer's error registry for
more information".
Searching the directory, I found the cnfgsrv.out:
Iniciando servicio ... (Initiating service...)
Modern_Spanish_CI_AS
-m -Q -T4022 -T3659
Error al intentar iniciar el servicio (193) (Error trying to initiate the
service)
Error de configuracin del servidor SQL Server. (Configuration error of the
SQL Server)
Well, after that, I removed everything related to SQL Server, the Management
Console, the SQL Agent, everything. Deleted all the files, searched the
registry, deleting everything.
Then I reinstalled the MSDE instance again, getting the same error.
Then, I tried to install the SQL Server, but the installer told me that "The
SQL Server 2000 Standard Edition component is not compatible with this
operating system. Only the client components will be available".
My operating system is Windows 2000 Professional.
How can I reinstall SQL Server?
Thanks!!
Arnau.hi Arnau,
Arnau Font wrote:
> Hi,
> This morning I tried to start my MSDE instance like I do everyday.
> But, sadly, an error message raised, telling me that '%1 is not a
> valid Win32 application'.
> At this point, as I didn't have anything important at this instance, I
> removed the program through the control panel, and reinstalled it.
> But, when it was finishing, it raised another error: "The installer
> could not configure the server. Read the server's and installer's
> error registry for more information".
please have a look at
http://support.microsoft.com/defaul...kb;en-us;320873 and
http://support.microsoft.com/defaul...b;EN-US;Q290991 for 2 pieces
of information about properly manually unistall MSDE...
--
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply|||Thanks Andrea,
I found an useful article at microsoft:
http://support.microsoft.com/defaul...kb;en-us;812486
I had a hidden file at Program Files named 'Microsoft' that didn't allow the
MSDE service to run!
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> escribi en el mensaje
news:3ss810FpikjbU1@.individual.net...
> hi Arnau,
> Arnau Font wrote:
> please have a look at
> http://support.microsoft.com/defaul...kb;en-us;320873 and
> http://support.microsoft.com/defaul...b;EN-US;Q290991 for 2
pieces
> of information about properly manually unistall MSDE...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
Error: %1 is not a valid Win32 application
This morning I tried to start my MSDE instance like I do everyday. But,
sadly, an error message raised, telling me that '%1 is not a valid Win32
application'.
At this point, as I didn't have anything important at this instance, I
removed the program through the control panel, and reinstalled it. But, when
it was finishing, it raised another error: "The installer could not
configure the server. Read the server's and installer's error registry for
more information".
Searching the directory, I found the cnfgsrv.out:
Iniciando servicio ... (Initiating service...)
Modern_Spanish_CI_AS
-m -Q -T4022 -T3659
Error al intentar iniciar el servicio (193) (Error trying to initiate the
service)
Error de configuración del servidor SQL Server. (Configuration error of the
SQL Server)
Well, after that, I removed everything related to SQL Server, the Management
Console, the SQL Agent, everything. Deleted all the files, searched the
registry, deleting everything.
Then I reinstalled the MSDE instance again, getting the same error.
Then, I tried to install the SQL Server, but the installer told me that "The
SQL Server 2000 Standard Edition component is not compatible with this
operating system. Only the client components will be available".
My operating system is Windows 2000 Professional.
How can I reinstall SQL Server?
Thanks!!
Arnau.hi Arnau,
Arnau Font wrote:
> Hi,
> This morning I tried to start my MSDE instance like I do everyday.
> But, sadly, an error message raised, telling me that '%1 is not a
> valid Win32 application'.
> At this point, as I didn't have anything important at this instance, I
> removed the program through the control panel, and reinstalled it.
> But, when it was finishing, it raised another error: "The installer
> could not configure the server. Read the server's and installer's
> error registry for more information".
please have a look at
http://support.microsoft.com/default.aspx?scid=kb;en-us;320873 and
http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q290991 for 2 pieces
of information about properly manually unistall MSDE...
--
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply|||Thanks Andrea,
I found an useful article at microsoft:
http://support.microsoft.com/default.aspx?scid=kb;en-us;812486
I had a hidden file at Program Files named 'Microsoft' that didn't allow the
MSDE service to run!
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> escribió en el mensaje
news:3ss810FpikjbU1@.individual.net...
> hi Arnau,
> Arnau Font wrote:
> > Hi,
> >
> > This morning I tried to start my MSDE instance like I do everyday.
> > But, sadly, an error message raised, telling me that '%1 is not a
> > valid Win32 application'.
> >
> > At this point, as I didn't have anything important at this instance, I
> > removed the program through the control panel, and reinstalled it.
> > But, when it was finishing, it raised another error: "The installer
> > could not configure the server. Read the server's and installer's
> > error registry for more information".
> please have a look at
> http://support.microsoft.com/default.aspx?scid=kb;en-us;320873 and
> http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q290991 for 2
pieces
> of information about properly manually unistall MSDE...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
Error: %1 is not a valid Win32 application
This morning I tried to start my MSDE instance like I do everyday. But,
sadly, an error message raised, telling me that '%1 is not a valid Win32
application'.
At this point, as I didn't have anything important at this instance, I
removed the program through the control panel, and reinstalled it. But, when
it was finishing, it raised another error: "The installer could not
configure the server. Read the server's and installer's error registry for
more information".
Searching the directory, I found the cnfgsrv.out:
Iniciando servicio ... (Initiating service...)
Modern_Spanish_CI_AS
-m -Q -T4022 -T3659
Error al intentar iniciar el servicio (193) (Error trying to initiate the
service)
Error de configuracin del servidor SQL Server. (Configuration error of the
SQL Server)
Well, after that, I removed everything related to SQL Server, the Management
Console, the SQL Agent, everything. Deleted all the files, searched the
registry, deleting everything.
Then I reinstalled the MSDE instance again, getting the same error.
Then, I tried to install the SQL Server, but the installer told me that "The
SQL Server 2000 Standard Edition component is not compatible with this
operating system. Only the client components will be available".
My operating system is Windows 2000 Professional.
How can I reinstall SQL Server?
Thanks!!
Arnau.
hi Arnau,
Arnau Font wrote:
> Hi,
> This morning I tried to start my MSDE instance like I do everyday.
> But, sadly, an error message raised, telling me that '%1 is not a
> valid Win32 application'.
> At this point, as I didn't have anything important at this instance, I
> removed the program through the control panel, and reinstalled it.
> But, when it was finishing, it raised another error: "The installer
> could not configure the server. Read the server's and installer's
> error registry for more information".
please have a look at
http://support.microsoft.com/default...b;en-us;320873 and
http://support.microsoft.com/default...;EN-US;Q290991 for 2 pieces
of information about properly manually unistall MSDE...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thanks Andrea,
I found an useful article at microsoft:
http://support.microsoft.com/default...b;en-us;812486
I had a hidden file at Program Files named 'Microsoft' that didn't allow the
MSDE service to run!
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> escribi en el mensaje
news:3ss810FpikjbU1@.individual.net...
> hi Arnau,
> Arnau Font wrote:
> please have a look at
> http://support.microsoft.com/default...b;en-us;320873 and
> http://support.microsoft.com/default...;EN-US;Q290991 for 2
pieces
> of information about properly manually unistall MSDE...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
Error: %1 is not a valid Win32 application
This morning I tried to start my MSDE instance like I do everyday. But,
sadly, an error message raised, telling me that '%1 is not a valid Win32
application'.
At this point, as I didn't have anything important at this instance, I
removed the program through the control panel, and reinstalled it. But, when
it was finishing, it raised another error: "The installer could not
configure the server. Read the server's and installer's error registry for
more information".
Searching the directory, I found the cnfgsrv.out:
Iniciando servicio ... (Initiating service...)
Modern_Spanish_CI_AS
-m -Q -T4022 -T3659
Error al intentar iniciar el servicio (193) (Error trying to initiate the
service)
Error de configuracin del servidor SQL Server. (Configuration error of the
SQL Server)
Well, after that, I removed everything related to SQL Server, the Management
Console, the SQL Agent, everything. Deleted all the files, searched the
registry, deleting everything.
Then I reinstalled the MSDE instance again, getting the same error.
Then, I tried to install the SQL Server, but the installer told me that "The
SQL Server 2000 Standard Edition component is not compatible with this
operating system. Only the client components will be available".
My operating system is Windows 2000 Professional.
How can I reinstall SQL Server?
Thanks!!
Arnau.
hi Arnau,
Arnau Font wrote:
> Hi,
> This morning I tried to start my MSDE instance like I do everyday.
> But, sadly, an error message raised, telling me that '%1 is not a
> valid Win32 application'.
> At this point, as I didn't have anything important at this instance, I
> removed the program through the control panel, and reinstalled it.
> But, when it was finishing, it raised another error: "The installer
> could not configure the server. Read the server's and installer's
> error registry for more information".
please have a look at
http://support.microsoft.com/default...b;en-us;320873 and
http://support.microsoft.com/default...;EN-US;Q290991 for 2 pieces
of information about properly manually unistall MSDE...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thanks Andrea,
I found an useful article at microsoft:
http://support.microsoft.com/default...b;en-us;812486
I had a hidden file at Program Files named 'Microsoft' that didn't allow the
MSDE service to run!
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> escribi en el mensaje
news:3ss810FpikjbU1@.individual.net...
> hi Arnau,
> Arnau Font wrote:
> please have a look at
> http://support.microsoft.com/default...b;en-us;320873 and
> http://support.microsoft.com/default...;EN-US;Q290991 for 2
pieces
> of information about properly manually unistall MSDE...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
Friday, March 9, 2012
error.log invalid protocol specified
an msde on WinXP home.
Where does this Invalid Protocol specified for a ?
come from ?
Should i run svrnetcn.exe to configure protocols ?
Is it true, that I have to install MSDE with
DISABLENETWORKPROTOCOL=0 set to access it from
a remote site ?
2004-04-29 11:54:05.34 server Using 'SSNETLIB.DLL'
version '8.0.760'.
2004-04-29 11:54:05.34 server Invalid Protocol
specified for a
??4? instance: ?.
2004-04-29 11:54:05.34 server Invalid Protocol
specified for a
??t? instance: ?c??t?.
2004-04-29 11:54:05.34 server Invalid Protocol
specified for a
??t?y, Winsock Proxy instance: ?.
2004-04-29 11:54:05.34 spid5 Starting up
database 'model'.
2004-04-29 11:54:05.63 server SQL server listening on
192.168.1.34:
1433.
2004-04-29 11:54:05.63 server SQL server listening on
127.0.0.1:
1433.
2004-04-29 11:54:05.63 server SuperSocket Info: Bind
failed on TCP
port 1433.
2004-04-29 11:54:05.64 server SQL server listening on
192.168.1.34:
1433.
2004-04-29 11:54:05.64 server SQL server listening on
127.0.0.1:
1433.
..
hi Dominique,
"Dominique" <anonymous@.discussions.microsoft.com> ha scritto nel messaggio
news:a26601c434eb$a425b4f0$a601280a@.phx.gbl...
> I get the entries shown below in my error.log of
> an msde on WinXP home.
> Where does this Invalid Protocol specified for a ?
> come from ?
> Should i run svrnetcn.exe to configure protocols ?
> Is it true, that I have to install MSDE with
> DISABLENETWORKPROTOCOL=0 set to access it from
> a remote site ?
MSDE sp3a and MSDE release A install by default disabling all network
protocols in order to protect the installed instance from malicious external
attacks..
if you want your instance to be accessible from remote client you have to
enable network protocols at install time, via the DISABLENETWORKPROTOCOL=0
command line parameter or anabling them after install via Server Network
Utility (svrnetcn.exe)...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.7.0 - DbaMgr ver 0.53.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
Wednesday, March 7, 2012
error with sqlmaint.exe
I'm using McAfee ePO here which uses an MSDE database. I am trying to run
the recommended maintenance command on the DB but keep getting an error. It
seems to be related to the -U and -P account I'm using but I've tried every
variation of user and password it could be including domain admin + passwd.
Is there some way of adding a user to the DB? My only way of interacting
with it is through osql commands as far as I know.
The command I'm trying to run is:
sqlmaint -S SERVERNAME -U "domain\user" -P "password" -D
ePO_database_data -RebldIdx 15 -RmUnusedSpace 110 15 -UpdOptiStats 15
and the error that it's returning:
error 18452 Login failed for user, 'domain\user' reason: Not associated with
a trusted SQL Server connection.
I've tried several variations for the user and password but always get the
same result. I've read a bit about changing the authentication type for the
DB but A. I'm not sure if thats the right way to go and B. am afraid if I do
change something that ePO will not then be able to access the DB.
Thanks for the reply and if you can provide any assistance I'd really
appreciate it!
gerryR
hi,
gerryR wrote:
> Hi All
> I'm using McAfee ePO here which uses an MSDE database. I am trying to
> run the recommended maintenance command on the DB but keep getting an
> error. It seems to be related to the -U and -P account I'm using but
> I've tried every variation of user and password it could be including
> domain admin + passwd.
> Is there some way of adding a user to the DB? My only way of
> interacting with it is through osql commands as far as I know.
> The command I'm trying to run is:
> sqlmaint -S SERVERNAME -U "domain\user" -P "password" -D
> ePO_database_data -RebldIdx 15 -RmUnusedSpace 110 15 -UpdOptiStats 15
> and the error that it's returning:
> error 18452 Login failed for user, 'domain\user' reason: Not
> associated with a trusted SQL Server connection.
> I've tried several variations for the user and password but always
> get the same result. I've read a bit about changing the
> authentication type for the DB but A. I'm not sure if thats the right
> way to go and B. am afraid if I do change something that ePO will not
> then be able to access the DB.
this exception,
> error 18452 Login failed for user, 'domain\user' reason: Not
> associated with a trusted SQL Server connection.
usually is relative to a SQL Server instance only allowing trusted WinNT
authenticated connections (default setting for MSDE, you can actually modify
as reported in
http://support.microsoft.com/default...b;en-us;285097 ...
anyway, you do not have to provide SQL Server credentials for a standard SQL
Server authenticated connection in the form -U "domain\user" -P "domain
password" as SQL Server is unaware of your domain controller... for this
type of login you have to provide credentials regarding a registered SQL
Server login... ie: "sa" and it's password..
http://msdn.microsoft.com/library/de...maint_19ix.asp
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.18.0 - DbaMgr ver 0.62.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Hi Andrea
Thanks for your reply and apologies for not getting back sooner!
I changed the regiatry to allow mixed authentication and have got a bit
further. I am now getting a new error and was wondering if you know what
might be causing it (google has not returned much info on this!)
Using the same command as before but with "-U administrator -P password" I
now get the following error:
Logged on to SQL Server 'servername'
as 'administrator' <non-trusted>
error 21776: the name 'data_baseName' was not found in the database
collection. If the name is a qualified name use [] to seperate various
parts of the name and try again.
I've tried enclosing the database with the [ ] but to no avail. My database
name looks like
ePO_SERVER_data.mdf
Ive tried [ePO_SERVER_data] and [ePO_SERVER_data.mdf] but it doesn't do
anything.
I'd appreciate any help you can give
cheers
gerry
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:4691c0Fa2i54U1@.individual.net...
> hi,
> gerryR wrote:
> this exception,
> usually is relative to a SQL Server instance only allowing trusted WinNT
> authenticated connections (default setting for MSDE, you can actually
> modify as reported in
> http://support.microsoft.com/default...b;en-us;285097 ...
> anyway, you do not have to provide SQL Server credentials for a standard
> SQL Server authenticated connection in the form -U "domain\user" -P
> "domain password" as SQL Server is unaware of your domain controller...
> for this type of login you have to provide credentials regarding a
> registered SQL Server login... ie: "sa" and it's password..
> http://msdn.microsoft.com/library/de...maint_19ix.asp
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.18.0 - DbaMgr ver 0.62.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||hi Gerry,
gerryR wrote:
> error 21776: the name 'data_baseName' was not found in the database
> collection. If the name is a qualified name use [] to seperate
> various parts of the name and try again.
> I've tried enclosing the database with the [ ] but to no avail. My
> database name looks like
> ePO_SERVER_data.mdf
> Ive tried [ePO_SERVER_data] and [ePO_SERVER_data.mdf] but it doesn't
> do anything.
you have to indicate the "logical" database name..
ePO_SERVER_data.mdf is the physical name of the primary data file..
try a
SELECT db.name
FROM master.dbo.sysdatabases db
WHERE db.filename LIKE '%ePO_SERVER_data.mdf'
to identify the correct logical database name you are interested with...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.18.0 - DbaMgr ver 0.62.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Hi Andrea, thanks a million for that I didn't realise it had to be the
logical name and not the file name. The logical name is ePO_servername and
the command ran without error!! Thanks a million for your help!
One thing I did notice is the file size stayed the same. Is this normal? I
would have thought the "RmUnusedSpace" part would have freed up some space
and thus reduced the file size?
any way thanks again for all your help in solving my problem.
all the best
gerryR
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:46j2qqFbc3ebU1@.individual.net...
> hi Gerry,
> gerryR wrote:
> you have to indicate the "logical" database name..
> ePO_SERVER_data.mdf is the physical name of the primary data file..
> try a
> SELECT db.name
> FROM master.dbo.sysdatabases db
> WHERE db.filename LIKE '%ePO_SERVER_data.mdf'
> to identify the correct logical database name you are interested with...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.18.0 - DbaMgr ver 0.62.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||The file won't get smaller unless you explicitly tell it to get smaller with
the shrink command. IMHO, shrink should only be used if you are desperate
for disk space and you know that your database isn't going to grow anymore.
Growing a database is reasonably expensive - as is shrinking it so
continuously growing and shrinking your database files is a waste of
resources. To me it's like when your mother comes to visit you add another
bedroom to your house and as soon as she leaves you tear it down. This only
makes sense if you know for sure you're never having visitors again. If
your mom is coming again next Christmas, you would probably be better off
leaving the spare room where it is - unless you really need the space for
the new hot-tub.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"gerryR" <gerryrminus@.thisgerryr.com> wrote in message
news:%230$BsIHPGHA.312@.TK2MSFTNGP12.phx.gbl...
> Hi Andrea, thanks a million for that I didn't realise it had to be the
> logical name and not the file name. The logical name is ePO_servername
> and the command ran without error!! Thanks a million for your help!
> One thing I did notice is the file size stayed the same. Is this normal?
> I would have thought the "RmUnusedSpace" part would have freed up some
> space and thus reduced the file size?
> any way thanks again for all your help in solving my problem.
> all the best
> gerryR
>
>
> "Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
> news:46j2qqFbc3ebU1@.individual.net...
>
|||Thaks for the info Roger, I'll leave it the way it is so.
good analogy btw!
gerryR
"Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
news:uq51f4HPGHA.3064@.TK2MSFTNGP10.phx.gbl...
> The file won't get smaller unless you explicitly tell it to get smaller
> with the shrink command. IMHO, shrink should only be used if you are
> desperate for disk space and you know that your database isn't going to
> grow anymore. Growing a database is reasonably expensive - as is shrinking
> it so continuously growing and shrinking your database files is a waste of
> resources. To me it's like when your mother comes to visit you add
> another bedroom to your house and as soon as she leaves you tear it down.
> This only makes sense if you know for sure you're never having visitors
> again. If your mom is coming again next Christmas, you would probably be
> better off leaving the spare room where it is - unless you really need the
> space for the new hot-tub.
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "gerryR" <gerryrminus@.thisgerryr.com> wrote in message
> news:%230$BsIHPGHA.312@.TK2MSFTNGP12.phx.gbl...
>
error with OpenRowSet
but receive the following error:
OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error.
Connection Closed
here's the sql:
select *
into MyTable
FROM OPENROWSET('Microsoft.Jet.OLEDB.4.0',
'Excel 8.0;Database=C:\Default.xls;HDR=YES',
'SELECT * FROM [Sheet1$]')
any help is appreciated...I think it should work if file name is correct. Check whether the file
name is correct
Madhivanan|||Hi
Try this one
SELECT *
FROM OpenDataSource( 'Microsoft.Jet.OLEDB.4.0',
'Data Source="d:\MyData.xls";
User ID=Admin;Password=;Extended properties=Excel 8.0')...Sheet1$
OR
Specify all columns
insert into MyTable (col1,col2)
SELECT col1,col2
FROM OPENROWSET('Microsoft.Jet.OLEDB.4.0',
'Excel 8.0;Database=C:\Default.xls;HDR=YES',
'SELECT * FROM [Sheet1$]')
".bill" <wSweetman@.ucsd.edu> wrote in message news:O3rAPZfHFHA.3612@.TK2MSFTN
GP09.phx.gbl...
I'm trying to import a simple excel spreadsheet into MSDE using OpenRowSet,
but receive the following error:
OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error.
Connection Closed
here's the sql:
select *
into MyTable
FROM OPENROWSET('Microsoft.Jet.OLEDB.4.0',
'Excel 8.0;Database=C:\Default.xls;HDR=YES',
'SELECT * FROM [Sheet1$]')
any help is appreciated...|||Do you have the file opened in Excel when you try to do this?
That would cause an error, but otherwise the syntax looks ok.
If the file C:\Default.xls exists and has a sheet named
Sheet1, it should work. Does the SQL Server
login have access to that file? What happens if you try
exec master..xp_cmdshell N'dir C:\*.xls'
Steve Kass
Drew University
.bill wrote:
>I'm trying to import a simple excel spreadsheet into MSDE using OpenRowSet,
but receive the following error:
>OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error.
>Connection Closed
>here's the sql:
>select *
>into MyTable
>FROM OPENROWSET('Microsoft.Jet.OLEDB.4.0',
> 'Excel 8.0;Database=C:\Default.xls;HDR=YES',
> 'SELECT * FROM [Sheet1$]')
>any help is appreciated...
>
>|||Hi there,
Has anyone found an answer to this yet?
I tried:
insert into tblTestSql (RowNo,RecNo,LdUserName,
Code,LogIn,LogOut)
SELECT RowNo,RecNo,LdUserName,
Code,LogIn,LogOut
FROM OPENROWSET('Microsoft.Jet.OLEDB.4.0',
'Excel 8.0;Database=C:\ReleaseTwo\LogInandOut.xls;HDR=YES',
'SELECT * FROM [Sheet1$]')
Which gives me
Server: Msg 7399, Level 16, State 1, Line 1
OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error.
[OLE/DB provider returned message: Unspecified error]
When I try:
exec master..xp_cmdshell N'dir c:\ReleaseTwo\LogInandOut.xls'
I get
The system cannot find the file specified.
Any ideas?
Paul
".bill" wrote:
> I'm trying to import a simple excel spreadsheet into MSDE using OpenRowSet
, but receive the following error:
> OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error.
> Connection Closed
> here's the sql:
> select *
> into MyTable
> FROM OPENROWSET('Microsoft.Jet.OLEDB.4.0',
> 'Excel 8.0;Database=C:\Default.xls;HDR=YES',
> 'SELECT * FROM [Sheet1$]')
> any help is appreciated..|||Hi Paul,
The file is in the local machine and you might have run the query in
the server which is not the local machine
Madhivanan|||Hi Madhivanan,
It dosn't matter whether the excel (or txt/csv) file is on the server on on
my local machine I get the same result.
Paul.
"Madhivanan" wrote:
> Hi Paul,
> The file is in the local machine and you might have run the query in
> the server which is not the local machine
> Madhivanan
>|||Paul,
How do you know the file exists?
If it does, and exec master..xp_cmdshell N'dir
c:\ReleaseTwo\LogInandOut.xls' fails,
it's not a problem with OPENROWSET. It sounds like the account used by
SQL Server does not have permission to access the Excel file.
SK
Paul in Harrow wrote:
>Hi there,
>Has anyone found an answer to this yet?
>I tried:
>insert into tblTestSql (RowNo,RecNo,LdUserName,
>Code,LogIn,LogOut)
>SELECT RowNo,RecNo,LdUserName,
>Code,LogIn,LogOut
>FROM OPENROWSET('Microsoft.Jet.OLEDB.4.0',
> 'Excel 8.0;Database=C:\ReleaseTwo\LogInandOut.xls;HDR=YES',
> 'SELECT * FROM [Sheet1$]')
>Which gives me
>Server: Msg 7399, Level 16, State 1, Line 1
>OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error.
>[OLE/DB provider returned message: Unspecified error]
>When I try:
>exec master..xp_cmdshell N'dir c:\ReleaseTwo\LogInandOut.xls'
>I get
>The system cannot find the file specified.
>Any ideas?
>Paul
>".bill" wrote:
>
>|||> How do you know the file exists?
Because I created it.
> If it does, and exec master..xp_cmdshell N'dir
> c:\ReleaseTwo\LogInandOut.xls' fails,
> it's not a problem with OPENROWSET. It sounds like the account used by
> SQL Server does not have permission to access the Excel file.
I've just shown that to my techie and he's looking blank! How do I/we find
out what permissions SQL Server has & how do I/we (proberly me) change them?
Many thanks
Paul.|||
Paul in Harrow wrote:
>Because I created it.
>
>
>I've just shown that to my techie and he's looking blank! How do I/we find
>out what permissions SQL Server has & how do I/we (proberly me) change them
?
>
>
It might be as simple as: navigate to the file in Windows Explorer,
right-click, go to the security tab, and make sure the file is available
to the account under which the SQL Server service is running.
But managing Windows accounts is not my strong point, so you could also
look at "Setting up Windows Services Accounts" in Books Online and
see what you find on Usenet:
http://groups.google.co.uk/groups? ...missions%20file
http://www.google.co.uk/search? q=%...missions%20file
For the openquery statement to work, you should be able to log on to
Windows with the same account used by the SQL Server service and
then access the file.
SK
>Many thanks
>Paul.
>
Error with MSDE with Crystal Report - From VB
(1) How can i pass MSDE connection Parameter -> Crystal Report from VB...?
Let say, While designing cr.report - the server name & DB name is embedded
in report. But now we removed the server & DB name from the Table Name.
After doing this the report does'nt show anything eventhough we pass the
connection strings from VB.
Is there any solution to achieve my connection with DB from VB.
Mahehskumar.R
"? Mahesh Kumar" wrote:
> Hi groups,
> (1) How can i pass MSDE connection Parameter -> Crystal Report from VB...?
> Let say, While designing cr.report - the server name & DB name is embedded
> in report. But now we removed the server & DB name from the Table Name.
> After doing this the report does'nt show anything eventhough we pass the
> connection strings from VB.
> Is there any solution to achieve my connection with DB from VB.
>
> Mahehskumar.R
>
Try this:
Dim Report As CRAXDRT.Report
Dim crxDBT As CRAXDRT.DatabaseTable
For Each crxDBT In Report.Database.Tables
crxDBT.SetLogOnInfo ServerName, DatabaseName, UserName, Password
Next
Bye
Nedi Freguglia
Sunday, February 26, 2012
Error with Downloading MSDE
I am new to SQL I download "sql2ksp3" to my laptop (Window Xp Pentium III) and then I start to setup MSDE:
>> setup SAPWD=pass SECURITYMODE=SQL
After I run this command it gives me the following statment!!!
Setup failed to configure the server.Refer to the server error logs and setup error logs for more information.
Please help me what i have to do to make this stuff works!!
Sincerely
Henok::Please help me what i have to do to make this stuff works!!
I hate to tell you, but this starts with reading the error message. And following the isntructions it provides.
See:
::Setup failed to configure the server.Refer to the server error logs and setup error logs for
::more information.
Tells you to go to the sever error logs and the setup error logs and get more information.
Now, without this information, I do not really see how we could help you. Maybe if my crystal ball version 22332233 is finally delivered, but until then at least I actually do rely on you getting the errors our of your computer.
Are you sure that pass and securitymode are correct, btw? I NEVER had to run setup with any parameters.|||Have you installed MSDE before this, and you're just upgrading your current instance?
check out this tutorial on MSDE installation:
A Beginner's Guide - Installing MSDE
|||To DL the MSDE Engine I would first Download This file... Latest Update, From memory the file you listed above is the SP3 for SQL Server and not the desktop install.
<<http://www.microsoft.com/downloads/details.aspx?FamilyID=413744d1-a0bc-479f-bafa-e4b278eb9147&DisplayLang=en>>
MSDE SP3a Download.|||I had the same problem because I, too, read the installation instructions that shipped with MSDE.
I used the following command:
setup SAPWD="bubba"
If you choose to use theSECURITYMODE switch, you won't need to encloseSQL in quotations.
Good luck!
John|||David,
Thanks for pointing us (at least me) to a nice artilce. I could over come this issue and it works fine for me. Thank you.
Friday, February 24, 2012
Error while trying to open/create a DTS - urgent
I have MSDE SP3 installed and the only thing that I have changed
recently is my Windows login Password.
In the Enterprise Manager the SQL server is registered using mixed
authentication.
When I try to open any DTS in Design mode, I get an error dialog with
the title 'DTS Design error' and saying that:
"Error occured during creation of a DTS package"
and then when I click on the OKAY button I get the 2nd error dialog
saying:
"The selected package cannot be opened. The DTS designer has been
closed."
I am getting the same message when I try to create a new package

Can someone PLEASE help me out here.
Thanks.
Re-register the DTS dlls.
You can find them listed here
Redistributing DTS with your program
(http://www.sqldts.com/Default.aspx?225)
Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.Konesans.com
"Learner" <wantnospam@.email.com> wrote in message
news:MPG.1bc14741c6d2435e989747@.msnews.microsoft.c om...
> Hi,
> I have MSDE SP3 installed and the only thing that I have changed
> recently is my Windows login Password.
> In the Enterprise Manager the SQL server is registered using mixed
> authentication.
> When I try to open any DTS in Design mode, I get an error dialog with
> the title 'DTS Design error' and saying that:
> "Error occured during creation of a DTS package"
>
> and then when I click on the OKAY button I get the 2nd error dialog
> saying:
> "The selected package cannot be opened. The DTS designer has been
> closed."
>
> I am getting the same message when I try to create a new package

> Can someone PLEASE help me out here.
> --
> Thanks.
|||Many thanks Allan. Appreciate your help.
Regards.
> | Re-register the DTS dlls.
> |
> | You can find them listed here
> |
> | Redistributing DTS with your program
> | (http://www.sqldts.com/Default.aspx?225)
> |
> |
Error While starting SQL Server 2000
SuperSocket Info: Bind failed on TCP port 1433.
please advise
also note thta it is only MSDE not the whole SQL Sever
Posted using the http://www.dbforumz.com interface, at author's request
Articles individually checked for conformance to usenet standards
Topic URL: http://www.dbforumz.com/Connect-Erro...ict195117.html
Visit Topic URL to contact author (reg. req'd). Report abuse: http://www.dbforumz.com/eform.php?p=660630
Hi
Looks like something else is listening on port 1433 by the time you are
trying to start the service.
Before you start MSDE, run "NETSTAT -a"to see what is listening on 1433.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"mujeeb" <UseLinkToEmail@.dbForumz.com> wrote in message
news:1109uoa2fg07p33@.news.supernews.com...
> Im getting this error when starting the Mssql server 2000
> SuperSocket Info: Bind failed on TCP port 1433.
> please advise
> also note thta it is only MSDE not the whole SQL Sever
> --
> Posted using the http://www.dbforumz.com interface, at author's request
> Articles individually checked for conformance to usenet standards
> Topic URL:
http://www.dbforumz.com/Connect-Erro...ict195117.html
> Visit Topic URL to contact author (reg. req'd). Report abuse:
http://www.dbforumz.com/eform.php?p=660630
|||"Mike Epprecht" wrote:
> Hi
> Looks like something else is listening on port 1433 by the
> time you are
> trying to start the service.
> Before you start MSDE, run "NETSTAT -a"to see what is
> listening on 1433.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "mujeeb" <UseLinkToEmail@.dbForumz.com> wrote in message
> news:1109uoa2fg07p33@.news.supernews.com...
> standards
> http://www.dbforumz.com/Connect-Erro...ict195117.html
> abuse:
> http://www.dbforumz.com/eform.php?p=660630
I did all that and the netstat part of output is here
TCP 193.9.200.243:1361 193.9.200.244:139 TIME_WAIT
TCP 193.9.200.243:1363 193.9.200.51:139 TIME_WAIT
TCP 193.9.200.243:1383 193.9.200.244:139 TIME_WAIT
TCP 193.9.200.243:1433 0.0.0.0:0 LISTENING
UDP 0.0.0.0:135 *:*
UDP 0.0.0.0:445 *:*
UDP 0.0.0.0:1026 *:*
UDP 0.0.0.0:1434 *:*
regards
Error While starting SQL Server 2000
SuperSocket Info: Bind failed on TCP port 1433.
please advise
also note thta it is only MSDE not the whole SQL Sever
Posted using the http://www.dbforumz.com interface, at author's request
Articles individually checked for conformance to usenet standards
Topic URL: http://www.dbforumz.com/Connect-Err... />
95117.html
Visit Topic URL to contact author (reg. req'd). Report abuse: http://www.dbforumz
.com/eform.php?p=660630Hi
Looks like something else is listening on port 1433 by the time you are
trying to start the service.
Before you start MSDE, run "NETSTAT -a"to see what is listening on 1433.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"mujeeb" <UseLinkToEmail@.dbForumz.com> wrote in message
news:1109uoa2fg07p33@.news.supernews.com...
> Im getting this error when starting the Mssql server 2000
> SuperSocket Info: Bind failed on TCP port 1433.
> please advise
> also note thta it is only MSDE not the whole SQL Sever
> --
> Posted using the http://www.dbforumz.com interface, at author's request
> Articles individually checked for conformance to usenet standards
> Topic URL:
http://www.dbforumz.com/Connect-Err...pict195117.htmlreen">
> Visit Topic URL to contact author (reg. req'd). Report abuse:
http://www.dbforumz.com/eform.php?p=660630|||"Mike Epprecht" wrote:
> Hi
> Looks like something else is listening on port 1433 by the
> time you are
> trying to start the service.
> Before you start MSDE, run "NETSTAT -a"to see what is
> listening on 1433.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "mujeeb" <UseLinkToEmail@.dbForumz.com> wrote in message
> news:1109uoa2fg07p33@.news.supernews.com...
> standards
> http://www.dbforumz.com/Connect-Err...17.htm
l
> abuse:
> http://www.dbforumz.com/eform.php?p=660630
I did all that and the netstat part of output is here
TCP 193.9.200.243:1361 193.9.200.244:139 TIME_WAIT
TCP 193.9.200.243:1363 193.9.200.51:139 TIME_WAIT
TCP 193.9.200.243:1383 193.9.200.244:139 TIME_WAIT
TCP 193.9.200.243:1433 0.0.0.0:0 LISTENING
UDP 0.0.0.0:135 *:*
UDP 0.0.0.0:445 *:*
UDP 0.0.0.0:1026 *:*
UDP 0.0.0.0:1434 *:*
regards