Microsoft Search service can't start after SQL2005 installation!

Hi
The version numbers in your post seem to be inconsistent!
I assume that you have removed SQL 2000 and only have a named instance of
SQL 2005. If you want the instance of SQL 2005 to be the default instance you
will need to install SQL 2005 again anyhow, and possibly remove the named
instance of SQL 2005 if it is not wanted. If you want to reinstall the
current named instance you can install it from the command line with the
REINSTALLMODE=OMUS option see
http://msdn2.microsoft.com/en-us/library/ms144259.aspx#reinstallmode
REINSTALLMODE=O will replace the missing file, but it would probably not do
any harm having the other options.
John
"PG" wrote:

> Hi everybody I had a server with SQL2000 Standard on Server2003 Standard
> working, but I was told to uninstall and install SQl2005 Standard, but now
> when I start the server I receive an error saying that a service could not
> start, I went to see what service the server was talking about and it was
> the Microsoft Search service. The error says that the specified file can't
> be found, so I went to "C:\Program Files\Common
> Files\System\MSSearch\Bin\mssearch.exe" and the file mssearch.exe is
> missing!!!
> Was it the uninstall of SQL2000 that screwed this up, or the installation of
> SQL2005?
> I dont know what to do from here, what can I do?...Any help would be
> appreciated.
> Thanks in advance..
>
>
Hi
"PG" wrote:

> I'm sorry if I didn't make myself clear, what I did was uninstall SQL2000
> and afterwards install SQL2005 on the same machine (WindowsServer2003).
>
mssearch.exe is for SQL 2000 if you want to reinstall it see
http://support.microsoft.com/default.aspx/kb/827449 but if you have SQL 2005
you should see an instance of SQL Server FullText Search (MSSQLSERVER) in
your services which runs "C:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\Binn\msftesql.exe". The article also shows how to
remove it.
John
|||John Bell from BCSI?
Jason

Quote:

Originally Posted by John Bell

Hi
"PG" wrote:

> I'm sorry if I didn't make myself clear, what I did was uninstall SQL2000
> and afterwards install SQL2005 on the same machine (WindowsServer2003).
>
mssearch.exe is for SQL 2000 if you want to reinstall it see
http://support.microsoft.com/default.aspx/kb/827449 but if you have SQL 2005
you should see an instance of SQL Server FullText Search (MSSQLSERVER) in
your services which runs "C:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\Binn\msftesql.exe". The article also shows how to
remove it.
John

Microsoft Search service can't start after SQL2005 installation!

Hi everybody I had a server with SQL2000 Standard on Server2003 Standard
working, but I was told to uninstall and install SQl2005 Standard, but now
when I start the server I receive an error saying that a service could not
start, I went to see what service the server was talking about and it was
the Microsoft Search service. The error says that the specified file can't
be found, so I went to "C:\Program Files\Common
Files\System\MSSearch\Bin\mssearch.exe" and the file mssearch.exe is
missing!!!
Was it the uninstall of SQL2000 that screwed this up, or the installation of
SQL2005?
I dont know what to do from here, what can I do?...Any help would be
appreciated.
Thanks in advance..Hi
The version numbers in your post seem to be inconsistent!
I assume that you have removed SQL 2000 and only have a named instance of
SQL 2005. If you want the instance of SQL 2005 to be the default instance you
will need to install SQL 2005 again anyhow, and possibly remove the named
instance of SQL 2005 if it is not wanted. If you want to reinstall the
current named instance you can install it from the command line with the
REINSTALLMODE=OMUS option see
http://msdn2.microsoft.com/en-us/library/ms144259.aspx#reinstallmode
REINSTALLMODE=O will replace the missing file, but it would probably not do
any harm having the other options.
John
"PG" wrote:
> Hi everybody I had a server with SQL2000 Standard on Server2003 Standard
> working, but I was told to uninstall and install SQl2005 Standard, but now
> when I start the server I receive an error saying that a service could not
> start, I went to see what service the server was talking about and it was
> the Microsoft Search service. The error says that the specified file can't
> be found, so I went to "C:\Program Files\Common
> Files\System\MSSearch\Bin\mssearch.exe" and the file mssearch.exe is
> missing!!!
> Was it the uninstall of SQL2000 that screwed this up, or the installation of
> SQL2005?
> I dont know what to do from here, what can I do?...Any help would be
> appreciated.
> Thanks in advance..
>
>|||I'm sorry if I didn't make myself clear, what I did was uninstall SQL2000
and afterwards install SQL2005 on the same machine (WindowsServer2003).
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:82ECF7F8-D4A2-4213-9A68-76656BC41C79@.microsoft.com...
> Hi
> The version numbers in your post seem to be inconsistent!
> I assume that you have removed SQL 2000 and only have a named instance of
> SQL 2005. If you want the instance of SQL 2005 to be the default instance
> you
> will need to install SQL 2005 again anyhow, and possibly remove the named
> instance of SQL 2005 if it is not wanted. If you want to reinstall the
> current named instance you can install it from the command line with the
> REINSTALLMODE=OMUS option see
> http://msdn2.microsoft.com/en-us/library/ms144259.aspx#reinstallmode
> REINSTALLMODE=O will replace the missing file, but it would probably not
> do
> any harm having the other options.
> John
> "PG" wrote:
>> Hi everybody I had a server with SQL2000 Standard on Server2003 Standard
>> working, but I was told to uninstall and install SQl2005 Standard, but
>> now
>> when I start the server I receive an error saying that a service could
>> not
>> start, I went to see what service the server was talking about and it was
>> the Microsoft Search service. The error says that the specified file
>> can't
>> be found, so I went to "C:\Program Files\Common
>> Files\System\MSSearch\Bin\mssearch.exe" and the file mssearch.exe is
>> missing!!!
>> Was it the uninstall of SQL2000 that screwed this up, or the installation
>> of
>> SQL2005?
>> I dont know what to do from here, what can I do?...Any help would be
>> appreciated.
>> Thanks in advance..
>>|||Hi
"PG" wrote:
> I'm sorry if I didn't make myself clear, what I did was uninstall SQL2000
> and afterwards install SQL2005 on the same machine (WindowsServer2003).
>
mssearch.exe is for SQL 2000 if you want to reinstall it see
http://support.microsoft.com/default.aspx/kb/827449 but if you have SQL 2005
you should see an instance of SQL Server FullText Search (MSSQLSERVER) in
your services which runs "C:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\Binn\msftesql.exe". The article also shows how to
remove it.
John

Microsoft Search service can't start after SQL2005 installation!

Hi everybody I had a server with SQL2000 Standard on Server2003 Standard
working, but I was told to uninstall and install SQl2005 Standard, but now
when I start the server I receive an error saying that a service could not
start, I went to see what service the server was talking about and it was
the Microsoft Search service. The error says that the specified file can't
be found, so I went to "C:\Program Files\Common
Files\System\MSSearch\Bin\mssearch.exe" and the file mssearch.exe is
missing!!!
Was it the uninstall of SQL2000 that screwed this up, or the installation of
SQL2005?
I dont know what to do from here, what can I do?...Any help would be
appreciated.
Thanks in advance..Hi
The version numbers in your post seem to be inconsistent!
I assume that you have removed SQL 2000 and only have a named instance of
SQL 2005. If you want the instance of SQL 2005 to be the default instance yo
u
will need to install SQL 2005 again anyhow, and possibly remove the named
instance of SQL 2005 if it is not wanted. If you want to reinstall the
current named instance you can install it from the command line with the
REINSTALLMODE=OMUS option see
http://msdn2.microsoft.com/en-us/li...x#reinstallmode
REINSTALLMODE=O will replace the missing file, but it would probably not do
any harm having the other options.
John
"PG" wrote:

> Hi everybody I had a server with SQL2000 Standard on Server2003 Standard
> working, but I was told to uninstall and install SQl2005 Standard, but now
> when I start the server I receive an error saying that a service could not
> start, I went to see what service the server was talking about and it was
> the Microsoft Search service. The error says that the specified file can't
> be found, so I went to "C:\Program Files\Common
> Files\System\MSSearch\Bin\mssearch.exe" and the file mssearch.exe is
> missing!!!
> Was it the uninstall of SQL2000 that screwed this up, or the installation
of
> SQL2005?
> I dont know what to do from here, what can I do?...Any help would be
> appreciated.
> Thanks in advance..
>
>|||I'm sorry if I didn't make myself clear, what I did was uninstall SQL2000
and afterwards install SQL2005 on the same machine (WindowsServer2003).
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:82ECF7F8-D4A2-4213-9A68-76656BC41C79@.microsoft.com...[vbcol=seagreen]
> Hi
> The version numbers in your post seem to be inconsistent!
> I assume that you have removed SQL 2000 and only have a named instance of
> SQL 2005. If you want the instance of SQL 2005 to be the default instance
> you
> will need to install SQL 2005 again anyhow, and possibly remove the named
> instance of SQL 2005 if it is not wanted. If you want to reinstall the
> current named instance you can install it from the command line with the
> REINSTALLMODE=OMUS option see
> http://msdn2.microsoft.com/en-us/li...x#reinstallmode
> REINSTALLMODE=O will replace the missing file, but it would probably not
> do
> any harm having the other options.
> John
> "PG" wrote:
>

Microsoft OLE DB Provider for DB2 in SSIS vs. ODBC in DTS

I finally made data transfer between AS400 and SQL2005 work by using Microsoft OLE DB provider for DB2. I have tried other methods, some do not have build-in destination, some have unicode conversion problem. The only issue I have with this method is the peformance. For example, 300,000 rows load from AS400 take only 3 minutes with the ODBC connection in DTS, but more than 5 minutes with the microsoft OLD DB provider for DB2 in SSIS.

Does anyone have the same issue or figured out any tweaking that may speed up the transfer?

Thanks.

In the 5 minute example, what was your destination?|||The destination is the same - an OLE DB connection that connect to a SQL 2005 server.|||

Jane2006 wrote:

The destination is the same - an OLE DB connection that connect to a SQL 2005 server.

And are you using the "fast load" option?|||

Since I also need to load data back from SQL2005 to AS400, I could not use ADO.NET/ODBC method unless as someone else suggested, build a component for that missing destination microsoft does not have time to build. Also, the unicode issue drives me crazy. So I decide to use Microsoft OLE DB Provider for DB2.

Based on my experience, only the version released in April 2007 is good on 64-bit machine. The old versions did not work on our 64-bit machine even thought it said it should.

|||

Are you talking about the Data access mode in OLE DB Destination Editor? Yes. I am using the fast load. Actually this is a default unless changed.

|||

Jane2006 wrote:

Since I also need to load data back from SQL2005 to AS400, I could not use ADO.NET/ODBC method unless as someone else suggested, build a component for that missing destination microsoft does not have time to build. Also, the unicode issue drives me crazy. So I decide to use Microsoft OLE DB Provider for DB2.

Based on my experience, only the version released in April 2007 is good on 64-bit machine. The old versions did not work on our 64-bit machine even thought it said it should.

This is irrelevant. On the OLE DB destination, are you using the "Table or view - fast load" option when loading your results from AS400 to SQL Server?|||Yes. I think there must be some settings in Microsoft Provider OLE DB Provider for DB2 that needs to be tuned up. I just don't know where.|||How many rows are you retrieving and what is your MaxInsertCommitSize set to?|||Retrieving 3048740 rows from AS400. Maximum insert commit size is 0.|||Try setting MaxInsertCommitSize to 20000 and see what happens.|||Just give it a try. Not much difference. Still more than 5 minutes.|||Any transformations? Or just source -> destination?

Are you specifying a query in the source connection, or selecting a table from the drop down list?|||The one fundamental difference here is that you are using a Microsoft DB2 driver. It isn't a native AS400 driver. It's a 3rd party driver as far as connecting to the mainframe is concerned. You can download the IBM DB2 driver and you might have luck with that.

This isn't the same as using ODBC, which would (perhaps) use a native driver to connect.|||

No transformation. A straight source to destination. I am using SQL commnd for this particular one.

I have used tables in other scenarions as well. The row sizes are much smaller than this one, but ODBC consistently has better performance, even though only several seconds better.