Thursday, March 29, 2012
can't conect remotely to SQL Express
connection string that I use.
cn.ConnectionString = "Provider=SQLNCLI;Network Library=DBMSSOCN;Integrated
Security=SSPI;"Server=192.168.10.243\SQLEXPRESS,1433;" & _
"database=CopyRequest"
I get "Login failed for user 'ILYA-TEST-PC\Guest'" error when I try to
connect. What is the cause of this error? I allow remote connections on SQL
Server.Hi
Have you checked the permissions for 'ILYA-TEST-PC\Guest' ?
John
"Ilya" wrote:
> I am connecting remotely to SQL Express using my VB application. Here is t
he
> connection string that I use.
> cn.ConnectionString = "Provider=SQLNCLI;Network Library=DBMSSOCN;Integrate
d
> Security=SSPI;"Server=192.168.10.243\SQLEXPRESS,1433;" & _
> "database=CopyRequest"
> I get "Login failed for user 'ILYA-TEST-PC\Guest'" error when I try to
> connect. What is the cause of this error? I allow remote connections on SQ
L
> Server.|||Guest is disabled by default. I assume you're not logged in as guest when
you try to make the connection so this error means you are connecting as a
Windows user who doesn't have permissions or can't be authenticated to the
local Windows machine. Get Windows security working and I think it will
work.
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
"Ilya" <Ilya@.discussions.microsoft.com> wrote in message
news:6CAFF2A5-3273-4E28-AFEB-07060DFFE503@.microsoft.com...
>I am connecting remotely to SQL Express using my VB application. Here is
>the
> connection string that I use.
> cn.ConnectionString = "Provider=SQLNCLI;Network
> Library=DBMSSOCN;Integrated
> Security=SSPI;"Server=192.168.10.243\SQLEXPRESS,1433;" & _
> "database=CopyRequest"
> I get "Login failed for user 'ILYA-TEST-PC\Guest'" error when I try to
> connect. What is the cause of this error? I allow remote connections on
> SQL
> Server.
can't conect remotely to SQL Express
connection string that I use.
cn.ConnectionString = "Provider=SQLNCLI;Network Library=DBMSSOCN;Integrated
Security=SSPI;"Server=192.168.10.243\SQLEXPRESS,14 33;" & _
"database=CopyRequest"
I get "Login failed for user 'ILYA-TEST-PC\Guest'" error when I try to
connect. What is the cause of this error? I allow remote connections on SQL
Server.
Hi
Have you checked the permissions for 'ILYA-TEST-PC\Guest' ?
John
"Ilya" wrote:
> I am connecting remotely to SQL Express using my VB application. Here is the
> connection string that I use.
> cn.ConnectionString = "Provider=SQLNCLI;Network Library=DBMSSOCN;Integrated
> Security=SSPI;"Server=192.168.10.243\SQLEXPRESS,14 33;" & _
> "database=CopyRequest"
> I get "Login failed for user 'ILYA-TEST-PC\Guest'" error when I try to
> connect. What is the cause of this error? I allow remote connections on SQL
> Server.
|||Guest is disabled by default. I assume you're not logged in as guest when
you try to make the connection so this error means you are connecting as a
Windows user who doesn't have permissions or can't be authenticated to the
local Windows machine. Get Windows security working and I think it will
work.
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
"Ilya" <Ilya@.discussions.microsoft.com> wrote in message
news:6CAFF2A5-3273-4E28-AFEB-07060DFFE503@.microsoft.com...
>I am connecting remotely to SQL Express using my VB application. Here is
>the
> connection string that I use.
> cn.ConnectionString = "Provider=SQLNCLI;Network
> Library=DBMSSOCN;Integrated
> Security=SSPI;"Server=192.168.10.243\SQLEXPRESS,14 33;" & _
> "database=CopyRequest"
> I get "Login failed for user 'ILYA-TEST-PC\Guest'" error when I try to
> connect. What is the cause of this error? I allow remote connections on
> SQL
> Server.
can't conect remotely to SQL Express
connection string that I use.
cn.ConnectionString = "Provider=SQLNCLI;Network Library=DBMSSOCN;Integrated
Security=SSPI;"Server=192.168.10.243\SQLEXPRESS,1433;" & _
"database=CopyRequest"
I get "Login failed for user 'ILYA-TEST-PC\Guest'" error when I try to
connect. What is the cause of this error? I allow remote connections on SQL
Server.Hi
Have you checked the permissions for 'ILYA-TEST-PC\Guest' ?
John
"Ilya" wrote:
> I am connecting remotely to SQL Express using my VB application. Here is the
> connection string that I use.
> cn.ConnectionString = "Provider=SQLNCLI;Network Library=DBMSSOCN;Integrated
> Security=SSPI;"Server=192.168.10.243\SQLEXPRESS,1433;" & _
> "database=CopyRequest"
> I get "Login failed for user 'ILYA-TEST-PC\Guest'" error when I try to
> connect. What is the cause of this error? I allow remote connections on SQL
> Server.|||Guest is disabled by default. I assume you're not logged in as guest when
you try to make the connection so this error means you are connecting as a
Windows user who doesn't have permissions or can't be authenticated to the
local Windows machine. Get Windows security working and I think it will
work.
--
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
"Ilya" <Ilya@.discussions.microsoft.com> wrote in message
news:6CAFF2A5-3273-4E28-AFEB-07060DFFE503@.microsoft.com...
>I am connecting remotely to SQL Express using my VB application. Here is
>the
> connection string that I use.
> cn.ConnectionString = "Provider=SQLNCLI;Network
> Library=DBMSSOCN;Integrated
> Security=SSPI;"Server=192.168.10.243\SQLEXPRESS,1433;" & _
> "database=CopyRequest"
> I get "Login failed for user 'ILYA-TEST-PC\Guest'" error when I try to
> connect. What is the cause of this error? I allow remote connections on
> SQL
> Server.
Tuesday, March 27, 2012
Can't change the name of a OLE DB Source component name
Hi,
I've created an application that create package with a dataflow. The package with the dataflow and the ole db Source was created succesfully but for some reason the name of the Ole DB Source dosen't change programmitcally It's stays with the default name "OLE DB Source". This is very problematic because I want to add another Ole Db source and the package won't load because there will be two components with the same name.
Thanks.
This is the Code, It's from msdn exmples:
Imports Microsoft.SqlServer.Dts.Runtime
Imports Microsoft.SqlServer.Dts.Runtime.Wrapper
Imports Microsoft.SqlServer.Dts.Pipeline
Imports Microsoft.SqlServer.Dts.Pipeline.Wrapper
Module Module1
Sub Main()
Dim package As Microsoft.SqlServer.Dts.Runtime.Package = _
New Microsoft.SqlServer.Dts.Runtime.Package()
Dim e As Executable = package.Executables.Add("DTS.Pipeline.1")
Dim thMainPipe As Microsoft.SqlServer.Dts.Runtime.TaskHost = _
CType(e, Microsoft.SqlServer.Dts.Runtime.TaskHost)
Dim dataFlowTask As MainPipe = CType(thMainPipe.InnerObject, MainPipe)
' Add an OLEDB connection manager to the package.
Dim cm As ConnectionManager = package.Connections.Add("OLEDB")
cm.Name = "OLEDB ConnectionManager"
cm.ConnectionString = "Data Source=(local);" & _
"Initial Catalog=AdventureWorks;Provider=SQLOLEDB.1;" & _
"Integrated Security=SSPI;"
' Add an OLE DB source to the data flow.
Dim component As IDTSComponentMetaData90 = _
dataFlowTask.ComponentMetaDataCollection.New()
component.Name = "AdventureWorks;Product"
component.ComponentClassID = "DTSAdapter.OleDbSource.1"
' You can also use the CLSID of the component instead of the PROGID.
'component.ComponentClassID = "{2C0A8BE5-1EDC-4353-A0EF-B778599C65A0}";
' Get the design time instance of the component.
Dim instance As CManagedComponentWrapper = component.Instantiate()
' Initialize the component.
instance.ProvideComponentProperties()
' Specify the connection manager.
If component.RuntimeConnectionCollection.Count > 0 Then
component.RuntimeConnectionCollection(0).ConnectionManager = _
DtsConvert.ToConnectionManager90(package.Connections(0))
End If
' Set the custom properties.
instance.SetComponentProperty("AccessMode", 2)
instance.SetComponentProperty("SqlCommand", _
"Select * from Production.Product")
' Reinitialize the metadata.
instance.AcquireConnections(vbNull)
instance.ReinitializeMetaData()
instance.ReleaseConnections()
' Add other components to the data flow and connect them.
End Sub
End Module
If I remember correctly, the Name should be set after the call to
instance.ProvideComponentProperties();
|||Thanks It worksThursday, March 22, 2012
Can't Add a linked table to SQL Server 2005 with Access 2003
Hi,
I have an Access 2003 front end that contains a number of linked tables on SQL Server 2005 SE. I recreated the application on a second network for testing and was able to use the Linked Table Manager to refresh the database connections. The problem is when I try and add another linked table. I select Link Tables from the menu and then when I select 'ODBC Databases()' from the 'Files of Type' list box, the Link window closes right away.
Any suggestions?
I would post to MS Access newsgroups to get help on this, sounds like a problem with Microsoft Access ->
http://www.microsoft.com/office/community/en-us/default.mspx
My only feeble guess for you is that somehow ODBC is not installed correctly on the computer, try re-installing latest MDAC.
|||if you are running Norton AV , turn off the Office Plug in, Anti-virus/Options/Misc|||You can't modify tables in access 2003 against SQL 2005. I use access 2007 beta with good results.|||I was having the same problem as bonkers1963 and I found this posting. I have Norton AV and the Office Plugin option was set on. I turned off the Office Plugin option and restared Access then I could link tables with no problem.
Thanks for the info.
Can't Add a linked table to SQL Server 2005 with Access 2003
Hi,
I have an Access 2003 front end that contains a number of linked tables on SQL Server 2005 SE. I recreated the application on a second network for testing and was able to use the Linked Table Manager to refresh the database connections. The problem is when I try and add another linked table. I select Link Tables from the menu and then when I select 'ODBC Databases()' from the 'Files of Type' list box, the Link window closes right away.
Any suggestions?
I would post to MS Access newsgroups to get help on this, sounds like a problem with Microsoft Access ->
http://www.microsoft.com/office/community/en-us/default.mspx
My only feeble guess for you is that somehow ODBC is not installed correctly on the computer, try re-installing latest MDAC.
|||if you are running Norton AV , turn off the Office Plug in, Anti-virus/Options/Misc|||You can't modify tables in access 2003 against SQL 2005. I use access 2007 beta with good results.|||I was having the same problem as bonkers1963 and I found this posting. I have Norton AV and the Office Plugin option was set on. I turned off the Office Plugin option and restared Access then I could link tables with no problem.
Thanks for the info.
sqlThursday, March 8, 2012
Cannot update. Database or object are read-only
I've created Data Source File "test.dsn" and tested succesfully.
SQL Server database in on the other machine.
This is a code that I am using.
And error message I am geting is "Cannot update. Database or object are read-only".
Dim cn As ADODB.Connection
Dim strSQL As String
Set cn = New ADODB.Connection
cn.Open "Provider=Microsoft.Jet.OLEDB.4.0;" & _
"Data Source=C:\Documents and Settings\pd\Desktop\Development\test.xls;" & _
"Extended Properties=Excel 8.0"
strSQL = "INSERT INTO [DSN = test.dsn].Region Values(5, 'ab');"
cn.Execute strSQL
cn.Close
Set cn = Nothing
Read-only of databse properties is not selected.If I get it right you're attempting to insert a row into excel. As long as I know it's not possible because you cannot update, insert records throught Jet provider. mojza|||Your query is unclear . Understanding you are trying to update region table In sql database .
if that's case you should then rather open an ODBC or OLE DB connection to SQL server
cn.Provider = "sqloledb"
cn.Properties("Data Source") = ServerName
cn.Properties("Initial Catalog") = DatabaseName
' If Windows NT authentication.
cn.Properties("Integrated Security")= "SSPI"
'If SQL Authentication
cn.Properties("User ID")= UserID
cn.Properties("Password") = pwd
' Open the database.
cn.Open
Dim strSQL as string
strSQL "INSERT INTO dbo.Region Values(5, 'ab')"
cn.execute strSQL
cn.close
set cn = nothing
Wednesday, March 7, 2012
Cannot start your application. The workgroup information file is missing or opened exclusively b
when i browse my web application the eror as below display..
what should i do..
any suggestion or tips...
"Cannot start your application. The workgroup information file is missing or opened exclusively by another user.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.Exception Details: System.Data.OleDb.OleDbException: Cannot start your application. The workgroup information file is missing or opened exclusively by another user. "
thanks in advance..
thank you very much..
That is not a SQL Server problem as you aure using obviously MS Access, you better post your question to one of the Access forums in the public newgroup network. But, as far as I can remember from my old Access days, you will have to delete the lock file which is located in the same folder as the workgroup file which contains the security informa′tion.
Jens K. Suessmeyer
http://www.sqlserver2005.de
Tuesday, February 14, 2012
Cannot save English dates!
Hi All,
I have this dumb problem with dates in my mobile application. The problem is when saving a short date in English format ex 20/08/2006 the sql server 200 windows CE Edition display an error stating
THERE IS AN ERROR IN THE DATEPART FORMAT. [,,,Expression,,]
When changing the date in American format the problem is solved ex 08/20/2006
The problem is that I require the dates in English Format only!
Is there anyway of solving my problem ?
Thanks
Matt
Please use parameters to avoid formatting issues. If you don’t know how, please look up SqlCeParameter class on MSDN and/or search this forum.
Note: SQL CE 2.0 only supports unnamed parameters, SQL Mobile supports both named and unnamed parameters.
Friday, February 10, 2012
Cannot resolve a package path
I have a parent package - Main.dtsx that calls a number of child packages. I also use configuration packages as I must deploy the application across multiple environments.
Main.dtsx contains a single Ccnfiguration file - Child_Packages.dtsConfig. This contains the connection strings for all the child packages.
Each child package contains a single configuration file - Main.dtsConfig that contains a superset of OLE DB connections. That is no single child package uses all of the connections contained in main.dtsConfig.
Each child package will execute independently without error. However, when called from Main.dtsx, I get the following errors:
Error: 2007-08-15 15:44:22.93
Code: 0xC001000E
Source: UserSecurity
Description: The connection "CRM" is not found. This error is thrown by Connections collection when the specific connection element is not found.
End Error
Warning: 2007-08-15 15:44:22.93
Code: 0x8001F02F
Source: UserSecurity
Description: Cannot resolve a package path to an object in the package ".Connections[CRM].Properties[ConnectionString]". Verify that the package path is valid.
End Warning
Warning: 2007-08-15 15:44:22.94
Code: 0x80012017
Source: UserSecurity
Description: The package path referenced an object that cannot be found: "\Package.Connections[CRM].Properties[ConnectionString]". This occurs when an attempt is made to resolve a package path to an object that cannot be found.
End Warning
I have seen discussions that suggest that these errors occur where the connection in the config file is not found in the child package. Is there any way of suppressing this ?
Are there any simpler methods that allow me to change connections in each environment?
I suspect I will end up having to tailor config files for each child package, but I live in hope.
Michael M.
Duh! The main cause of this error is the fact that the child packages do not contain all of the connections that are in Main.dtsConfig.
But it is a pain to have to add connections that you don't use to each package.
And it is pain that you can't use the Deployment utility because it crashes attempting to copy the same config files over.
|||You can use individual configuration files if you want; that way each package uses only the config files that really requires. BTW, I think, a package does not fail because the configuration file has an entry that is not used by that package; rather you see a warning.
|||Regarding: BTW, I think, a package does not fail...
What caused this error?
Code Snippet
Error: 2007-08-15 15:44:22.93
Code: 0xC001000E
Source: UserSecurity
Description: The connection "CRM" is not found. This error is thrown by Connections collection when the specific connection element is not found.
End Error
As to writing individual config files, this is creates unneccessary work, IMHO. Other ETL packages can use a single config file.
The best solution would be to build a tool that updates the .dtsx files in each environment and then we don't need config files at all.
Cannot resolve a package path
I have a parent package - Main.dtsx that calls a number of child packages. I also use configuration packages as I must deploy the application across multiple environments.
Main.dtsx contains a single Ccnfiguration file - Child_Packages.dtsConfig. This contains the connection strings for all the child packages.
Each child package contains a single configuration file - Main.dtsConfig that contains a superset of OLE DB connections. That is no single child package uses all of the connections contained in main.dtsConfig.
Each child package will execute independently without error. However, when called from Main.dtsx, I get the following errors:
Error: 2007-08-15 15:44:22.93
Code: 0xC001000E
Source: UserSecurity
Description: The connection "CRM" is not found. This error is thrown by Connections collection when the specific connection element is not found.
End Error
Warning: 2007-08-15 15:44:22.93
Code: 0x8001F02F
Source: UserSecurity
Description: Cannot resolve a package path to an object in the package ".Connections[CRM].Properties[ConnectionString]". Verify that the package path is valid.
End Warning
Warning: 2007-08-15 15:44:22.94
Code: 0x80012017
Source: UserSecurity
Description: The package path referenced an object that cannot be found: "\Package.Connections[CRM].Properties[ConnectionString]". This occurs when an attempt is made to resolve a package path to an object that cannot be found.
End Warning
I have seen discussions that suggest that these errors occur where the connection in the config file is not found in the child package. Is there any way of suppressing this ?
Are there any simpler methods that allow me to change connections in each environment?
I suspect I will end up having to tailor config files for each child package, but I live in hope.
Michael M.
Duh! The main cause of this error is the fact that the child packages do not contain all of the connections that are in Main.dtsConfig.
But it is a pain to have to add connections that you don't use to each package.
And it is pain that you can't use the Deployment utility because it crashes attempting to copy the same config files over.
|||You can use individual configuration files if you want; that way each package uses only the config files that really requires. BTW, I think, a package does not fail because the configuration file has an entry that is not used by that package; rather you see a warning.
|||Regarding: BTW, I think, a package does not fail...
What caused this error?
Code Snippet
Error: 2007-08-15 15:44:22.93
Code: 0xC001000E
Source: UserSecurity
Description: The connection "CRM" is not found. This error is thrown by Connections collection when the specific connection element is not found.
End Error
As to writing individual config files, this is creates unneccessary work, IMHO. Other ETL packages can use a single config file.
The best solution would be to build a tool that updates the .dtsx files in each environment and then we don't need config files at all.