If you re-attach a db to a different server, presumably you are shutting out your users (by them not having logins to the new server). If you are moving to a different domain I can only think that having the sa pwd and switching to "Mixed Authentication" would be the only way to get back in to start adding new logins/users, is that correct?
View 2 RepliesHey!
I need help getting all the users that are "attached" or "allowed" to access a given database and their login information. I do not know if this is even possible but I had tried to do my own research and cant figure it out/find any info on it. Any help is greatly appreciated!
Thank you!
-Teenprogrammer
Hello, there this is my first post and Iīm desperate seeking for help, I have almost not knowledge of SQL as it is not my usual work.
However, suddenly it has converted in mine....Hopefully I will got help in here.
Well the issue is that our database manager has resigned suddenly and before doing it he has changed the passwords of all the users in
our database of a monitoring web application. So all our users have no access now to the application. After many tryouts I finally got
access to the database and to the users table. However I have the issue that the passwords looks as below showed and I donīt know what
the real password is.
I have tried to decrypt using web decrypting pages as it looks like normal base64 strings, but it returns weird stuff. Also as I donīt
know the real encryption used I canīt change to a know string. So if some could help me getting how it was encrypted or better to find
out the real passwords it will be truly appreciated. If it is needed more info please tell me so I can send it to you, or if you need the
database itself I can send you a backup.
Best Regards to everyone.
Quote:
NumberUSERNAMEPassword
11***uFHNaI0yloE=
22***uQ7f4zrS+I8=
33***vZLMcLSYGgU=
44***X1huNktKxiE=
55***Xj7X/j7IJlY=
66***xnjJfMyiK24=
77***YcQhuzE8ZKM=
88***yPkatR/yu34=
99***Z/+ujjLnAPI=
1010***Z/+ujjLnAPI=
1111***/E4vCqpZ0HWGa5akKPfeGg==
1212***+/IkfCripBiyGKX+0BOq5Q==
1313***+wv6aVBpAdoaVOIop5k7hA==
1414***0Xn9c0+SZLfFS+jEYqBUuQ==
1515***1CvLvdtfMemipN6agFOUcw==
1616***1YVYxTctsZlar9Vv7btVTw==
1717***4PVwBey0bOkwC3NA183F5g==
1818***5thrQN8LxHNhaMr4RJz1Bg==
1919***6qk+WBaRa9+GiOdvR5pEjw==
i restored a database from a .bak file.
from production to development.
But i dropped the database from development before restoring. Now all the users are gone from this database. Anyone know how to recover them?
the users from development are different from production's
We have an existing SSRS server, and have just created a new child domain. We'll be migrating users from the parent to the child, and want to add the users of that new domain with access to SSRS. In the parent domain they are able to access, but after migration with the child domain account, they cannot.
I have added the group CHILDDomain Users with a system user role on SSRS, and PARENTDomain Users was already there.
Is there any additional step I should/could take to get this active?
I have had this issue just pop up. I have local users who can connect fine, but my users that require connection by VPN cannot connect. I get the server not available or access denied error. I did confirm that the VPN'ers are connected to the network correctly and can see that their shares and mappings are correct. Any ideas? Thanking you all in advance!!
View 6 Replies View RelatedI am trying to revert back to Windows 7 after upgrading to Windows 10, however it will not let me and the following message occurs: "Remove new accounts.Before you can go back to a previous version of Windows, you'll need to remove any user accounts you added after the most recent upgrade. The accounts need to be completely removed, including their profiles.You created one account (NT SERVICEMSSQLSERVER) Go to Settings> Accounts> Other users to remove these accounts and then try again".However I did not create any new users and there are no other users listed in the Accounts section.
View 2 Replies View Relatedhi alli've got two tables called "webusers" (id, name, fk_country) and "countries" (id, name)
at the meantime, i've a search-page where i can fill a form to search users. in the dropdown to select the country i included an option which is called "all countries".
now the problem is: how can i make a stored procedure that makes a restriction to the fk_country depending on the submitted fk_country parameter?it should be something like
SELECT * FROM webusers(if @fk_country > 0, which is the value for "all countries"){ WHERE fk_country = @fk_country}
who has an idea how to solve this problem?
Hi. I am using VS 2005 and I want to create a database file (mdf) and have it on my server, but not have it attach to an instance of SQL server. Is this possible? The hosting I am using only allows for 1 SQL DB, and obviously doesn't allow you to attach instances of a DB. I would rather go with an mdf file that access, but not sure if this is possible. If anyone knows if it is and how to pull it off it would be GREAT!!
View 7 Replies View Relatedhow can i attached MDF file only without .log and data only
View 6 Replies View RelatedI have two programs which access sql server 2005. One was written in vb6 the other in vb8 (aka vb.net 2005).
vb6 works well with this connection string:
Provider=SQLNCLI;Integrated Security=SSPI;Persist Security Info=False;Database=MyDbName;Data Source=.MyServerInstanceName
vb8 (in vs2005) generated the following connection string which works well in the vb8 application:
Data Source=.MyServerInstanceName;AttachDbFilename='C:MyDbPathMyDbName.mdf';Integrated Security=True
Within their own programs each connection string works well. However, if I use one program and then the other (e.g., vb8 program then vb6), I get an error message:
Unable to open the physical file "C:MyDbPathMyDbName.mdf". Operating system error 32: "32(The process cannot acces the file because it is being used by another process.)".
If I detach the database using SSMS, I can then access it with the other program. Obviously, this is not an ideal situation and not something I would want the end user to have to do.
Also, when using the vb6 connection string, SSMS lists the database in Object Explorer as: MyDbName. When using the vb8, the database is listed as C:MyDbPathMyDbName.mdf. BTW, the database is set for multi-user.
How can I get the two programs to place nice together?
Hi,
I was trying to figure out how to back up a database that has been attached to the SQL Express instance. I found on the web this tutorial and tried to use it, however it seems like it cannot find the database. The DB is attached by the web application using AttachDbFilename in the connectionstring.
http://www.sqldbatips.com/showarticle.asp?ID=27
Any ideas?
thanks
I used Query Analyser to De-tach a SQL 7 database and that worked fine. The database became 'invisible' in Enterprise Manager and the entry was removed from the sysdatabases in Master. The mdf and ldf file remain in the file system. However, when I ran the sp to Attach the database QA said successful but it does not show in Enterprise Manager or in sysdatabases in Master. I'm going to run through the procedure again and if problems I'll check the logs but has anyone else had difficulty with this. Also with attaching the db to a SQL2000 install I believe the logins on the SQL7 install are not brought over. In my case, the client is using trusted logins with their database application so their is probably not a lot to manually recreate on the SQL 2000 install but doees anyone have nay sample code/script that can give me an idea of what is required in the area of getting logins out of the Master of SQL7 and into SQL2000.
Great forum...
Have a great day,
ChrisE
Is there a stored procedure to list attached databases?
You can do this:
use Master
exec sp_helpfile
go
Which shows you the config files for the current DB.
What if you want to do a multiple sp_detach_db? If you could get a list of the attached DB's you could recursilvely or conditioinaly detach.
Hello all,
I'm using SQL 2005 Express edition. I'm currently connecting to the database file directrly (from ASP.NET) and that db file is not attached to the server.
My question is this:
What is the difference ? Will the performance improve if the db is attached and I connect to it throught the server ? I'm really not sure what the difference is.
Thanks
How can I, programatically, get a list of attached databases? I'm using VB.
View 4 Replies View RelatedHi Team,
In SQL Enterprise Manager, when we expand "Database -->Users", we see the
users there. When we expand "Security --> logins" we see the same users there.
Can you differentiate these two.
Thanks
Santhosh
When you have SQL Server Express installed, and you drop a database in App_Code it will be attached and you can browse it with Server Explorer in Visual Studio. Same when you choose Website -> ASP.NET Configuration, you get a new ASPNETDB database in App_Code and it will be attached.My question: is it normal behaviour that I cannot see these databases in the Object Browser in SQL Server Management Studio?For the record: I also have SQL Server 2005 Dev installed, so the Management Studio I have is not the Express edition.
View 4 Replies View Relatedi'm building a web page to help our support staff run and export their sql queries faster and more easily than going through the sql server manager. i found an article at codeproject [1] that i was able to customize to be more flexible, but i'm not sure how to get it to export the results of a query along with the comments that preceed the query.
for example, i have the following sql file: -- this query does a certain thing, and the comment can be pretty long at times, depending on how complicated the query is
select * from table where columnid > 100would anyone be able to tell me how to edit Kolluri's export function to allow for a comment section? alternatively if his way of doing an export is out of date, i'd be interested in a newer way. most importantly, though, i need to be able to export the comments along with query results.my ultimate goal is to have a drop down list of databases on the server, a list of query files (from a certain consolodated folder) for them to run on the chosen database, a "test query" function, and an export function that exports the comments and results.[1] http://www.codeproject.com/aspnet/ExportClassLibrary.asp
I attach my SQL Server Express data file to my host. I would like to copy all of my member information back to my local computer. How can I do this? My host won't allow my to physically copy the data file over. My host is discountasp.net. Thanks,Jeff
View 1 Replies View RelatedI need to get a unique value to use for a record *before* the record is added to a table. It doesn't have to be contiguous with existing records, but it must always be unique, has to be persistent over multiple instantiations of an ASP.NET application, and has to work in that sort of a multi-session environment (where other sessions could need additional unique values before the first session gets around to actually adding a record to the table).
I considered generating and using unique CLSIDs for this, but the resulting value also needs to become part of the filename of some files that are being saved to the disk (and those names also saved in the table), and including text CLSIDs along with other filename data would make for some unpleasantly long and difficult to work with filenames.
I also don't think there's a practical way for me to use a trigger associated with an identity column for this, because I need to save files to disk using the unique value before I even know if the record will in fact end up being added to the table, and what's more, the numbers and names of those files will vary in ways that might be difficult to handle in a stored procedure.
What I'm thinking I will have to do is create a separate database table called something like "UniqueIDGen". This table would have a single record in it with a single integer value, initialized to a value of 1. Then, each time an ID is needed, this one record would be locked, read and incremented by 1. The only reason for doing it this way instead of with an application variable, as I see it, is that the values need to be unique and continue incrementing in perpetuity, no matter how many times the ASP.NET application is recycled or the server is rebooted.
But I still have to wonder if there might be a more efficient method provided by SQL Server for this type of unique value generation ... something that is equally as persistent without requiring an entire table with only a single record to be allocated to such a basic task. Does anyone know of a more elegant solution for this?
I'm having some problems with SQL Server 2005. I installed the Personal Starter kit but don't have the Express edition installed so I attached the .mdf file to SQL Server 2005. That's ok and I also changed the connection string to integrated security.<add name="Personal" connectionString="Data Source=MyTestServer;Initial Catalog=Personal;Integrated Security=True" providerName="System.Data.SqlClient"/>I tried setting the security settings in the Management studio under Security | Logins | BUILTINAdministrators where I select the User mapping and check the checkbox before the Personal.mdf file. But this doesn't seem to do the trick. How can I set the correct security settings?
View 2 Replies View RelatedHi, paws.
My server crashed recently, I didn't give to much importance because I knew that having access to the partitions I could recover my DB files and attach my database to my new server, and everything was fine until ... I found that my DTS Packages and Jobs where not in my Attached DB.
Now, where can I find these ?
Can you help a tormented man ?
Thanks in advance.
Francisco J
I attached my database to SQL 2005 but it's showing up as read-only for some reason. I've attached this before just fine in another instance of the Vista OS. Why would it attach differently this time compared to all other times and show read only?
The .mdb and .ldf files are not read only if you right-click and check out their properties.
The upgrade to SQL 2k5 SP1 fails to upgraede the Database Services. Attached is the log. Will work for help.
05/24/2006 16:19:47.500 ================================================================================
05/24/2006 16:19:47.500 Hotfix package launched
05/24/2006 16:19:53.687 Product discovery successfully completed during the install process for MSSQLSERVER
05/24/2006 16:19:53.687 SP Level check successfully completed during the install process for MSSQLSERVER
05/24/2006 16:19:53.687 Product language check successfully completed during the install process for MSSQLSERVER
05/24/2006 16:19:53.687 Product version check successfully completed during the install process for MSSQLSERVER
05/24/2006 16:19:53.687 Command-line instance name check completed during the install process
05/24/2006 16:19:53.687 Baseline build check completed during the install process
05/24/2006 17:08:03.187 Attempting to install instance: MSSQLSERVER
05/24/2006 17:08:03.281 Attempting to install target: TERRANCE
05/24/2006 17:08:03.375 Attempting to stop service: SQLSERVERAGENT
05/24/2006 17:08:11.093 Successfully stopped service: SQLSERVERAGENT
05/24/2006 17:08:11.109 Attempting to stop service: MSSQLServer
05/24/2006 17:08:18.625 Successfully stopped service: MSSQLServer
05/24/2006 17:08:19.031 Attempting to check for locked files: sqlrun_sql.msp
05/24/2006 17:08:21.390 Attempting to check for locked files: \TERRANCEe$6d48928b5baeb824319ba523e3fdHotFixSQLFilessqlrun_sql.msp
05/24/2006 17:08:21.406 Creating MSP locked file check log at: C:WINDOWSHotfixSQL9LogsSQL9_Hotfix_KB913090_sqlrun_sql.msp.out
05/24/2006 17:09:22.343 MSP returned 1602: The user cancels installation.
05/24/2006 17:09:22.375 Successfully checked file: \TERRANCEe$6d48928b5baeb824319ba523e3fdHotFixSQLFilessqlrun_sql.msp
05/24/2006 17:09:22.468 Successfully opened registry key: SystemCurrentControlSetControlSession Manager
05/24/2006 17:09:22.468 Failed to read registry key: PendingFileRenameOperations
05/24/2006 17:09:22.484 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnxmlfilt.dll
05/24/2006 17:09:22.484 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnThaWBrkr.dll
05/24/2006 17:09:22.484 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnquery.dll
05/24/2006 17:09:22.484 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnls400.dll
05/24/2006 17:09:22.484 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnlhtml.dll
05/24/2006 17:09:22.500 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnmsir5jp.dll
05/24/2006 17:09:22.500 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnmsftesql.exe
05/24/2006 17:09:22.500 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnmsftepxy.dll
05/24/2006 17:09:22.500 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnmsftefd.exe
05/24/2006 17:09:22.515 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnmsfte.dll
05/24/2006 17:09:22.515 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnLangWrbk.dll
05/24/2006 17:09:22.515 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnkorwbrkr.dll
05/24/2006 17:09:22.515 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinninfosoft.dll
05/24/2006 17:09:22.515 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnFTERefFTERef.dll
05/24/2006 17:09:22.515 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnCHTBRKR.DLL
05/24/2006 17:09:22.531 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnChsBrkr.dll
05/24/2006 17:09:22.531 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0
C:Program FilesMicrosoft SQL Server90COMResources1033REPLRES.rll
05/24/2006 17:09:22.531 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0
C:Program FilesMicrosoft SQL Server90COM
eplrec.dll
05/24/2006 17:09:22.531 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0
C:Program FilesMicrosoft SQL Server90COM
plisapi.dll
05/24/2006 17:09:22.531 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0
C:WINDOWSassemblyGAC_32Microsoft.SqlServer.Replication9.0.242.0__89845dcd8080cc91Repl.dll
05/24/2006 17:09:22.531 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.DataStorage9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.DataStorage.dll
05/24/2006 17:09:22.531 Failed to read version information for the following file: C:Program FilesCommon FilesMicrosoft SharedDatabase ReplicationResources10332005.90.2047.0
E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLInstall
plhtfin.sql
05/24/2006 17:09:22.531 Failed to read version information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLInstall
C:Program FilesMicrosoft SQL Server90COMqrdrsvc.exe
05/24/2006 17:09:22.546 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0
C:Program FilesMicrosoft SQL Server90COMsnapshot.exe
05/24/2006 17:09:22.546 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0
C:Program FilesMicrosoft SQL Server90COM
eplmerg.exe
05/24/2006 17:09:22.546 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90COM ablediff.exe
05/24/2006 17:09:22.546 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0
C:Program FilesMicrosoft SQL Server90COMDISTRIB.exe
05/24/2006 17:09:22.609 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnDatabaseMail90.exe
05/24/2006 17:09:22.609 Failed to read version information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources30822005.90.2047.0
E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources2052sqlevn70.rll
05/24/2006 17:09:22.609 Failed to read version information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources10422005.90.2047.0
E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1041sqlevn70.rll
05/24/2006 17:09:22.609 Failed to read version information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources10402005.90.2047.0
E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1036sqlevn70.rll
05/24/2006 17:09:22.625 Failed to read version information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources10332005.90.2047.0
E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1031sqlevn70.rll
05/24/2006 17:09:22.625 Failed to read version information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources10282005.90.2047.0
E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033XPStar90.RLL
05/24/2006 17:09:22.625 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlaccess.dll
05/24/2006 17:09:22.625 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlaccess.dll
05/24/2006 17:09:22.625 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlaccess.dll
05/24/2006 17:09:22.625 Failed to read version information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn6.6.3.5
C:Program FilesMicrosoft SQL Server90Sharedmsxmlsql.dll
05/24/2006 17:09:22.640 Failed to read version information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn2.0.3609.0
E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnxmlrw.dll
05/24/2006 17:09:22.640 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlsvc90.dll
05/24/2006 17:09:22.640 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlsvc90.dll
05/24/2006 17:09:22.640 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlsvc90.dll
05/24/2006 17:09:22.640 Failed to read version information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn2005.90.2047.0
E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLBOOT.dll
05/24/2006 17:09:22.640 Failed to read version information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn2005.90.2047.0
E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnxplog70.dll
05/24/2006 17:09:22.640 Failed to read version information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn2005.90.2047.0
E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnatchp~1.dll
05/24/2006 17:09:22.640 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAgentMail90.rll
05/24/2006 17:09:22.656 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAgentMail90.rll
05/24/2006 17:09:22.656 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAgentMail90.rll
05/24/2006 17:09:22.656 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAGENT90.RLL
05/24/2006 17:09:22.656 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAGENT90.RLL
05/24/2006 17:09:22.656 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAGENT90.RLL
05/24/2006 17:09:22.656 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAgentMail90.dll
05/24/2006 17:09:22.671 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAgentMail90.dll
05/24/2006 17:09:22.687 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAgentMail90.dll
05/24/2006 17:09:22.703 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAGENT90.EXE
05/24/2006 17:09:22.703 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAGENT90.EXE
05/24/2006 17:09:22.718 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAGENT90.EXE
05/24/2006 17:09:22.718 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90SharedResources10339.0.2047.0
C:Program FilesMicrosoft SQL Server90Sharedmsmdrdir.dll
05/24/2006 17:09:22.734 Failed to read version information for the following file: C:Program FilesCommon FilesSystemole db2.0.3609.0
C:Program FilesCommon FilesSystemole dbxmlrw.dll
05/24/2006 17:09:22.750 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsmdlocal.dll
05/24/2006 17:09:22.750 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsmdlocal.dll
05/24/2006 17:09:22.765 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsmdlocal.dll
05/24/2006 17:09:22.781 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlbrowser.exe
05/24/2006 17:09:22.781 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlbrowser.exe
05/24/2006 17:09:22.796 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlbrowser.exe
05/24/2006 17:09:22.812 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsasxpress.dll
05/24/2006 17:09:22.812 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsasxpress.dll
05/24/2006 17:09:22.828 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsasxpress.dll
05/24/2006 17:09:22.859 Failed to read version information for the following file: C:Program FilesMicrosoft.NETADOMD.NET90enMicrosoft.AnalysisServices.AdomdClient.xml
05/24/2006 17:09:22.875 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft.NETADOMD.NET90Microsoft.AnalysisServices.AdomdClient.dll
05/24/2006 17:09:22.875 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.AnalysisServices.AdomdClient9.0.242.0__89845dcd8080cc91Microsoft.AnalysisServices.AdomdClient.dll
05/24/2006 17:09:22.875 Failed to read version information for the following file: E:Program FilesMicrosoft SQL Server90ToolsBinnResources1033
E:Program FilesMicrosoft SQL Server90ToolsBinnResources1033sqlcm.xml
05/24/2006 17:09:22.890 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL Server90ToolsBinnResources1033SqlManager.rll
05/24/2006 17:09:22.890 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL Server90ToolsBinnResources1033SqlManager.rll
05/24/2006 17:09:22.906 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL Server90ToolsBinnResources1033SqlManager.rll
05/24/2006 17:09:22.906 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL Server90ToolsinnSqlManager.dll
05/24/2006 17:09:22.921 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL Server90ToolsinnSqlManager.dll
05/24/2006 17:09:22.937 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL Server90ToolsinnSqlManager.dll
05/24/2006 17:09:22.953 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL Server90ToolsBinnatchparser90.dll
05/24/2006 17:09:22.953 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL Server90ToolsBinnatchparser90.dll
05/24/2006 17:09:22.968 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL Server90ToolsBinnatchparser90.dll
05/24/2006 17:09:22.968 Failed to read version information for the following file: E:Program FilesMicrosoft SQL Server90ToolsBinnResources10332005.90.2047.0
E:Program FilesMicrosoft SQL Server90ToolsinnSQLSVC90.DLL
05/24/2006 17:09:22.984 Failed to read version information for the following file: E:Program FilesMicrosoft SQL Server90ToolsBinn2.0.3609.0
E:Program FilesMicrosoft SQL Server90ToolsBinnSQLdiag.exe
05/24/2006 17:09:22.984 Failed to read version information for the following file: E:Program FilesMicrosoft SQL Server90ToolsBinn2005.90.2047.0
C:Program FilesMicrosoft SQL Server90Sharedsqlsvc~1.dll
05/24/2006 17:09:22.984 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlsecacctchg.dll
05/24/2006 17:09:23.000 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlsecacctchg.dll
05/24/2006 17:09:23.000 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlsecacctchg.dll
05/24/2006 17:09:23.015 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlftacct.dll
05/24/2006 17:09:23.015 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlftacct.dll
05/24/2006 17:09:23.015 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlftacct.dll
05/24/2006 17:09:23.015 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedisacctchange.dll
05/24/2006 17:09:23.015 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedisacctchange.dll
05/24/2006 17:09:23.015 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedisacctchange.dll
05/24/2006 17:09:23.031 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsvrenumapi.dll
05/24/2006 17:09:23.031 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsvrenumapi.dll
05/24/2006 17:09:23.031 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsvrenumapi.dll
05/24/2006 17:09:23.031 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90Shared2005.90.2047.0
C:Program FilesMicrosoft SQL Server90Sharedsqlsqm.exe
05/24/2006 17:09:23.031 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90Shared9.0.2047.0
C:Program FilesMicrosoft SQL Server90Shareddbghelp.dll
05/24/2006 17:09:23.031 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90SharedSqlDumper.exe
05/24/2006 17:09:23.046 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90SharedSqlDumper.exe
05/24/2006 17:09:23.046 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90SharedSqlDumper.exe
05/24/2006 17:09:23.046 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.Rmo9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.Rmo.dll
05/24/2006 17:09:23.046 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.AnalysisServices9.0.242.0__89845dcd8080cc91Microsoft.AnalysisServices.DLL
05/24/2006 17:09:23.046 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.DataWarehouse.Interfaces9.0.242.0__89845dcd8080cc91Microsoft.DataWarehouse.Interfaces.DLL
05/24/2006 17:09:23.046 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.RegSvrEnum9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.RegSvrEnum.dll
05/24/2006 17:09:23.062 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_32Microsoft.SqlServer.BatchParser9.0.242.0__89845dcd8080cc91microsoft.sqlserver.batchparser.dll
05/24/2006 17:09:23.062 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_32Microsoft.SqlServer.BatchParser9.0.242.0__89845dcd8080cc91microsoft.sqlserver.batchparser.dll
05/24/2006 17:09:23.062 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_32Microsoft.SqlServer.BatchParser9.0.242.0__89845dcd8080cc91microsoft.sqlserver.batchparser.dll
05/24/2006 17:09:23.062 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.ServiceBrokerEnum9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.ServiceBrokerEnum.dll
05/24/2006 17:09:23.062 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.WmiEnum9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.WmiEnum.dll
05/24/2006 17:09:23.078 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.SqlEnum9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.SqlEnum.dll
05/24/2006 17:09:23.078 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.SmoEnum9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.SmoEnum.dll
05/24/2006 17:09:23.078 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.Smo9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.Smo.dll
05/24/2006 17:09:23.078 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90SharedSqlSAC.exe
05/24/2006 17:09:23.078 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90SharedMicrosoft.SqlSac.Public.dll
05/24/2006 17:09:57.218 Attempting to install file: sqlrun_sql.msp
05/24/2006 17:09:57.609 Attempting to install file: \TERRANCEe$6d48928b5baeb824319ba523e3fdHotFixSQLFilessqlrun_sql.msp
05/24/2006 17:09:57.609 Creating MSP install log file at: C:WINDOWSHotfixSQL9LogsSQL9_Hotfix_KB913090_sqlrun_sql.msp.log
05/24/2006 17:09:57.609 Successfully opened registry key: SoftwarePoliciesMicrosoftWindowsInstaller
05/24/2006 17:09:57.609 Failed to read registry key: Debug
05/24/2006 17:15:25.375 MSP returned 1603: A fatal error occurred during installation.
05/24/2006 17:15:25.390 Successfully opened registry key: SoftwarePoliciesMicrosoftWindowsInstaller
05/24/2006 17:15:25.406 Failed to read registry key: Debug
05/24/2006 17:15:25.593 Unable to install MSP file: \TERRANCEe$6d48928b5baeb824319ba523e3fdHotFixSQLFilessqlrun_sql.msp
05/24/2006 17:15:25.593 The following exception occurred: Unable to install Windows Installer MSP file Date: 05/24/2006 17:15:25.593 File: depotsqlvaultsetupmainsetupsqlsesqlsedllcopyengine.cpp Line: 856
05/24/2006 17:15:25.937
05/24/2006 17:15:25.937 Product Status Summary:
05/24/2006 17:15:25.937 Product: SQL Server Native Client
05/24/2006 17:15:25.953 SQL Server Native Client (RTM ) - Success
05/24/2006 17:15:25.953
05/24/2006 17:15:25.953 Product: Setup Support Files
05/24/2006 17:15:25.953 Setup Support Files (RTM ) - Success
05/24/2006 17:15:25.953
05/24/2006 17:15:25.953 Product: Database Services
05/24/2006 17:15:25.953 Database Services (RTM 1399 ENU) - Failure
05/24/2006 17:15:25.953 Details: Unable to install Windows Installer MSP file
05/24/2006 17:15:25.953 Analysis Services (SP1 2047 ENU) - Not Applied
05/24/2006 17:15:25.953 Reporting Services (SP1 2047 ENU) - Not Applied
05/24/2006 17:15:25.953
05/24/2006 17:15:25.953 Product: Notification Services
05/24/2006 17:15:25.953 Notification Services (SP1 2047 ENU) - Not Applied
05/24/2006 17:15:25.953
05/24/2006 17:15:25.953 Product: Integration Services
05/24/2006 17:15:25.953 Integration Services (SP1 2047 ENU) - Not Applied
05/24/2006 17:15:25.968
05/24/2006 17:15:25.968 Product: Client Components
05/24/2006 17:15:25.968 Client Components (SP1 2047 ENU) - Not Applied
05/24/2006 17:15:25.968
05/24/2006 17:15:25.968 Product: MSXML 6.0 Parser
05/24/2006 17:15:25.968 MSXML 6.0 Parser (RTM ) - Not Applied
05/24/2006 17:15:25.968
05/24/2006 17:15:25.968 Product: SQLXML4
05/24/2006 17:15:25.968 SQLXML4 (RTM ) - Not Applied
05/24/2006 17:15:25.968
05/24/2006 17:15:25.968 Product: Backward Compatibility
05/24/2006 17:15:25.968 Backward Compatibility (RTM ) - Not Applied
05/24/2006 17:15:25.968
05/24/2006 17:15:25.968 Product: Microsoft SQL Server VSS Writer
05/24/2006 17:15:25.968 Microsoft SQL Server VSS Writer (RTM ) - Not Applied
05/24/2006 17:15:25.984
I attached .mdf and .ldf from the app_data folder in an asp.net web site. I set the configuration to SSPI. The trouble is, I get this error
requested by the login. The login failed.
Login failed for user 'IN-XYZmattaniah'.
If I create a database and connect to it using SSPI I do not get this error. I assume there is something I am missing.
Hello,
I was wondering about the principles of SQL Server. In all of my books, they show me to attach the DB, even create the DB through Visual Studio 2005. Which creates a .mdf file and a .ldf file.
Ok, but I cannot open those files through SQL Server Management. The only DB I am able to manage through SQL Server Management is the ones created with it.
So my question is: For a Multi-User type Application, is there a problem to attach a network based file through VS2005, the same way as an access file ?
Again my keyword here is Multi-User. Sorry if this myth be a stupid question but I am used to MSAccess. SQL Server is a lot more complexe and I don't want to start in the wrong direction.
Thank you for your response.
Hello all,
I'm using SQL 2005 Express edition. I'm currently connecting to the database file directrly (from ASP.NET) and that db file is not attached to the server.
My question is this:
What is the difference ? Will the performance improve if the db is attached and I connect to it throught the server ? I'm really not sure what the difference is.
Thanks
Hi there,
I need to extract a attached file which is sent via email. I believe that I can do this via SSIS... but I would like to know how...
Could you kindly send me any idea about how can I do it?
Thank you, so much.
Luis Antonio
Hi All
I am in process of moving a SQL 2005 solution from a development box that used local storage to UAT environment with SAN attached storage. The solution uses database snapshots
The database files are on the SAN storage but during testing I was unable to create a Database snapshot on the SAN disk. Creating snapshots on the local disk worked fine.
Is their some restriction/problem in using the database snapshot technology with SAN storage?
Hello,
I was using a SQL Express database for some time now with no problems for a NUnit Test project. No, all of a sudden, I'm getting these problems:
DatabaseProviderTest.TestContainsUser : System.Data.SqlClient.SqlException : Cannot open user default database. Login failed.Login failed for user 'XXXXXX'.
For the SQLEXPRESS database, I checked and I am a user, and I gave myself every permission imaginable. The default database is master, so I don't know why I am getting this problem?
Any ideas? Thanks.
Hi allI have a question concerning sql database mdf files. In the old days I would user a ms access database. This file would be stored with the actual web files and would utilise a dsn connection. I have noted when designing with vwd 2005 express it allows you to use 2 methods of creating a mdf database. You can either create it as an attachment mdf or you can create it directly using sql manager. My question is, if you create the mdf database as an attachement file can you store it in the same manner as if you where using a ms access database, meaning can you store it with the web site's files so it uses the file storage allocated size and then create a connection similar to a dsn (but for sql) to the isp's sql engine or does it have to be uploaded to the isp' s sql server.The reason for this question is some of my customers do not want to pay the extra cost to have an sql allocation, however I do not want to go back to using old asp methods to create advanced sites as I prefer using stored procedures. Any help will be appreciated
View 4 Replies View RelatedWhy in the hell doesn't SQL Server provide a facility for dropping anactive connection on an attached database in SQL Server Managementconsole? I can't detach an attached database because apparently thereis an active connection.I know you can use SSEUTIL but it seems like kluge for a poorlythought out function.Crazy
View 2 Replies View Related