"The system cannot find the file specified" upon login

I recently upgraded my WinXP Pro SP2 PC from SQL Server 2000 to SQL Server 2005. After a subsequent reboot and login, I saw a generic error message:

Error
The system cannot find the file specified.
OK

I didn't think much of it the first time, but it appears each time I reboot.

Sysinternals' Process Explorer identified the error dialog with C:\Program Files\Microsoft SQL Server\80\Tools\Binn\sqlmangr.exe. I just realized today that upon pressing the OK button, SQL Server Service Manager appears in my system tray, with a solid white circle. Upon opening Service Manager, the Services list is empty. The status bar says it is "Not Connected". I figured the entire ..\80 directory had been removed as part of the 2000-to-2005 upgrade; however, the directory and .exe do exist. Is this normal?

Any suggestions on how to proceed?

I think your problem was caused by the SQL 2000 install. I had an old Beta 2 copy of SQL 2000 on my development system, which had long since expired, and I ran into the same problem trying to install SQL 2005 Express. I suspect you have found a solution by now, but in case someone else runs into the same problem just uninstall SQL 2005, uninstall SQL 2000 and then install SQL 2005.

I had to uninstall SQL 2000 manually by following the instructions at the following link.

http://support.microsoft.com/kb/290991/en-us

sql

"The system cannot find the file specified" upon login

I recently upgraded my WinXP Pro SP2 PC from SQL Server 2000 to SQL Server 2005. After a subsequent reboot and login, I saw a generic error message:

Error
The system cannot find the file specified.
OK

I didn't think much of it the first time, but it appears each time I reboot.

Sysinternals' Process Explorer identified the error dialog with C:\Program Files\Microsoft SQL Server\80\Tools\Binn\sqlmangr.exe. I just realized today that upon pressing the OK button, SQL Server Service Manager appears in my system tray, with a solid white circle. Upon opening Service Manager, the Services list is empty. The status bar says it is "Not Connected". I figured the entire ..\80 directory had been removed as part of the 2000-to-2005 upgrade; however, the directory and .exe do exist. Is this normal?

Any suggestions on how to proceed?

I think your problem was caused by the SQL 2000 install. I had an old Beta 2 copy of SQL 2000 on my development system, which had long since expired, and I ran into the same problem trying to install SQL 2005 Express. I suspect you have found a solution by now, but in case someone else runs into the same problem just uninstall SQL 2005, uninstall SQL 2000 and then install SQL 2005.

I had to uninstall SQL 2000 manually by following the instructions at the following link.

http://support.microsoft.com/kb/290991/en-us

"Logon failure: unknown user name or bad password"

First, I checked all the obvious problems. The password is right and the login works perfectly.
Here is the output from Developer Studio when trying to deploy/process a cube:

Performing an incremental deployment of the 'MaxMinManufacturingDM' database to the 'localhost' server.
Generating deployment script...
Process Database MaxMinManufacturingDM
Done
Sending deployment script to the server...
Error -1056899072 : The following system error occurred: Logon failure: unknown user name or bad password. .
Error -1055784860 : Errors in the high-level relational engine. A connection could not be made to the data source with the DataSourceID of 'Max Min Manufacturing DM', Name of 'Max Min Manufacturing DM'.
Error -1054932980 : Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'Manufacturing Fact', Name of 'Dim Time' was being processed.
Error -1054932979 : Errors in the OLAP storage engine: An error occurred while the 'Year Of Manufacture' attribute of the 'Dim Time' dimension from the 'MaxMinManufacturingDM' database was being processed.

My Analysis Services project (or Business Intelligence project) has only one Data Source, "Max Min Manufacturing DM.ds". I'm using a SQL Server login with a saved password.

I double click the data source to get to the "Data Source Designer" dialog and see the following connection string:

Provider=SQLNCLI.1;Data Source=localhost;Persist Security Info=True;Password=**********;User ID=MaxMinUser;Initial Catalog=MaxMinManufacturingDM

I click "Edit" and "Test Connection" and get "Test connection succeeded". The "Save my password" option is checked. The password is fine and the login should works perfectly. Developer Studio can obviously connect to the database since I've done all the design through it. I can't imagine why I'm getting this error.

I'm using:

Windows XP (dev machine)
Relational Data Mart is using SQL Server 2000 SP4 (I can't upgrade to SQL Server 2005 for business reasons beyond my control)
Visual Studio Studio 2005
SQL Server Analysis Services 2005 (I believe I put SP1 on this).

Any idea?

Hello. Are you running the SQL Server services and the SSAS2005 services with the same or different accounts?

When you process a cube the SSAS2005 must have permissions to read data from the source database. If you run SSAS2005 on a separate machine than the sourec database and the SSAS2005 service account is running as "local system" this server have no permissions on other servers/machines.

You can check this is the SQL Server Configuration manager(for SSAS2005).

Also, try the default impersonation mode for the data source connection.

HTH

Thomas Ivarsson

|||Great!!! Setting the "impersonation mode" to default worked. I guess I should read up on that so I understand what the difference between the impersonation mode and the database login is.

Yes, everything is running on the same server (it's a development box): SSAS2005, MSSQL2000, and Visual Studio.

"Cannot apply value null to property Login: Value cannot be null..".

I'm trying to use a transfer "SQL Server Objects Task" between a 2005 SQL Server Database and a 2000 SQL Sever Database. I have the login info specified in the connection I'm using.
According to the Debug Output the process truncates the destination tables but then stops with the: "Cannot apply value null to property Login: Value cannot be null..".
Any help anybody?
NFThis probably means that you need to specify a login to use in the transfer.

Could you repost this in the SSIS forum? (http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=80&SiteID=1)|||

I had the same problem and I was specifying the sa login for my connection. When I tested the connection everything worked fine. But I received the same error message when I attempted to execute the package. I changed it to Windows Authentication and it worked fine. Unfortunately, I have to be able to specify a SQL login when I roll this into production.

I have tried all of the PackageProtectionLevels, but none seem to work. Any help would be greatly appreciated.

|||

I had the same problem. I installed SQL 2005 SP1 and it worked for me with SQL authentication.

|||

Unfortunately I’m using SSIS between a SQL 2000 (local) & SQL 2005 (remote). If I install SQL 2005 SP1 on my machine will that cure this problem – meaning, will the SSIS tools work properly?

-Cheers

|||Try changing your compatability level of the database to 2005

"Cannot apply value null to property Login: Value cannot be null..".

I'm trying to use a transfer "SQL Server Objects Task" between a 2005 SQL Server Database and a 2000 SQL Sever Database. I have the login info specified in the connection I'm using.
According to the Debug Output the process truncates the destination tables but then stops with the: "Cannot apply value null to property Login: Value cannot be null..".
Any help anybody?
NFThis probably means that you need to specify a login to use in the transfer.

Could you repost this in the SSIS forum? (http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=80&SiteID=1)|||

I had the same problem and I was specifying the sa login for my connection. When I tested the connection everything worked fine. But I received the same error message when I attempted to execute the package. I changed it to Windows Authentication and it worked fine. Unfortunately, I have to be able to specify a SQL login when I roll this into production.

I have tried all of the PackageProtectionLevels, but none seem to work. Any help would be greatly appreciated.

|||

I had the same problem. I installed SQL 2005 SP1 and it worked for me with SQL authentication.

|||

Unfortunately I’m using SSIS between a SQL 2000 (local) & SQL 2005 (remote). If I install SQL 2005 SP1 on my machine will that cure this problem – meaning, will the SSIS tools work properly?

-Cheers

|||Try changing your compatability level of the database to 2005

"Cannot apply value null to property Login: Value cannot be null..".

I'm trying to use a transfer "SQL Server Objects Task" between a 2005 SQL Server Database and a 2000 SQL Sever Database. I have the login info specified in the connection I'm using.
According to the Debug Output the process truncates the destination tables but then stops with the: "Cannot apply value null to property Login: Value cannot be null..".
Any help anybody?
NFThis probably means that you need to specify a login to use in the transfer.

Could you repost this in the SSIS forum? (http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=80&SiteID=1)|||

I had the same problem and I was specifying the sa login for my connection. When I tested the connection everything worked fine. But I received the same error message when I attempted to execute the package. I changed it to Windows Authentication and it worked fine. Unfortunately, I have to be able to specify a SQL login when I roll this into production.

I have tried all of the PackageProtectionLevels, but none seem to work. Any help would be greatly appreciated.

|||

I had the same problem. I installed SQL 2005 SP1 and it worked for me with SQL authentication.

|||

Unfortunately I’m using SSIS between a SQL 2000 (local) & SQL 2005 (remote). If I install SQL 2005 SP1 on my machine will that cure this problem – meaning, will the SSIS tools work properly?

-Cheers

|||Try changing your compatability level of the database to 2005

"Cannot apply value null to property Login: Value cannot be null..".

I'm trying to use a transfer "SQL Server Objects Task" between a 2005 SQL Server Database and a 2000 SQL Sever Database. I have the login info specified in the connection I'm using.
According to the Debug Output the process truncates the destination tables but then stops with the: "Cannot apply value null to property Login: Value cannot be null..".
Any help anybody?
NF
This probably means that you need to specify a login to use in the transfer.

Could you repost this in the SSIS forum? (http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=80&SiteID=1)|||

I had the same problem and I was specifying the sa login for my connection. When I tested the connection everything worked fine. But I received the same error message when I attempted to execute the package. I changed it to Windows Authentication and it worked fine. Unfortunately, I have to be able to specify a SQL login when I roll this into production.

I have tried all of the PackageProtectionLevels, but none seem to work. Any help would be greatly appreciated.

|||

I had the same problem. I installed SQL 2005 SP1 and it worked for me with SQL authentication.

|||

Unfortunately I’m using SSIS between a SQL 2000 (local) & SQL 2005 (remote). If I install SQL 2005 SP1 on my machine will that cure this problem – meaning, will the SSIS tools work properly?

-Cheers

|||Try changing your compatability level of the database to 2005

<Alter Login sa - SQL 2005 - Login Failed>

Hi all, i issued the alter login sa name = [xxxsa] on SQL Server 2005. After
doing this, i cannot login using the sa or xxxsa user id. It keeps telling me
that login failed.
How i can i login back?
Thanks
I figured out the problem. When i changed the login to xxxsa, SQL Server
changed the login to 'xxxsa' (with the quotes). When i used the login with
the quotes, it worked.
"Houston Lucifer" wrote:

> Hi all, i issued the alter login sa name = [xxxsa] on SQL Server 2005. After
> doing this, i cannot login using the sa or xxxsa user id. It keeps telling me
> that login failed.
> How i can i login back?
> Thanks
>

<Alter Login sa - SQL 2005 - Login Failed>

Hi all, i issued the alter login sa name = [xxxsa] on SQL Server 2005. A
fter
doing this, i cannot login using the sa or xxxsa user id. It keeps telling m
e
that login failed.
How i can i login back?
ThanksI figured out the problem. When i changed the login to xxxsa, SQL Server
changed the login to 'xxxsa' (with the quotes). When i used the login with
the quotes, it worked.
"Houston Lucifer" wrote:

> Hi all, i issued the alter login sa name = [xxxsa] on SQL Server 2005.
After
> doing this, i cannot login using the sa or xxxsa user id. It keeps telling
me
> that login failed.
> How i can i login back?
> Thanks
>

<Alter Login sa - SQL 2005 - Login Failed>

Hi all, i issued the alter login sa name = [xxxsa] on SQL Server 2005. After
doing this, i cannot login using the sa or xxxsa user id. It keeps telling me
that login failed.
How i can i login back?
ThanksI figured out the problem. When i changed the login to xxxsa, SQL Server
changed the login to 'xxxsa' (with the quotes). When i used the login with
the quotes, it worked.
"Houston Lucifer" wrote:
> Hi all, i issued the alter login sa name = [xxxsa] on SQL Server 2005. After
> doing this, i cannot login using the sa or xxxsa user id. It keeps telling me
> that login failed.
> How i can i login back?
> Thanks
>