Hi,
Our users that connect to a MSSQL db via MS-Access cannot access more than
10 000 records. In other words, all the records that have been inserted afte
r
the 10 000th record cannot be access nor from the table, nor from a query.
Is there any way to overcome the problem?
ThanksHere's a not so awesome way:
Create all your tables without data. When they need data you create a
connection in code and snapshot the data out of SQL into your Access
tables.
Frankly, that just sux. I've not heard of a 10,000 record limit in Access.
Can you point me to an MSDN are similar article that talks about this. I
would be interested in looking into this a little more.
> Our users that connect to a MSSQL db via MS-Access cannot access more than
> 10 000 records. In other words, all the records that have been inserted
> after the 10 000th record cannot be access nor from the table, nor from a
> query.|||We have users using linked tables in Access to connect to SQL Server and
there is no such limit.
Ben Nevarez
"DexterV" <DexterV@.discussions.microsoft.com> wrote in message
news:CA155716-7F98-4D64-9318-EF816ADA42BB@.microsoft.com...
> Hi,
> Our users that connect to a MSSQL db via MS-Access cannot access more than
> 10 000 records. In other words, all the records that have been inserted
> after
> the 10 000th record cannot be access nor from the table, nor from a query.
> Is there any way to overcome the problem?
> Thanks|||Dexter,
This is an option in the ms-access settings, probably to avoid long lists
being sent accross the network,
to augment the limit: I'll try to guide you (my ms-access version is in dutc
h)
go to the ms-access menu tools / options, the option dialog box opens.
There is a tab called edit/find and in there is there is text box with the
limit number like 10000
Hope this helps
--
Jan D''Hondt
<Toto, I''ve got a feeling we''re not in Kansas anymore.>
SQL database and .NET solutions
"DexterV" wrote:
> Hi,
> Our users that connect to a MSSQL db via MS-Access cannot access more than
> 10 000 records. In other words, all the records that have been inserted af
ter
> the 10 000th record cannot be access nor from the table, nor from a query.
> Is there any way to overcome the problem?
> Thanks|||Thanks Jan,
Actually, I found the max. record limit parameter on the advanced tab.
I should have explored Ms-access options first.
"Jan D''Hondt" wrote:
[vbcol=seagreen]
> Dexter,
> This is an option in the ms-access settings, probably to avoid long lists
> being sent accross the network,
> to augment the limit: I'll try to guide you (my ms-access version is in du
tch)
> go to the ms-access menu tools / options, the option dialog box opens.
> There is a tab called edit/find and in there is there is text box with the
> limit number like 10000
> Hope this helps
> --
> Jan D''Hondt
> <Toto, I''ve got a feeling we''re not in Kansas anymore.>
> SQL database and .NET solutions
>
> "DexterV" wrote:
>
Showing posts with label connect. Show all posts
Showing posts with label connect. Show all posts
Monday, March 26, 2012
remove 10 000 records limit
Hi,
Our users that connect to a MSSQL db via MS-Access cannot access more than
10 000 records. In other words, all the records that have been inserted after
the 10 000th record cannot be access nor from the table, nor from a query.
Is there any way to overcome the problem?
ThanksHere's a not so awesome way:
Create all your tables without data. When they need data you create a
connection in code and snapshot the data out of SQL into your Access
tables.
Frankly, that just sux. I've not heard of a 10,000 record limit in Access.
Can you point me to an MSDN are similar article that talks about this. I
would be interested in looking into this a little more.
> Our users that connect to a MSSQL db via MS-Access cannot access more than
> 10 000 records. In other words, all the records that have been inserted
> after the 10 000th record cannot be access nor from the table, nor from a
> query.|||We have users using linked tables in Access to connect to SQL Server and
there is no such limit.
Ben Nevarez
"DexterV" <DexterV@.discussions.microsoft.com> wrote in message
news:CA155716-7F98-4D64-9318-EF816ADA42BB@.microsoft.com...
> Hi,
> Our users that connect to a MSSQL db via MS-Access cannot access more than
> 10 000 records. In other words, all the records that have been inserted
> after
> the 10 000th record cannot be access nor from the table, nor from a query.
> Is there any way to overcome the problem?
> Thanks|||Dexter,
This is an option in the ms-access settings, probably to avoid long lists
being sent accross the network,
to augment the limit: I'll try to guide you (my ms-access version is in dutch)
go to the ms-access menu tools / options, the option dialog box opens.
There is a tab called edit/find and in there is there is text box with the
limit number like 10000
Hope this helps
--
Jan D''Hondt
<Toto, I''ve got a feeling we''re not in Kansas anymore.>
SQL database and .NET solutions
"DexterV" wrote:
> Hi,
> Our users that connect to a MSSQL db via MS-Access cannot access more than
> 10 000 records. In other words, all the records that have been inserted after
> the 10 000th record cannot be access nor from the table, nor from a query.
> Is there any way to overcome the problem?
> Thanks|||Thanks Jan,
Actually, I found the max. record limit parameter on the advanced tab.
I should have explored Ms-access options first.
"Jan D''Hondt" wrote:
> Dexter,
> This is an option in the ms-access settings, probably to avoid long lists
> being sent accross the network,
> to augment the limit: I'll try to guide you (my ms-access version is in dutch)
> go to the ms-access menu tools / options, the option dialog box opens.
> There is a tab called edit/find and in there is there is text box with the
> limit number like 10000
> Hope this helps
> --
> Jan D''Hondt
> <Toto, I''ve got a feeling we''re not in Kansas anymore.>
> SQL database and .NET solutions
>
> "DexterV" wrote:
> > Hi,
> >
> > Our users that connect to a MSSQL db via MS-Access cannot access more than
> > 10 000 records. In other words, all the records that have been inserted after
> > the 10 000th record cannot be access nor from the table, nor from a query.
> >
> > Is there any way to overcome the problem?
> >
> > Thanks
Our users that connect to a MSSQL db via MS-Access cannot access more than
10 000 records. In other words, all the records that have been inserted after
the 10 000th record cannot be access nor from the table, nor from a query.
Is there any way to overcome the problem?
ThanksHere's a not so awesome way:
Create all your tables without data. When they need data you create a
connection in code and snapshot the data out of SQL into your Access
tables.
Frankly, that just sux. I've not heard of a 10,000 record limit in Access.
Can you point me to an MSDN are similar article that talks about this. I
would be interested in looking into this a little more.
> Our users that connect to a MSSQL db via MS-Access cannot access more than
> 10 000 records. In other words, all the records that have been inserted
> after the 10 000th record cannot be access nor from the table, nor from a
> query.|||We have users using linked tables in Access to connect to SQL Server and
there is no such limit.
Ben Nevarez
"DexterV" <DexterV@.discussions.microsoft.com> wrote in message
news:CA155716-7F98-4D64-9318-EF816ADA42BB@.microsoft.com...
> Hi,
> Our users that connect to a MSSQL db via MS-Access cannot access more than
> 10 000 records. In other words, all the records that have been inserted
> after
> the 10 000th record cannot be access nor from the table, nor from a query.
> Is there any way to overcome the problem?
> Thanks|||Dexter,
This is an option in the ms-access settings, probably to avoid long lists
being sent accross the network,
to augment the limit: I'll try to guide you (my ms-access version is in dutch)
go to the ms-access menu tools / options, the option dialog box opens.
There is a tab called edit/find and in there is there is text box with the
limit number like 10000
Hope this helps
--
Jan D''Hondt
<Toto, I''ve got a feeling we''re not in Kansas anymore.>
SQL database and .NET solutions
"DexterV" wrote:
> Hi,
> Our users that connect to a MSSQL db via MS-Access cannot access more than
> 10 000 records. In other words, all the records that have been inserted after
> the 10 000th record cannot be access nor from the table, nor from a query.
> Is there any way to overcome the problem?
> Thanks|||Thanks Jan,
Actually, I found the max. record limit parameter on the advanced tab.
I should have explored Ms-access options first.
"Jan D''Hondt" wrote:
> Dexter,
> This is an option in the ms-access settings, probably to avoid long lists
> being sent accross the network,
> to augment the limit: I'll try to guide you (my ms-access version is in dutch)
> go to the ms-access menu tools / options, the option dialog box opens.
> There is a tab called edit/find and in there is there is text box with the
> limit number like 10000
> Hope this helps
> --
> Jan D''Hondt
> <Toto, I''ve got a feeling we''re not in Kansas anymore.>
> SQL database and .NET solutions
>
> "DexterV" wrote:
> > Hi,
> >
> > Our users that connect to a MSSQL db via MS-Access cannot access more than
> > 10 000 records. In other words, all the records that have been inserted after
> > the 10 000th record cannot be access nor from the table, nor from a query.
> >
> > Is there any way to overcome the problem?
> >
> > Thanks
remove 10 000 records limit
Hi,
Our users that connect to a MSSQL db via MS-Access cannot access more than
10 000 records. In other words, all the records that have been inserted after
the 10 000th record cannot be access nor from the table, nor from a query.
Is there any way to overcome the problem?
Thanks
Here's a not so awesome way:
Create all your tables without data. When they need data you create a
connection in code and snapshot the data out of SQL into your Access
tables.
Frankly, that just sux. I've not heard of a 10,000 record limit in Access.
Can you point me to an MSDN are similar article that talks about this. I
would be interested in looking into this a little more.
> Our users that connect to a MSSQL db via MS-Access cannot access more than
> 10 000 records. In other words, all the records that have been inserted
> after the 10 000th record cannot be access nor from the table, nor from a
> query.
|||We have users using linked tables in Access to connect to SQL Server and
there is no such limit.
Ben Nevarez
"DexterV" <DexterV@.discussions.microsoft.com> wrote in message
news:CA155716-7F98-4D64-9318-EF816ADA42BB@.microsoft.com...
> Hi,
> Our users that connect to a MSSQL db via MS-Access cannot access more than
> 10 000 records. In other words, all the records that have been inserted
> after
> the 10 000th record cannot be access nor from the table, nor from a query.
> Is there any way to overcome the problem?
> Thanks
|||Dexter,
This is an option in the ms-access settings, probably to avoid long lists
being sent accross the network,
to augment the limit: I'll try to guide you (my ms-access version is in dutch)
go to the ms-access menu tools / options, the option dialog box opens.
There is a tab called edit/find and in there is there is text box with the
limit number like 10000
Hope this helps
Jan D''Hondt
<Toto, I''ve got a feeling we''re not in Kansas anymore.>
SQL database and .NET solutions
"DexterV" wrote:
> Hi,
> Our users that connect to a MSSQL db via MS-Access cannot access more than
> 10 000 records. In other words, all the records that have been inserted after
> the 10 000th record cannot be access nor from the table, nor from a query.
> Is there any way to overcome the problem?
> Thanks
|||Thanks Jan,
Actually, I found the max. record limit parameter on the advanced tab.
I should have explored Ms-access options first.
"Jan D''Hondt" wrote:
[vbcol=seagreen]
> Dexter,
> This is an option in the ms-access settings, probably to avoid long lists
> being sent accross the network,
> to augment the limit: I'll try to guide you (my ms-access version is in dutch)
> go to the ms-access menu tools / options, the option dialog box opens.
> There is a tab called edit/find and in there is there is text box with the
> limit number like 10000
> Hope this helps
> --
> Jan D''Hondt
> <Toto, I''ve got a feeling we''re not in Kansas anymore.>
> SQL database and .NET solutions
>
> "DexterV" wrote:
Our users that connect to a MSSQL db via MS-Access cannot access more than
10 000 records. In other words, all the records that have been inserted after
the 10 000th record cannot be access nor from the table, nor from a query.
Is there any way to overcome the problem?
Thanks
Here's a not so awesome way:
Create all your tables without data. When they need data you create a
connection in code and snapshot the data out of SQL into your Access
tables.
Frankly, that just sux. I've not heard of a 10,000 record limit in Access.
Can you point me to an MSDN are similar article that talks about this. I
would be interested in looking into this a little more.
> Our users that connect to a MSSQL db via MS-Access cannot access more than
> 10 000 records. In other words, all the records that have been inserted
> after the 10 000th record cannot be access nor from the table, nor from a
> query.
|||We have users using linked tables in Access to connect to SQL Server and
there is no such limit.
Ben Nevarez
"DexterV" <DexterV@.discussions.microsoft.com> wrote in message
news:CA155716-7F98-4D64-9318-EF816ADA42BB@.microsoft.com...
> Hi,
> Our users that connect to a MSSQL db via MS-Access cannot access more than
> 10 000 records. In other words, all the records that have been inserted
> after
> the 10 000th record cannot be access nor from the table, nor from a query.
> Is there any way to overcome the problem?
> Thanks
|||Dexter,
This is an option in the ms-access settings, probably to avoid long lists
being sent accross the network,
to augment the limit: I'll try to guide you (my ms-access version is in dutch)
go to the ms-access menu tools / options, the option dialog box opens.
There is a tab called edit/find and in there is there is text box with the
limit number like 10000
Hope this helps
Jan D''Hondt
<Toto, I''ve got a feeling we''re not in Kansas anymore.>
SQL database and .NET solutions
"DexterV" wrote:
> Hi,
> Our users that connect to a MSSQL db via MS-Access cannot access more than
> 10 000 records. In other words, all the records that have been inserted after
> the 10 000th record cannot be access nor from the table, nor from a query.
> Is there any way to overcome the problem?
> Thanks
|||Thanks Jan,
Actually, I found the max. record limit parameter on the advanced tab.
I should have explored Ms-access options first.
"Jan D''Hondt" wrote:
[vbcol=seagreen]
> Dexter,
> This is an option in the ms-access settings, probably to avoid long lists
> being sent accross the network,
> to augment the limit: I'll try to guide you (my ms-access version is in dutch)
> go to the ms-access menu tools / options, the option dialog box opens.
> There is a tab called edit/find and in there is there is text box with the
> limit number like 10000
> Hope this helps
> --
> Jan D''Hondt
> <Toto, I''ve got a feeling we''re not in Kansas anymore.>
> SQL database and .NET solutions
>
> "DexterV" wrote:
Friday, March 23, 2012
Remotely connecting sql Server
Hi,
I'm Connecting to server on the internet. When I connect with the SQL Query analyzer it works fine.
but when I open the Enterprise Manager & Click on the database then It loads all the databases from the server. & it takes a lot of time. What I want that to load only specific databases or any other method by which I can improve its performance.
I hope you get that.
thanks in advance,
Das
I don't think you can change that behavior, but you can certainly increase
the timeout value for Enterprise Manager. For more informaiton, see:
http://vyaskn.tripod.com/sql_server_tools_faq.htm#q7
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"Das" <anonymous@.discussions.microsoft.com> wrote in message
news:A50CF25F-A767-4BA9-BE5E-5E046346F362@.microsoft.com...
Hi,
I'm Connecting to server on the internet. When I connect with the SQL Query
analyzer it works fine.
but when I open the Enterprise Manager & Click on the database then It
loads all the databases from the server. & it takes a lot of time. What I
want that to load only specific databases or any other method by which I can
improve its performance.
I hope you get that.
thanks in advance,
Das
I'm Connecting to server on the internet. When I connect with the SQL Query analyzer it works fine.
but when I open the Enterprise Manager & Click on the database then It loads all the databases from the server. & it takes a lot of time. What I want that to load only specific databases or any other method by which I can improve its performance.
I hope you get that.
thanks in advance,
Das
I don't think you can change that behavior, but you can certainly increase
the timeout value for Enterprise Manager. For more informaiton, see:
http://vyaskn.tripod.com/sql_server_tools_faq.htm#q7
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"Das" <anonymous@.discussions.microsoft.com> wrote in message
news:A50CF25F-A767-4BA9-BE5E-5E046346F362@.microsoft.com...
Hi,
I'm Connecting to server on the internet. When I connect with the SQL Query
analyzer it works fine.
but when I open the Enterprise Manager & Click on the database then It
loads all the databases from the server. & it takes a lot of time. What I
want that to load only specific databases or any other method by which I can
improve its performance.
I hope you get that.
thanks in advance,
Das
Remotely Connect to Sql Server
Hi
i am trying to registering the remote sql server (MMC Sql EnterPrise
Manager) which is outside our Network . i.e the machine is located at ISP.
it is giving me error SQL server does not exist or access denied.
i am specifying the IP address of remote machine to whom i want to access
remotely,
(SQL Server Properties ) under connection tab - (configuration done to
remote sql server)
i had selected the option of allowing other sql server to connect remotely
to this sql server using RPC
even i am not able register remote sql server in my local sql server.
Can anyone help me out what exactly we have to do for remote access of sql
server.
Thanks
MiteshCan you ping the SQL server?
Can you telnet to port 1433 from your side ?
Is there a firewall in between ?
Make sure you can connect on port 1433 otherwise it will not work , you
would then need to check whats blocking that port somewhere!
HTH
Dylan
"Mitesh Patel" <mitesh@.viraat.com> wrote in message
news:OJExAfU0EHA.1408@.TK2MSFTNGP10.phx.gbl...
> Hi
> i am trying to registering the remote sql server (MMC Sql EnterPrise
> Manager) which is outside our Network . i.e the machine is located at ISP.
> it is giving me error SQL server does not exist or access denied.
> i am specifying the IP address of remote machine to whom i want to access
> remotely,
> (SQL Server Properties ) under connection tab - (configuration done to
> remote sql server)
> i had selected the option of allowing other sql server to connect remotely
> to this sql server using RPC
> even i am not able register remote sql server in my local sql server.
> Can anyone help me out what exactly we have to do for remote access of sql
> server.
> Thanks
> Mitesh
>
>|||when i ping to ip address it is showing destination host unreachable (this
is due to internet provider had stopped ping )
yes i am able to do telnet to port 1433 after passing the telnet command at
port 1433. the telnet window shows connecting... and then telnet screen
becomes blank (might it been connected and waiting for commands )
remote server is located in data center then firewall will be there
............
Thanks
Mitesh
"Dylan Kruger" <carmellobear1@.hotmail.com> wrote in message
news:uaq5Y8U0EHA.1396@.tk2msftngp13.phx.gbl...
> Can you ping the SQL server?
> Can you telnet to port 1433 from your side ?
> Is there a firewall in between ?
> Make sure you can connect on port 1433 otherwise it will not work , you
> would then need to check whats blocking that port somewhere!
> HTH
> Dylan
>
> "Mitesh Patel" <mitesh@.viraat.com> wrote in message
> news:OJExAfU0EHA.1408@.TK2MSFTNGP10.phx.gbl...
ISP.[vbcol=seagreen]
access[vbcol=seagreen]
remotely[vbcol=seagreen]
sql[vbcol=seagreen]
>|||You should also make sure that it's the public IP you try to access or you
have the proper NAT settings in the Firewall in both ends. It could also be
the settings for your VPN connection (if that's what your using ) that needs
to be checked.
Regards
Steen
Dylan Kruger wrote:[vbcol=seagreen]
> Can you ping the SQL server?
> Can you telnet to port 1433 from your side ?
> Is there a firewall in between ?
> Make sure you can connect on port 1433 otherwise it will not work ,
> you would then need to check whats blocking that port somewhere!
> HTH
> Dylan
>
> "Mitesh Patel" <mitesh@.viraat.com> wrote in message
> news:OJExAfU0EHA.1408@.TK2MSFTNGP10.phx.gbl...sql
i am trying to registering the remote sql server (MMC Sql EnterPrise
Manager) which is outside our Network . i.e the machine is located at ISP.
it is giving me error SQL server does not exist or access denied.
i am specifying the IP address of remote machine to whom i want to access
remotely,
(SQL Server Properties ) under connection tab - (configuration done to
remote sql server)
i had selected the option of allowing other sql server to connect remotely
to this sql server using RPC
even i am not able register remote sql server in my local sql server.
Can anyone help me out what exactly we have to do for remote access of sql
server.
Thanks
MiteshCan you ping the SQL server?
Can you telnet to port 1433 from your side ?
Is there a firewall in between ?
Make sure you can connect on port 1433 otherwise it will not work , you
would then need to check whats blocking that port somewhere!
HTH
Dylan
"Mitesh Patel" <mitesh@.viraat.com> wrote in message
news:OJExAfU0EHA.1408@.TK2MSFTNGP10.phx.gbl...
> Hi
> i am trying to registering the remote sql server (MMC Sql EnterPrise
> Manager) which is outside our Network . i.e the machine is located at ISP.
> it is giving me error SQL server does not exist or access denied.
> i am specifying the IP address of remote machine to whom i want to access
> remotely,
> (SQL Server Properties ) under connection tab - (configuration done to
> remote sql server)
> i had selected the option of allowing other sql server to connect remotely
> to this sql server using RPC
> even i am not able register remote sql server in my local sql server.
> Can anyone help me out what exactly we have to do for remote access of sql
> server.
> Thanks
> Mitesh
>
>|||when i ping to ip address it is showing destination host unreachable (this
is due to internet provider had stopped ping )
yes i am able to do telnet to port 1433 after passing the telnet command at
port 1433. the telnet window shows connecting... and then telnet screen
becomes blank (might it been connected and waiting for commands )
remote server is located in data center then firewall will be there
............
Thanks
Mitesh
"Dylan Kruger" <carmellobear1@.hotmail.com> wrote in message
news:uaq5Y8U0EHA.1396@.tk2msftngp13.phx.gbl...
> Can you ping the SQL server?
> Can you telnet to port 1433 from your side ?
> Is there a firewall in between ?
> Make sure you can connect on port 1433 otherwise it will not work , you
> would then need to check whats blocking that port somewhere!
> HTH
> Dylan
>
> "Mitesh Patel" <mitesh@.viraat.com> wrote in message
> news:OJExAfU0EHA.1408@.TK2MSFTNGP10.phx.gbl...
ISP.[vbcol=seagreen]
access[vbcol=seagreen]
remotely[vbcol=seagreen]
sql[vbcol=seagreen]
>|||You should also make sure that it's the public IP you try to access or you
have the proper NAT settings in the Firewall in both ends. It could also be
the settings for your VPN connection (if that's what your using ) that needs
to be checked.
Regards
Steen
Dylan Kruger wrote:[vbcol=seagreen]
> Can you ping the SQL server?
> Can you telnet to port 1433 from your side ?
> Is there a firewall in between ?
> Make sure you can connect on port 1433 otherwise it will not work ,
> you would then need to check whats blocking that port somewhere!
> HTH
> Dylan
>
> "Mitesh Patel" <mitesh@.viraat.com> wrote in message
> news:OJExAfU0EHA.1408@.TK2MSFTNGP10.phx.gbl...sql
Remotely Connect to Sql Server
Hi
i am trying to registering the remote sql server (MMC Sql EnterPrise
Manager) which is outside our Network . i.e the machine is located at ISP.
it is giving me error SQL server does not exist or access denied.
i am specifying the IP address of remote machine to whom i want to access
remotely,
(SQL Server Properties ) under connection tab - (configuration done to
remote sql server)
i had selected the option of allowing other sql server to connect remotely
to this sql server using RPC
even i am not able register remote sql server in my local sql server.
Can anyone help me out what exactly we have to do for remote access of sql
server.
Thanks
Mitesh
Can you ping the SQL server?
Can you telnet to port 1433 from your side ?
Is there a firewall in between ?
Make sure you can connect on port 1433 otherwise it will not work , you
would then need to check whats blocking that port somewhere!
HTH
Dylan
"Mitesh Patel" <mitesh@.viraat.com> wrote in message
news:OJExAfU0EHA.1408@.TK2MSFTNGP10.phx.gbl...
> Hi
> i am trying to registering the remote sql server (MMC Sql EnterPrise
> Manager) which is outside our Network . i.e the machine is located at ISP.
> it is giving me error SQL server does not exist or access denied.
> i am specifying the IP address of remote machine to whom i want to access
> remotely,
> (SQL Server Properties ) under connection tab - (configuration done to
> remote sql server)
> i had selected the option of allowing other sql server to connect remotely
> to this sql server using RPC
> even i am not able register remote sql server in my local sql server.
> Can anyone help me out what exactly we have to do for remote access of sql
> server.
> Thanks
> Mitesh
>
>
|||when i ping to ip address it is showing destination host unreachable (this
is due to internet provider had stopped ping )
yes i am able to do telnet to port 1433 after passing the telnet command at
port 1433. the telnet window shows connecting... and then telnet screen
becomes blank (might it been connected and waiting for commands )
remote server is located in data center then firewall will be there
............
Thanks
Mitesh
"Dylan Kruger" <carmellobear1@.hotmail.com> wrote in message
news:uaq5Y8U0EHA.1396@.tk2msftngp13.phx.gbl...[vbcol=seagreen]
> Can you ping the SQL server?
> Can you telnet to port 1433 from your side ?
> Is there a firewall in between ?
> Make sure you can connect on port 1433 otherwise it will not work , you
> would then need to check whats blocking that port somewhere!
> HTH
> Dylan
>
> "Mitesh Patel" <mitesh@.viraat.com> wrote in message
> news:OJExAfU0EHA.1408@.TK2MSFTNGP10.phx.gbl...
ISP.[vbcol=seagreen]
access[vbcol=seagreen]
remotely[vbcol=seagreen]
sql
>
|||You should also make sure that it's the public IP you try to access or you
have the proper NAT settings in the Firewall in both ends. It could also be
the settings for your VPN connection (if that's what your using ) that needs
to be checked.
Regards
Steen
Dylan Kruger wrote:[vbcol=seagreen]
> Can you ping the SQL server?
> Can you telnet to port 1433 from your side ?
> Is there a firewall in between ?
> Make sure you can connect on port 1433 otherwise it will not work ,
> you would then need to check whats blocking that port somewhere!
> HTH
> Dylan
>
> "Mitesh Patel" <mitesh@.viraat.com> wrote in message
> news:OJExAfU0EHA.1408@.TK2MSFTNGP10.phx.gbl...
i am trying to registering the remote sql server (MMC Sql EnterPrise
Manager) which is outside our Network . i.e the machine is located at ISP.
it is giving me error SQL server does not exist or access denied.
i am specifying the IP address of remote machine to whom i want to access
remotely,
(SQL Server Properties ) under connection tab - (configuration done to
remote sql server)
i had selected the option of allowing other sql server to connect remotely
to this sql server using RPC
even i am not able register remote sql server in my local sql server.
Can anyone help me out what exactly we have to do for remote access of sql
server.
Thanks
Mitesh
Can you ping the SQL server?
Can you telnet to port 1433 from your side ?
Is there a firewall in between ?
Make sure you can connect on port 1433 otherwise it will not work , you
would then need to check whats blocking that port somewhere!
HTH
Dylan
"Mitesh Patel" <mitesh@.viraat.com> wrote in message
news:OJExAfU0EHA.1408@.TK2MSFTNGP10.phx.gbl...
> Hi
> i am trying to registering the remote sql server (MMC Sql EnterPrise
> Manager) which is outside our Network . i.e the machine is located at ISP.
> it is giving me error SQL server does not exist or access denied.
> i am specifying the IP address of remote machine to whom i want to access
> remotely,
> (SQL Server Properties ) under connection tab - (configuration done to
> remote sql server)
> i had selected the option of allowing other sql server to connect remotely
> to this sql server using RPC
> even i am not able register remote sql server in my local sql server.
> Can anyone help me out what exactly we have to do for remote access of sql
> server.
> Thanks
> Mitesh
>
>
|||when i ping to ip address it is showing destination host unreachable (this
is due to internet provider had stopped ping )
yes i am able to do telnet to port 1433 after passing the telnet command at
port 1433. the telnet window shows connecting... and then telnet screen
becomes blank (might it been connected and waiting for commands )
remote server is located in data center then firewall will be there
............
Thanks
Mitesh
"Dylan Kruger" <carmellobear1@.hotmail.com> wrote in message
news:uaq5Y8U0EHA.1396@.tk2msftngp13.phx.gbl...[vbcol=seagreen]
> Can you ping the SQL server?
> Can you telnet to port 1433 from your side ?
> Is there a firewall in between ?
> Make sure you can connect on port 1433 otherwise it will not work , you
> would then need to check whats blocking that port somewhere!
> HTH
> Dylan
>
> "Mitesh Patel" <mitesh@.viraat.com> wrote in message
> news:OJExAfU0EHA.1408@.TK2MSFTNGP10.phx.gbl...
ISP.[vbcol=seagreen]
access[vbcol=seagreen]
remotely[vbcol=seagreen]
sql
>
|||You should also make sure that it's the public IP you try to access or you
have the proper NAT settings in the Firewall in both ends. It could also be
the settings for your VPN connection (if that's what your using ) that needs
to be checked.
Regards
Steen
Dylan Kruger wrote:[vbcol=seagreen]
> Can you ping the SQL server?
> Can you telnet to port 1433 from your side ?
> Is there a firewall in between ?
> Make sure you can connect on port 1433 otherwise it will not work ,
> you would then need to check whats blocking that port somewhere!
> HTH
> Dylan
>
> "Mitesh Patel" <mitesh@.viraat.com> wrote in message
> news:OJExAfU0EHA.1408@.TK2MSFTNGP10.phx.gbl...
Remotely Connect to Sql Server
Hi
i am trying to registering the remote sql server (MMC Sql EnterPrise
Manager) which is outside our Network . i.e the machine is located at ISP.
it is giving me error SQL server does not exist or access denied.
i am specifying the IP address of remote machine to whom i want to access
remotely,
(SQL Server Properties ) under connection tab - (configuration done to
remote sql server)
i had selected the option of allowing other sql server to connect remotely
to this sql server using RPC
even i am not able register remote sql server in my local sql server.
Can anyone help me out what exactly we have to do for remote access of sql
server.
Thanks
MiteshCan you ping the SQL server?
Can you telnet to port 1433 from your side ?
Is there a firewall in between ?
Make sure you can connect on port 1433 otherwise it will not work , you
would then need to check whats blocking that port somewhere!
HTH
Dylan
"Mitesh Patel" <mitesh@.viraat.com> wrote in message
news:OJExAfU0EHA.1408@.TK2MSFTNGP10.phx.gbl...
> Hi
> i am trying to registering the remote sql server (MMC Sql EnterPrise
> Manager) which is outside our Network . i.e the machine is located at ISP.
> it is giving me error SQL server does not exist or access denied.
> i am specifying the IP address of remote machine to whom i want to access
> remotely,
> (SQL Server Properties ) under connection tab - (configuration done to
> remote sql server)
> i had selected the option of allowing other sql server to connect remotely
> to this sql server using RPC
> even i am not able register remote sql server in my local sql server.
> Can anyone help me out what exactly we have to do for remote access of sql
> server.
> Thanks
> Mitesh
>
>|||when i ping to ip address it is showing destination host unreachable (this
is due to internet provider had stopped ping )
yes i am able to do telnet to port 1433 after passing the telnet command at
port 1433. the telnet window shows connecting... and then telnet screen
becomes blank (might it been connected and waiting for commands )
remote server is located in data center then firewall will be there
............
Thanks
Mitesh
"Dylan Kruger" <carmellobear1@.hotmail.com> wrote in message
news:uaq5Y8U0EHA.1396@.tk2msftngp13.phx.gbl...
> Can you ping the SQL server?
> Can you telnet to port 1433 from your side ?
> Is there a firewall in between ?
> Make sure you can connect on port 1433 otherwise it will not work , you
> would then need to check whats blocking that port somewhere!
> HTH
> Dylan
>
> "Mitesh Patel" <mitesh@.viraat.com> wrote in message
> news:OJExAfU0EHA.1408@.TK2MSFTNGP10.phx.gbl...
> > Hi
> >
> > i am trying to registering the remote sql server (MMC Sql EnterPrise
> > Manager) which is outside our Network . i.e the machine is located at
ISP.
> > it is giving me error SQL server does not exist or access denied.
> >
> > i am specifying the IP address of remote machine to whom i want to
access
> > remotely,
> >
> > (SQL Server Properties ) under connection tab - (configuration done to
> > remote sql server)
> > i had selected the option of allowing other sql server to connect
remotely
> > to this sql server using RPC
> >
> > even i am not able register remote sql server in my local sql server.
> >
> > Can anyone help me out what exactly we have to do for remote access of
sql
> > server.
> >
> > Thanks
> > Mitesh
> >
> >
> >
>|||You should also make sure that it's the public IP you try to access or you
have the proper NAT settings in the Firewall in both ends. It could also be
the settings for your VPN connection (if that's what your using ) that needs
to be checked.
Regards
Steen
Dylan Kruger wrote:
> Can you ping the SQL server?
> Can you telnet to port 1433 from your side ?
> Is there a firewall in between ?
> Make sure you can connect on port 1433 otherwise it will not work ,
> you would then need to check whats blocking that port somewhere!
> HTH
> Dylan
>
> "Mitesh Patel" <mitesh@.viraat.com> wrote in message
> news:OJExAfU0EHA.1408@.TK2MSFTNGP10.phx.gbl...
>> Hi
>> i am trying to registering the remote sql server (MMC Sql EnterPrise
>> Manager) which is outside our Network . i.e the machine is located
>> at ISP. it is giving me error SQL server does not exist or access
>> denied.
>> i am specifying the IP address of remote machine to whom i want to
>> access remotely,
>> (SQL Server Properties ) under connection tab - (configuration
>> done to remote sql server)
>> i had selected the option of allowing other sql server to connect
>> remotely to this sql server using RPC
>> even i am not able register remote sql server in my local sql
>> server.
>> Can anyone help me out what exactly we have to do for remote access
>> of sql server.
>> Thanks
>> Mitesh
i am trying to registering the remote sql server (MMC Sql EnterPrise
Manager) which is outside our Network . i.e the machine is located at ISP.
it is giving me error SQL server does not exist or access denied.
i am specifying the IP address of remote machine to whom i want to access
remotely,
(SQL Server Properties ) under connection tab - (configuration done to
remote sql server)
i had selected the option of allowing other sql server to connect remotely
to this sql server using RPC
even i am not able register remote sql server in my local sql server.
Can anyone help me out what exactly we have to do for remote access of sql
server.
Thanks
MiteshCan you ping the SQL server?
Can you telnet to port 1433 from your side ?
Is there a firewall in between ?
Make sure you can connect on port 1433 otherwise it will not work , you
would then need to check whats blocking that port somewhere!
HTH
Dylan
"Mitesh Patel" <mitesh@.viraat.com> wrote in message
news:OJExAfU0EHA.1408@.TK2MSFTNGP10.phx.gbl...
> Hi
> i am trying to registering the remote sql server (MMC Sql EnterPrise
> Manager) which is outside our Network . i.e the machine is located at ISP.
> it is giving me error SQL server does not exist or access denied.
> i am specifying the IP address of remote machine to whom i want to access
> remotely,
> (SQL Server Properties ) under connection tab - (configuration done to
> remote sql server)
> i had selected the option of allowing other sql server to connect remotely
> to this sql server using RPC
> even i am not able register remote sql server in my local sql server.
> Can anyone help me out what exactly we have to do for remote access of sql
> server.
> Thanks
> Mitesh
>
>|||when i ping to ip address it is showing destination host unreachable (this
is due to internet provider had stopped ping )
yes i am able to do telnet to port 1433 after passing the telnet command at
port 1433. the telnet window shows connecting... and then telnet screen
becomes blank (might it been connected and waiting for commands )
remote server is located in data center then firewall will be there
............
Thanks
Mitesh
"Dylan Kruger" <carmellobear1@.hotmail.com> wrote in message
news:uaq5Y8U0EHA.1396@.tk2msftngp13.phx.gbl...
> Can you ping the SQL server?
> Can you telnet to port 1433 from your side ?
> Is there a firewall in between ?
> Make sure you can connect on port 1433 otherwise it will not work , you
> would then need to check whats blocking that port somewhere!
> HTH
> Dylan
>
> "Mitesh Patel" <mitesh@.viraat.com> wrote in message
> news:OJExAfU0EHA.1408@.TK2MSFTNGP10.phx.gbl...
> > Hi
> >
> > i am trying to registering the remote sql server (MMC Sql EnterPrise
> > Manager) which is outside our Network . i.e the machine is located at
ISP.
> > it is giving me error SQL server does not exist or access denied.
> >
> > i am specifying the IP address of remote machine to whom i want to
access
> > remotely,
> >
> > (SQL Server Properties ) under connection tab - (configuration done to
> > remote sql server)
> > i had selected the option of allowing other sql server to connect
remotely
> > to this sql server using RPC
> >
> > even i am not able register remote sql server in my local sql server.
> >
> > Can anyone help me out what exactly we have to do for remote access of
sql
> > server.
> >
> > Thanks
> > Mitesh
> >
> >
> >
>|||You should also make sure that it's the public IP you try to access or you
have the proper NAT settings in the Firewall in both ends. It could also be
the settings for your VPN connection (if that's what your using ) that needs
to be checked.
Regards
Steen
Dylan Kruger wrote:
> Can you ping the SQL server?
> Can you telnet to port 1433 from your side ?
> Is there a firewall in between ?
> Make sure you can connect on port 1433 otherwise it will not work ,
> you would then need to check whats blocking that port somewhere!
> HTH
> Dylan
>
> "Mitesh Patel" <mitesh@.viraat.com> wrote in message
> news:OJExAfU0EHA.1408@.TK2MSFTNGP10.phx.gbl...
>> Hi
>> i am trying to registering the remote sql server (MMC Sql EnterPrise
>> Manager) which is outside our Network . i.e the machine is located
>> at ISP. it is giving me error SQL server does not exist or access
>> denied.
>> i am specifying the IP address of remote machine to whom i want to
>> access remotely,
>> (SQL Server Properties ) under connection tab - (configuration
>> done to remote sql server)
>> i had selected the option of allowing other sql server to connect
>> remotely to this sql server using RPC
>> even i am not able register remote sql server in my local sql
>> server.
>> Can anyone help me out what exactly we have to do for remote access
>> of sql server.
>> Thanks
>> Mitesh
Remotely Connect to MSDE
Hi
I just installed MSDE over my Windows 2003 box and facing an small problem.
I installed it with SQL security mode and also set a password for user "sa".
Everything looks just fine using "osql" as it uses local address.
But I can't connect to my server from another computer using VS.NET Server Explorer.
It seems as MSDE is set to reject connections from outside by default.
My question is how to enable it so I can connect using my "sa" account.
Appreciate your help in advance.OK. are you trying to connect by IP address or server name? do you have a firewall installed?|||Since I am connecting from outside of the server, I am using IP address.
And also I don't have any firewall installed.|||at a guess I'd say you have only windows authentication enabled. not 100% sure how to change that in MSDE, but I'll scout around and see.
I just installed MSDE over my Windows 2003 box and facing an small problem.
I installed it with SQL security mode and also set a password for user "sa".
Everything looks just fine using "osql" as it uses local address.
But I can't connect to my server from another computer using VS.NET Server Explorer.
It seems as MSDE is set to reject connections from outside by default.
My question is how to enable it so I can connect using my "sa" account.
Appreciate your help in advance.OK. are you trying to connect by IP address or server name? do you have a firewall installed?|||Since I am connecting from outside of the server, I am using IP address.
And also I don't have any firewall installed.|||at a guess I'd say you have only windows authentication enabled. not 100% sure how to change that in MSDE, but I'll scout around and see.
Remote User Connection to SQL Server 7 Standard Edition
Is it possible to connect a remote user (in a wide area network) to a
database running on SQL Server 7 Standard Edition.
Do I need the Enterprise Edition to accomplish this?
Yes (to the first)
and
No (to the second)
Mike John
"guez" <guez@.discussions.microsoft.com> wrote in message
news:C4A2552E-74CA-4DDF-A1D1-4A1E05FB773C@.microsoft.com...
> Is it possible to connect a remote user (in a wide area network) to a
> database running on SQL Server 7 Standard Edition.
> Do I need the Enterprise Edition to accomplish this?
database running on SQL Server 7 Standard Edition.
Do I need the Enterprise Edition to accomplish this?
Yes (to the first)
and
No (to the second)
Mike John
"guez" <guez@.discussions.microsoft.com> wrote in message
news:C4A2552E-74CA-4DDF-A1D1-4A1E05FB773C@.microsoft.com...
> Is it possible to connect a remote user (in a wide area network) to a
> database running on SQL Server 7 Standard Edition.
> Do I need the Enterprise Edition to accomplish this?
Remote User Connection to SQL Server 7 Standard Edition
Is it possible to connect a remote user (in a wide area network) to a
database running on SQL Server 7 Standard Edition.
Do I need the Enterprise Edition to accomplish this?Yes (to the first)
and
No (to the second)
Mike John
"guez" <guez@.discussions.microsoft.com> wrote in message
news:C4A2552E-74CA-4DDF-A1D1-4A1E05FB773C@.microsoft.com...
> Is it possible to connect a remote user (in a wide area network) to a
> database running on SQL Server 7 Standard Edition.
> Do I need the Enterprise Edition to accomplish this?
database running on SQL Server 7 Standard Edition.
Do I need the Enterprise Edition to accomplish this?Yes (to the first)
and
No (to the second)
Mike John
"guez" <guez@.discussions.microsoft.com> wrote in message
news:C4A2552E-74CA-4DDF-A1D1-4A1E05FB773C@.microsoft.com...
> Is it possible to connect a remote user (in a wide area network) to a
> database running on SQL Server 7 Standard Edition.
> Do I need the Enterprise Edition to accomplish this?
Remote User Connection to SQL Server 7 Standard Edition
Is it possible to connect a remote user (in a wide area network) to a
database running on SQL Server 7 Standard Edition.
Do I need the Enterprise Edition to accomplish this?Yes (to the first)
and
No (to the second)
Mike John
"guez" <guez@.discussions.microsoft.com> wrote in message
news:C4A2552E-74CA-4DDF-A1D1-4A1E05FB773C@.microsoft.com...
> Is it possible to connect a remote user (in a wide area network) to a
> database running on SQL Server 7 Standard Edition.
> Do I need the Enterprise Edition to accomplish this?sql
database running on SQL Server 7 Standard Edition.
Do I need the Enterprise Edition to accomplish this?Yes (to the first)
and
No (to the second)
Mike John
"guez" <guez@.discussions.microsoft.com> wrote in message
news:C4A2552E-74CA-4DDF-A1D1-4A1E05FB773C@.microsoft.com...
> Is it possible to connect a remote user (in a wide area network) to a
> database running on SQL Server 7 Standard Edition.
> Do I need the Enterprise Edition to accomplish this?sql
Wednesday, March 21, 2012
Remote SSIS vs Domain\User: Access is Denied (0x80070005)
What OS permissions do I need to give a domain user to effectively connect to a remote instance of Integration Services?
I keep getting the following message:
Cannot connect to SQLDEV01
Failed to retreive data for this request.
Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)) (Microsoft.SqlServer.ManagedDTS)
I have already performed the Windows 2003 steps outlined in the "Eliminating the Access is Denied" error located at http://msdn2.microsoft.com/en-us/library/aa337083.aspx
I have no problem if the user is a local Administrator (go figure).
The MSDN page lacks another steps needed on W2K3 (not sure about XP) - add the account to Distributed COM Users group. (The page is being updated).|||Yes, I have done this, and gave the Domain\User the DCOM permissions upon the MsDtsSvr object. The Distributed COM Users step is actually included on ths webpage.
Thanks for responding. Perhaps there is another step missing?
|||JFoushee wrote:
The Distributed COM Users step is actually included on ths webpage.
Not really (if we get the same copy of http://msdn2.microsoft.com/en-us/library/aa337083.aspx).
The page talks about configuring security for MsDtsServer application, but on Windows 2003 Server and 64-bit XP machine there is another global per-machine setting: in DCOMCNFG right click My Computer, select Properties, find COM Security page and inspect both Edit Limits settings: they should allow the user to access the machine. The simplest way to do it is to add user to Distributed COM Users user group.
|||I believe I got it to work...
One the webpage http://msdn2.microsoft.com/en-us/library/aa337083.aspx, under "To configure rights for remote users on Windows Server 2003"...
replace step 9 with "Click OK to close the dialog box."
Add a step 9.1 with the following text: "On the same Security tab, under Access Permissions, select Customize, then click Edit to open the Access Permission dialog box."
Add a step 9.2 with the following text: "In the Access Permission dialog box, add or delete users, and assign the appropriate permissions to the appropriate users and groups. The available permissions are Local Access, and Remote Access. The easiest is to add the local DCOM Distributed Users group. "
Add a step 9.3 with the following text: "Click OK to close the dialog box. Close the MMC snap-in."
Step 10 stays as-is: "Restart the Integration Services service."
|||
Thanks a lot.
Finally I can connect to SSIS.
Remote SSIS vs Domain\User: Access is Denied (0x80070005)
What OS permissions do I need to give a domain user to effectively connect to a remote instance of Integration Services?
I keep getting the following message:
Cannot connect to SQLDEV01
Failed to retreive data for this request.
Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)) (Microsoft.SqlServer.ManagedDTS)
I have already performed the Windows 2003 steps outlined in the "Eliminating the Access is Denied" error located at http://msdn2.microsoft.com/en-us/library/aa337083.aspx
I have no problem if the user is a local Administrator (go figure).
The MSDN page lacks another steps needed on W2K3 (not sure about XP) - add the account to Distributed COM Users group. (The page is being updated).|||Yes, I have done this, and gave the Domain\User the DCOM permissions upon the MsDtsSvr object. The Distributed COM Users step is actually included on ths webpage.
Thanks for responding. Perhaps there is another step missing?
|||JFoushee wrote:
The Distributed COM Users step is actually included on ths webpage.
Not really (if we get the same copy of http://msdn2.microsoft.com/en-us/library/aa337083.aspx).
The page talks about configuring security for MsDtsServer application, but on Windows 2003 Server and 64-bit XP machine there is another global per-machine setting: in DCOMCNFG right click My Computer, select Properties, find COM Security page and inspect both Edit Limits settings: they should allow the user to access the machine. The simplest way to do it is to add user to Distributed COM Users user group.
|||I believe I got it to work...
One the webpage http://msdn2.microsoft.com/en-us/library/aa337083.aspx, under "To configure rights for remote users on Windows Server 2003"...
replace step 9 with "Click OK to close the dialog box."
Add a step 9.1 with the following text: "On the same Security tab, under Access Permissions, select Customize, then click Edit to open the Access Permission dialog box."
Add a step 9.2 with the following text: "In the Access Permission dialog box, add or delete users, and assign the appropriate permissions to the appropriate users and groups. The available permissions are Local Access, and Remote Access. The easiest is to add the local DCOM Distributed Users group. "
Add a step 9.3 with the following text: "Click OK to close the dialog box. Close the MMC snap-in."
Step 10 stays as-is: "Restart the Integration Services service."
|||
Thanks alot.
Finally I can connect to SSIS.
Remote SSIS vs Domain\User: Access is Denied (0x80070005)
What OS permissions do I need to give a domain user to effectively connect to a remote instance of Integration Services?
I keep getting the following message:
Cannot connect to SQLDEV01
Failed to retreive data for this request.
Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)) (Microsoft.SqlServer.ManagedDTS)
I have already performed the Windows 2003 steps outlined in the "Eliminating the Access is Denied" error located at http://msdn2.microsoft.com/en-us/library/aa337083.aspx
I have no problem if the user is a local Administrator (go figure).
The MSDN page lacks another steps needed on W2K3 (not sure about XP) - add the account to Distributed COM Users group. (The page is being updated).|||Yes, I have done this, and gave the Domain\User the DCOM permissions upon the MsDtsSvr object. The Distributed COM Users step is actually included on ths webpage.
Thanks for responding. Perhaps there is another step missing?
|||The Distributed COM Users step is actually included on ths webpage.
Not really (if we get the same copy of http://msdn2.microsoft.com/en-us/library/aa337083.aspx).
The page talks about configuring security for MsDtsServer application, but on Windows 2003 Server and 64-bit XP machine there is another global per-machine setting: in DCOMCNFG right click My Computer, select Properties, find COM Security page and inspect both Edit Limits settings: they should allow the user to access the machine. The simplest way to do it is to add user to Distributed COM Users user group.
|||I believe I got it to work...
One the webpage http://msdn2.microsoft.com/en-us/library/aa337083.aspx, under "To configure rights for remote users on Windows Server 2003"...
replace step 9 with "Click OK to close the dialog box."
Add a step 9.1 with the following text: "On the same Security tab, under Access Permissions, select Customize, then click Edit to open the Access Permission dialog box."
Add a step 9.2 with the following text: "In the Access Permission dialog box, add or delete users, and assign the appropriate permissions to the appropriate users and groups. The available permissions are Local Access, and Remote Access. The easiest is to add the local DCOM Distributed Users group. "
Add a step 9.3 with the following text: "Click OK to close the dialog box. Close the MMC snap-in."
Step 10 stays as-is: "Restart the Integration Services service."
|||
Thanks a lot.
Finally I can connect to SSIS.
sqlRemote SSIS Access
Hello,
We have discovered that unless a user is an administrator on the MS SQL 2005
server, they cannot connect to SSIS server locally or remotely.
The SQL Junkies site has the solution. They recommend that you first add the
user to the Distributed COM Users group. Then you should run
%windir%\system32\Com\comexp.msc to launch Component Services to launch
component server. On the properties of MsDtsServer you can choose security
and from there you can set the Remote Activation permissions to allow the
user to connect the SSIS server remotely. The SSIS service should then be
restarted.
I tried it and it works. However, what are the security implications with
this solution?The implications are basically just what you set - you allow
that user to connect remotely to the process for
MsDtsServer. Not much outside of that really - you're only
changing this for SSIS and that particular user.
-Sue
On Thu, 8 Jun 2006 14:04:04 -0600, "Loren Zubis"
<Loren.Zubis@.gov.ab.ca> wrote:
>Hello,
>We have discovered that unless a user is an administrator on the MS SQL 200
5
>server, they cannot connect to SSIS server locally or remotely.
>The SQL Junkies site has the solution. They recommend that you first add th
e
>user to the Distributed COM Users group. Then you should run
>%windir%\system32\Com\comexp.msc to launch Component Services to launch
>component server. On the properties of MsDtsServer you can choose security
>and from there you can set the Remote Activation permissions to allow the
>user to connect the SSIS server remotely. The SSIS service should then be
>restarted.
>I tried it and it works. However, what are the security implications with
>this solution?
>|||The implications are basically just what you set - you allow
that user to connect remotely to the process for
MsDtsServer. Not much outside of that really - you're only
changing this for SSIS and that particular user.
-Sue
On Thu, 8 Jun 2006 14:04:04 -0600, "Loren Zubis"
<Loren.Zubis@.gov.ab.ca> wrote:
>Hello,
>We have discovered that unless a user is an administrator on the MS SQL 200
5
>server, they cannot connect to SSIS server locally or remotely.
>The SQL Junkies site has the solution. They recommend that you first add th
e
>user to the Distributed COM Users group. Then you should run
>%windir%\system32\Com\comexp.msc to launch Component Services to launch
>component server. On the properties of MsDtsServer you can choose security
>and from there you can set the Remote Activation permissions to allow the
>user to connect the SSIS server remotely. The SSIS service should then be
>restarted.
>I tried it and it works. However, what are the security implications with
>this solution?
>
We have discovered that unless a user is an administrator on the MS SQL 2005
server, they cannot connect to SSIS server locally or remotely.
The SQL Junkies site has the solution. They recommend that you first add the
user to the Distributed COM Users group. Then you should run
%windir%\system32\Com\comexp.msc to launch Component Services to launch
component server. On the properties of MsDtsServer you can choose security
and from there you can set the Remote Activation permissions to allow the
user to connect the SSIS server remotely. The SSIS service should then be
restarted.
I tried it and it works. However, what are the security implications with
this solution?The implications are basically just what you set - you allow
that user to connect remotely to the process for
MsDtsServer. Not much outside of that really - you're only
changing this for SSIS and that particular user.
-Sue
On Thu, 8 Jun 2006 14:04:04 -0600, "Loren Zubis"
<Loren.Zubis@.gov.ab.ca> wrote:
>Hello,
>We have discovered that unless a user is an administrator on the MS SQL 200
5
>server, they cannot connect to SSIS server locally or remotely.
>The SQL Junkies site has the solution. They recommend that you first add th
e
>user to the Distributed COM Users group. Then you should run
>%windir%\system32\Com\comexp.msc to launch Component Services to launch
>component server. On the properties of MsDtsServer you can choose security
>and from there you can set the Remote Activation permissions to allow the
>user to connect the SSIS server remotely. The SSIS service should then be
>restarted.
>I tried it and it works. However, what are the security implications with
>this solution?
>|||The implications are basically just what you set - you allow
that user to connect remotely to the process for
MsDtsServer. Not much outside of that really - you're only
changing this for SSIS and that particular user.
-Sue
On Thu, 8 Jun 2006 14:04:04 -0600, "Loren Zubis"
<Loren.Zubis@.gov.ab.ca> wrote:
>Hello,
>We have discovered that unless a user is an administrator on the MS SQL 200
5
>server, they cannot connect to SSIS server locally or remotely.
>The SQL Junkies site has the solution. They recommend that you first add th
e
>user to the Distributed COM Users group. Then you should run
>%windir%\system32\Com\comexp.msc to launch Component Services to launch
>component server. On the properties of MsDtsServer you can choose security
>and from there you can set the Remote Activation permissions to allow the
>user to connect the SSIS server remotely. The SSIS service should then be
>restarted.
>I tried it and it works. However, what are the security implications with
>this solution?
>
remote sql server connection
Hi all,
I am trying to connect to remote sql server in vb.net application.
I am getting an error "login failed for user'abc' ".
why am I getting this error, what could be the possible reason.
any help will be appreciated.what is the login and password in your database?
whats ur connection string in vb.net?|||http://www.freevbcode.com/ShowCode.asp?ID=2226 a template to perform the task.
What is the connection string set and SQL server authentication?|||Originally posted by deidei76
what is the login and password in your database?
whats ur connection string in vb.net?
login: abc
password: abc
"data source=IP address of server;initial catalog=databasename;persist security info=False;user id=abc;workstation id=WSID;packet size=4096"|||Originally posted by Satya
http://www.freevbcode.com/ShowCode.asp?ID=2226 a template to perform the task.
What is the connection string set and SQL server authentication?
thanks satya.I am able to connect to the server now. simple and stupid mistake.I forgot to mention password in connection string.
I am trying to connect to remote sql server in vb.net application.
I am getting an error "login failed for user'abc' ".
why am I getting this error, what could be the possible reason.
any help will be appreciated.what is the login and password in your database?
whats ur connection string in vb.net?|||http://www.freevbcode.com/ShowCode.asp?ID=2226 a template to perform the task.
What is the connection string set and SQL server authentication?|||Originally posted by deidei76
what is the login and password in your database?
whats ur connection string in vb.net?
login: abc
password: abc
"data source=IP address of server;initial catalog=databasename;persist security info=False;user id=abc;workstation id=WSID;packet size=4096"|||Originally posted by Satya
http://www.freevbcode.com/ShowCode.asp?ID=2226 a template to perform the task.
What is the connection string set and SQL server authentication?
thanks satya.I am able to connect to the server now. simple and stupid mistake.I forgot to mention password in connection string.
Remote SQL Server Connect using VB Studio?
I've read all of the related questions and none answer my situation. I am using Visual Studio 2005. I have not been able to connect to the remote SQL database at all. I have attempted to write a SMO to make the connection however, the info I have been able to get to on MSDN didn’t have enough information to carry me through.
Here is the code I found it on MSDN and have been attempting to use.
Module Module1
Sub Main()
Imports Microsoft.SqlServer.Management.Smo
Imports Microsoft.SqlServer.Management.Common
'Declare a ServerConnection object variable to specify SQL authentication, login and password.
Dim conn As New ServerConnection
conn.LoginSecure = False
conn.Login = xxxx
conn.Password = xxxxx
'Connect to the local, default instance of SQL Server.
Dim srv As Server
srv = New Server(conn)
'The actual connection is made when a property is retrieved.
Console.WriteLine(srv.Information.Version)
'The connection is automatically disconnected when the Server variable goes out of scope.
End Sub
End Module
The code executes however, nothing happens. I don’t know where the IP address comes into play. Thanks in advance.
· SQL Server 2005 Standard
· TCPIP
· Server not starting (I’m able to connect using SQL Server Management Studio
· I don’t know whether SQL Browser is enabled enabled. I use the IP address when using SQL Server Management Studio
· I’m not sure however, I believe it runs under Network Service with the Host provider
· I have not made a firewall exception
· Windows XPSP2
· Running Norton AntiVirus 2007
Thanks for any help or advice.
The conn object will takt the ip address if you want to connect with one of that to the server, then you probably do not nee the login and the password specified in the code as you can pass it with the connection string. (See connectionstrings.com for more information) If you want to specify the login and password within your application you can use the new Server("10.10.10.10") (as 10.10.10.10 is the IPAddress)
Jens K. Suessmeyer.
http://www.sqlserver2005.de
|||Thank you
Remote SQL Debug: Server cannot connect to the debugger on my mach
Hello,
I am trying to debug a stored procedure on remote server. The debugger
starts and passes through without stopping.
No error messages are generated on the client.
On the server the following error appears in the Application Log:
Event Type: Error
Event Source: SQLDebugging98
Event Category: None
Event ID: 1
Date: 10/7/2005
Time: 4:41:47 PM
User: N/A
Computer: <server>
Description:
SQL Server is running as '<domain account>' and cannot connect to the
debugger on machine '<my machine>' (error = 0x80070005 Access is denied. ).
Use one of the following options to fix this error. 1) Run SQL Server as
"Local System", as a domain account, or as a local account with identical
usernames and passwords on both machine '<server>' and '<my machine>'. 2)
Verify that machine '<server>' can open files on machine '<my machine>'.
Debugging disabled for connection 55.
Server is Windows 2003 Standard running SQL 2000 SP4 with .NET remote
debugging support.
Client is Windows XP Pro SP2 running SQL 2000 SP4 and .NET 1.1 SP1.
Windows Firewall is disabled on both machines.
All DCOM permissions seems to be set OK on the server. I am a local admin on
the server and sys admin on SQL server and I can run sp_sdidebug without any
problems.
I can debug SQL on my local machine using Query Analyzer and VS.NET without
any problems. I can also debug SQL using Query Analyzer on the server if I
log there with my account.
What could prevent SQL debugger from connecting to my workstation? I tried
to add that SQL service account to my local admin group, but it did not help
.
I am not sure what is required to "2) Verify that machine '<server>' can ope
n
files on machine '<my machine>'." Does it mean that I have to trust my serve
r
machine? How can I do that?
What else could be wrong?Hello Serge,
You wrote in conference microsoft.public.sqlserver.programming on Fri, 7
Oct 2005 17:25:03 -0700:
SM> I am trying to debug a stored procedure on remote server. The debugger
SM> starts and passes through without stopping.
http://support.microsoft.com/defaul...kb;en-us;841249
and especially
http://support.microsoft.com/defaul...kb;en-us;839280
Vadm Rapp|||After spending few hours troubleshooting my local COM+ security and killing
my registry :) I found the settings that make remote SQL debugging work for
SQL Analyzer and VS.NET.
All these settings apply to the Default COM Security for Windows XP
Workstation from which debugging is initiated.
Access Permissions:
-- Limits:
* ANONYMOUS LOGON - Allow All (Required to debug from SQL Analyzer)
* Everyone - Allow All (Required to debug from VS.NET)
Launch and Activation Permissions:
Limits (add)
* ANONYMOUS LOGON - Allow All (Required to debug from VS.NET)
Default (add)
* ANONYMOUS LOGON - Allow All (Required to debug from VS.NET)
Huh!
Of course all settings on the server must be done first as described in
several knowlege articles. If firewall is anabled, then it should be adresse
d
as well.
"Serge Matsevilo" wrote:
> Hello,
> I am trying to debug a stored procedure on remote server. The debugger
> starts and passes through without stopping.
> No error messages are generated on the client.
> On the server the following error appears in the Application Log:
> Event Type: Error
> Event Source: SQLDebugging98
> Event Category: None
> Event ID: 1
> Date: 10/7/2005
> Time: 4:41:47 PM
> User: N/A
> Computer: <server>
> Description:
> SQL Server is running as '<domain account>' and cannot connect to the
> debugger on machine '<my machine>' (error = 0x80070005 Access is denied. )
.
> Use one of the following options to fix this error. 1) Run SQL Server as
> "Local System", as a domain account, or as a local account with identical
> usernames and passwords on both machine '<server>' and '<my machine>'. 2)
> Verify that machine '<server>' can open files on machine '<my machine>'.
> Debugging disabled for connection 55.
> Server is Windows 2003 Standard running SQL 2000 SP4 with .NET remote
> debugging support.
> Client is Windows XP Pro SP2 running SQL 2000 SP4 and .NET 1.1 SP1.
> Windows Firewall is disabled on both machines.
> All DCOM permissions seems to be set OK on the server. I am a local admin
on
> the server and sys admin on SQL server and I can run sp_sdidebug without a
ny
> problems.
> I can debug SQL on my local machine using Query Analyzer and VS.NET withou
t
> any problems. I can also debug SQL using Query Analyzer on the server if I
> log there with my account.
> What could prevent SQL debugger from connecting to my workstation? I tried
> to add that SQL service account to my local admin group, but it did not he
lp.
> I am not sure what is required to "2) Verify that machine '<server>' can o
pen
> files on machine '<my machine>'." Does it mean that I have to trust my ser
ver
> machine? How can I do that?
> What else could be wrong?
I am trying to debug a stored procedure on remote server. The debugger
starts and passes through without stopping.
No error messages are generated on the client.
On the server the following error appears in the Application Log:
Event Type: Error
Event Source: SQLDebugging98
Event Category: None
Event ID: 1
Date: 10/7/2005
Time: 4:41:47 PM
User: N/A
Computer: <server>
Description:
SQL Server is running as '<domain account>' and cannot connect to the
debugger on machine '<my machine>' (error = 0x80070005 Access is denied. ).
Use one of the following options to fix this error. 1) Run SQL Server as
"Local System", as a domain account, or as a local account with identical
usernames and passwords on both machine '<server>' and '<my machine>'. 2)
Verify that machine '<server>' can open files on machine '<my machine>'.
Debugging disabled for connection 55.
Server is Windows 2003 Standard running SQL 2000 SP4 with .NET remote
debugging support.
Client is Windows XP Pro SP2 running SQL 2000 SP4 and .NET 1.1 SP1.
Windows Firewall is disabled on both machines.
All DCOM permissions seems to be set OK on the server. I am a local admin on
the server and sys admin on SQL server and I can run sp_sdidebug without any
problems.
I can debug SQL on my local machine using Query Analyzer and VS.NET without
any problems. I can also debug SQL using Query Analyzer on the server if I
log there with my account.
What could prevent SQL debugger from connecting to my workstation? I tried
to add that SQL service account to my local admin group, but it did not help
.
I am not sure what is required to "2) Verify that machine '<server>' can ope
n
files on machine '<my machine>'." Does it mean that I have to trust my serve
r
machine? How can I do that?
What else could be wrong?Hello Serge,
You wrote in conference microsoft.public.sqlserver.programming on Fri, 7
Oct 2005 17:25:03 -0700:
SM> I am trying to debug a stored procedure on remote server. The debugger
SM> starts and passes through without stopping.
http://support.microsoft.com/defaul...kb;en-us;841249
and especially
http://support.microsoft.com/defaul...kb;en-us;839280
Vadm Rapp|||After spending few hours troubleshooting my local COM+ security and killing
my registry :) I found the settings that make remote SQL debugging work for
SQL Analyzer and VS.NET.
All these settings apply to the Default COM Security for Windows XP
Workstation from which debugging is initiated.
Access Permissions:
-- Limits:
* ANONYMOUS LOGON - Allow All (Required to debug from SQL Analyzer)
* Everyone - Allow All (Required to debug from VS.NET)
Launch and Activation Permissions:
Limits (add)
* ANONYMOUS LOGON - Allow All (Required to debug from VS.NET)
Default (add)
* ANONYMOUS LOGON - Allow All (Required to debug from VS.NET)
Huh!
Of course all settings on the server must be done first as described in
several knowlege articles. If firewall is anabled, then it should be adresse
d
as well.
"Serge Matsevilo" wrote:
> Hello,
> I am trying to debug a stored procedure on remote server. The debugger
> starts and passes through without stopping.
> No error messages are generated on the client.
> On the server the following error appears in the Application Log:
> Event Type: Error
> Event Source: SQLDebugging98
> Event Category: None
> Event ID: 1
> Date: 10/7/2005
> Time: 4:41:47 PM
> User: N/A
> Computer: <server>
> Description:
> SQL Server is running as '<domain account>' and cannot connect to the
> debugger on machine '<my machine>' (error = 0x80070005 Access is denied. )
.
> Use one of the following options to fix this error. 1) Run SQL Server as
> "Local System", as a domain account, or as a local account with identical
> usernames and passwords on both machine '<server>' and '<my machine>'. 2)
> Verify that machine '<server>' can open files on machine '<my machine>'.
> Debugging disabled for connection 55.
> Server is Windows 2003 Standard running SQL 2000 SP4 with .NET remote
> debugging support.
> Client is Windows XP Pro SP2 running SQL 2000 SP4 and .NET 1.1 SP1.
> Windows Firewall is disabled on both machines.
> All DCOM permissions seems to be set OK on the server. I am a local admin
on
> the server and sys admin on SQL server and I can run sp_sdidebug without a
ny
> problems.
> I can debug SQL on my local machine using Query Analyzer and VS.NET withou
t
> any problems. I can also debug SQL using Query Analyzer on the server if I
> log there with my account.
> What could prevent SQL debugger from connecting to my workstation? I tried
> to add that SQL service account to my local admin group, but it did not he
lp.
> I am not sure what is required to "2) Verify that machine '<server>' can o
pen
> files on machine '<my machine>'." Does it mean that I have to trust my ser
ver
> machine? How can I do that?
> What else could be wrong?
Remote SQL connection
Hello everyone, I am trying to connect to a remote SQL 2005 database from Microsoft SQL Server Management Studio.
I enabled the remote connection on the server and creating a user on the server.
I am trying to connect to the server from my workstation using sql server authentication with the login name already created on the server.
I am receiving this error: cannot connect to "server name"
cannot open user default database. Login failed.
Login failed for user "username".(Microsoft SQL Server, Error: 4064)
Can anyone help?
under your server registration properties... do you have authentication set to "SQL Server Authentication"?
You aren't behind a firewall that blocks connections to your remote? (they do this on corporate networks)...
Tuesday, March 20, 2012
Remote SQL
Hello everyone, I am trying to connect to a remote SQL 2005 database from Microsoft SQL Server Management Studio.
I enabled the remote connection on the server and creating a user on the server.
I am trying to connect to the server from my workstation using sql server authentication with the login name already created on the server.
I am receiving this error: cannot connect to "server name"
cannot open user default database. Login failed.
Login failed for user "username".(Microsoft SQL Server, Error: 4064)
Can you help?
Whilst you created an account on the machine, have you granted that account access to its default database which hopefully is your application database?
Also, you can investigate what the connection string should be like:
1) Create an empty text file in windows explorer and rename it to X.UDL
2) Double click on it and the datalink provider dialog will appear.
3) Select the provider tab. Find the provider for SQL Server express and click next.
4) Select your database and select integerated authentication.
5) Test the connection and save it.
6) Compare the contents of X.UDL with your connections string.
You could try looking on http://www.connectionstrings.com/ for examples of connection strings.
HTH
Subscribe to:
Posts (Atom)