Cant get list of servers

I can't get my server to show with the DMO function ListAvailableSQLServers or with the osql -L flag. The OS is windows 2000, but the drive is fat32 and doesn't have Directory Service.
Do you need NTFS to have Directory Service, and does SQL Server need Directory Service to broadcast its available servers?
I've got Visual Studio .Net and had no luck when I searched for an answer.I meant Active Directory.|||no neither ADS nor NTFS is essential for server listing. r u able to connect to other servers using EM or QA? is EM showing the complete list? of not there could be issues with the broadcasting server. check if 1433 port is not blocked by any firewall programa at server end. also check that the server is not hidden by server network utility >> TCPIP >> hide server.|||It is actually MSDE, so I don't have EM or QA. But I have Visual Studio .Net and it has Server Explorer which functions much like EM and QA. The databases and programs I use to connect are on the same machine. I use this to learn/practice SQL Server. I don't have a machine with a server OS, so I can't check "proper" server operation.
But yes, Server Explorer connects and shows my SS instance. I can use osql, programs I create in VB.net, or even web pages scripted with ADO or DMO objects to connect and modify the SS databases, as long as I specify the server. The only thing I can't seem to do is get a list of the servers (I only have one server).
I have a software firewall, but only have it running while my dial-up is online.
Not sure what you mean by "server network utility >> TCPIP >> hide server". I have the server/client tools that were included (in the tools\binn folder); the program cnfgsvr.exe sounds like a good place to start. I'll check it out.
Thanks|||the server network utility i am referring to uses ...\bin\svrnetcn.exe (non-msde version). the exe u have identified may work as well, not sure. for same machine sql server uses shared-memory net lib. if TCPIP or Named Pipe is not enabled, i have seen that OSQL -L fails to identify local server...|||Yeah, that's the one,SVRNETCN.EXE, the Sql Server Network Utility. Both Tcp/Ip and Named Pipes protocols are enabled, the default port 1433 is set, and the Hide Server option is unchecked.
I forgot to mention that my MSDE was included free with my VS.Net. When I installed it, I chose all the defaults which gave my sql server an instance name of VSDOTNET. I don't know why it didn't just install with the default computername. Maybe that has something to do with it?
So I used the Sql Server Client Network Utility, CLICONFG.EXE, and created aliases, one for tcp/ip and one for named pipes. The aliases were listed properly with OSQL -L and using the DMO App.ListAvailableSQLServers() function. I don't know why computername\vsdotnet won't list without the aliases.

Can't get groups to work

Hi,
1. I have an Access ADP on SQL2000, uaing Windows users and groups..
2. Individual users with granted permissions work OK.
3. However, if I drop the individual users and try to uses the Windows
groups which contain them with same permissions granted, the app cannot make
connection.
4. Have revoked logins, re-added logins, database grants, and permissions,
but to no avail.
Any suggestions on what to look for?
Thanks.
AlanCan you make successfull connections from Query Analyser or OSQL.exe based
upon the group ?
Is the group a local group or domain based group?
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Kevin,
Thanks for your reply.
1. I can't connect with query analyzer, logging on to users's machine with
user's login but only his group login and group database access existing in
SQLServer.
2. User's group is a Universal domain group.
Using SQL@.000.
Useer: WinXP
OS: Win2000Server
DB Machine: Win2000 Server.
Regards,
Alan
"Kevin McDonnell [MSFT]" <kevmc@.online.microsoft.com> wrote in message
news:0WvCdgfxEHA.3640@.cpmsftngxa10.phx.gbl...
> Can you make successfull connections from Query Analyser or OSQL.exe based
> upon the group ?
> Is the group a local group or domain based group?
> Thanks,
> Kevin McDonnell
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>
>|||Ah. The problem may be the Universal Group.. There was a fix for this. Try
this update.
825042 FIX: SQL Server Jobs That Are Owned by Non-sysadmin Users May Not
Start
http://support.microsoft.com/?id=825042
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Kevin,
Thanks for your reply.
This sounds like it applies to jobs only, not regular database accesss. Do
you know if it applies to database access as well.
I'd like to avoid hotfixes on client's computers as well, plus I don't know
if they have installed required Win2000 SP4.
Thanks.
Alan
"Kevin McDonnell [MSFT]" <kevmc@.online.microsoft.com> wrote in message
news:7AkfzfpxEHA.768@.cpmsftngxa10.phx.gbl...
> Ah. The problem may be the Universal Group.. There was a fix for this.
Try
> this update.
> 825042 FIX: SQL Server Jobs That Are Owned by Non-sysadmin Users May Not
> Start
> http://support.microsoft.com/?id=825042
>
> Thanks,
> Kevin McDonnell
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>
>|||Its' been some time since I did testing, but I don't think we enumerate
Universal Groups only Domain Global Groups.
Try;
xp_logininf groupname
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||"Kevin McDonnell [MSFT]" <kevmc@.online.microsoft.com> wrote in message
news:0mIdcZrxEHA.3984@.cpmsftngxa10.phx.gbl...
> Its' been some time since I did testing, but I don't think we enumerate
> Universal Groups only Domain Global Groups.
> Try;
> xp_logininf groupname
Kevin,
Thanks again for your reply.
I've asked net admin to recreate groups as global, not universal.
In meantime, I've put results of xp_logininfo below.
1. xp_login 'GroupAccountName', 'members': properly displays list of members
2. xp_login 'GroupMemberAccountName', 'all': gives NULL RECORD!!
3. If, as a test, I add the GroupMemberAccountName to SQL logins as new
separate login IndividualUserName and do
xp_login 'IndividualUserName', 'all' :
then displays individual user's record, but no additional record for group
path.
CONCLUSION?
--
Does above mean that somewhere no connection is being made in SQLServer
between the group and the individual member?
BOL on xp_logininfo: If account_name is a valid Windows NT account but that
account does not have permission to access SQL Server, an empty result set
is returned.
Thanks very much.
Alan|||I know that Domain Local Groups won't work correctly for jobs and I
couldn't remember the results with Universal Groups.
Another question is , Is SQL Server in the same Domain that the users
groups are defined in?
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Kevin,
It's in a separate domain.
Alan
"Kevin McDonnell [MSFT]" <kevmc@.online.microsoft.com> wrote in message
news:0Jw0SF1xEHA.3984@.cpmsftngxa10.phx.gbl...
> I know that Domain Local Groups won't work correctly for jobs and I
> couldn't remember the results with Universal Groups.
> Another question is , Is SQL Server in the same Domain that the users
> groups are defined in?
> Thanks,
> Kevin McDonnell
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>
>

Can't Generate SSPI

Hi,
I'm trying to configure a Windows Authentication SQL Server user and I get a
message that the compuetr can;t generate an SSPI connection. The Enterprise
Manager then won't connect to the SQL Server. The VS.NET 2003 enviroment, w
hich is the user preferred
connection enviroment to the SQL Server also won't connect.
The user has SQL Server 2000 Develop edition SP3a installed on the computer
and we are trying to connect to a SQL Server 2000 Enterprise edition SP3a. T
he user also has on his computer VS6 and VS.NET 2003.
Does any one know the cause of this problems?
Thanks,Try these links:
http://www.sqlservercentral.com/col...kb;en-us;811889
Ray Higdon MCSE, MCDBA, CCNA
--
"Shai Goldberg" <gshai(removethis)@.shamir.co.il> wrote in message
news:B52289F3-1E9F-410F-B49C-BCB73C80D1AD@.microsoft.com...
> Hi,
> I'm trying to configure a Windows Authentication SQL Server user and I get
a message that the compuetr can;t generate an SSPI connection. The
Enterprise Manager then won't connect to the SQL Server. The VS.NET 2003
enviroment, which is the user preferred connection enviroment to the SQL
Server also won't connect.
> The user has SQL Server 2000 Develop edition SP3a installed on the
computer and we are trying to connect to a SQL Server 2000 Enterprise
edition SP3a. The user also has on his computer VS6 and VS.NET 2003.
> Does any one know the cause of this problems?
> Thanks,|||Thanks,sql

CAN'T FULLY UNINSTALL SQL SERVER 2005 STANDARD

We have a Windows Server 2003 SP1 machine with two hard drives. I
installed MS SQL Server 2005 without paying attantion to where it
installed to. The c: drive is very small while d: is large. SQL
installed on c:. Apparentely, log files were growing and filled up all
the space on c:. I couldn't access SQL Server and decided uninstall it.
I went ahead and uninstall all components via add/remove programs.
After that I noticed all sql folders on c: are present, all services
are running and I was able to open Management Studio. At the same time
no SQL products are listed in add/remove. I need to fully uninstall it.
I tried command prompt pointing to the setup.exe file (where I copied
disks since it is a remote server) and failed.
Please, help!!!
StanYou did a reboot, right?
"suslikovich" <suslikovich@.yahoo.com> wrote in message
news:1146518232.810806.181140@.y43g2000cwc.googlegroups.com...
> We have a Windows Server 2003 SP1 machine with two hard drives. I
> installed MS SQL Server 2005 without paying attantion to where it
> installed to. The c: drive is very small while d: is large. SQL
> installed on c:. Apparentely, log files were growing and filled up all
> the space on c:. I couldn't access SQL Server and decided uninstall it.
> I went ahead and uninstall all components via add/remove programs.
> After that I noticed all sql folders on c: are present, all services
> are running and I was able to open Management Studio. At the same time
> no SQL products are listed in add/remove. I need to fully uninstall it.
> I tried command prompt pointing to the setup.exe file (where I copied
> disks since it is a remote server) and failed.
> Please, help!!!
> Stan
>|||Yes, I did a reboot after I uninstalled all sql products.
Stan

Can't Find SQL Native Client in ODBC Connection Manager in SQL Server Open Database Connectivit

I apologize if this is not the correct forum for this posting. Looking at the descriptions, it appeared to be the best choice.

I am running Windows XP Pro SP2. I have installed the SQL Native Client for

XP. However, when I try to add a new data source through ODBC Connection

Manager, SQL Native Client is not listed as an option. I have followed this procedure on three other systems with no problems. What would be causing the

SQL Native Client to not show up in the list of available ODBC data sources?

Hi, James,

First of all - are you sure that the installation of the SQL Native Client completed successfully? Do you see the packet in the Add/Remove Programs applet? What you can try first is to uninstall (if available) and reinstall the Client, check if any errors or warnings would be reported.

Going further - the ODBC drivers information is stored in the registry. Using regedit, go to HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI and check if the SQL Native Client driver is present, the entries in the folder as well as an entry at "HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\ODBC Drivers" folder.

If the SQL Native Client driver is not present in the registry, you might have a permission issue. One possible approach is to run and capture a RegMon log during the installation (http://www.microsoft.com/technet/sysinternals/SystemInformation/Regmon.mspx) and see if access to the key above failed.

If the SQL Native Client driver is present in the registry, then for some reason the ODBC Administrator fails to enumerate it or it contains invalid entries. First step would be to compare the entries to a "working" machine and then you could probably use RegMon again - this time when running ODBC Administrator.

Based on the findings, you could take corrective actions and start seeing the driver properly.

HTH,

Jivko Dobrev - MSFT
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||Thanks for the reply. SQL Native Client does appear in Add/Remove programs, and I am able to uninstall and reinstall. I will do the other checks you mentioned, and let you know the results. Thanks.|||

I am having a very similar problem. I am using Visual C++ 2005 Express and have installed the Microsoft SQL Server Native Client. All the mentioned registrty entries appear to be correct. I have also include all of the ODBC components in my toolbox. When I try to configure the ODBC data adpater, create a new connection, the only types of data sources that are in the possible list are the SQL Server and Access. If I add an OdbcConnection tool to the form and try to modify the connection string to a new connection, I get a message that the data provider identified by guid "all zeroes" could not be loaded. It would appear that csomething is missing.

I have tried to find a "Data" component to reference in the project that might include the missing component, but have had no success.

Can't Find SQL Native Client in ODBC Connection Manager in SQL Server Open Database Connectivit

I apologize if this is not the correct forum for this posting. Looking at the descriptions, it appeared to be the best choice.

I am running Windows XP Pro SP2. I have installed the SQL Native Client for XP. However, when I try to add a new data source through ODBC Connection Manager, SQL Native Client is not listed as an option. I have followed this procedure on three other systems with no problems. What would be causing the SQL Native Client to not show up in the list of available ODBC data sources?

Hi, James,

First of all - are you sure that the installation of the SQL Native Client completed successfully? Do you see the packet in the Add/Remove Programs applet? What you can try first is to uninstall (if available) and reinstall the Client, check if any errors or warnings would be reported.

Going further - the ODBC drivers information is stored in the registry. Using regedit, go to HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI and check if the SQL Native Client driver is present, the entries in the folder as well as an entry at "HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\ODBC Drivers" folder.

If the SQL Native Client driver is not present in the registry, you might have a permission issue. One possible approach is to run and capture a RegMon log during the installation (http://www.microsoft.com/technet/sysinternals/SystemInformation/Regmon.mspx) and see if access to the key above failed.

If the SQL Native Client driver is present in the registry, then for some reason the ODBC Administrator fails to enumerate it or it contains invalid entries. First step would be to compare the entries to a "working" machine and then you could probably use RegMon again - this time when running ODBC Administrator.

Based on the findings, you could take corrective actions and start seeing the driver properly.

HTH,

Jivko Dobrev - MSFT
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||Thanks for the reply. SQL Native Client does appear in Add/Remove programs, and I am able to uninstall and reinstall. I will do the other checks you mentioned, and let you know the results. Thanks.
|||

I am having a very similar problem. I am using Visual C++ 2005 Express and have installed the Microsoft SQL Server Native Client. All the mentioned registrty entries appear to be correct. I have also include all of the ODBC components in my toolbox. When I try to configure the ODBC data adpater, create a new connection, the only types of data sources that are in the possible list are the SQL Server and Access. If I add an OdbcConnection tool to the form and try to modify the connection string to a new connection, I get a message that the data provider identified by guid "all zeroes" could not be loaded. It would appear that csomething is missing.

I have tried to find a "Data" component to reference in the project that might include the missing component, but have had no success.

sql

Can't Find SQL Native Client in ODBC Connection Manager

I am running Windows XP Pro SP2. I have installed the SQL Native Client for
XP. However, when I try to add a new data source through ODBC Connection
Manager, SQL Native Client is not listed as an option. I have followed this
procedure on three other systems with no problems. What would be causing the
SQL Native Client to not show up in the list of available ODBC data sources?MDAC issues, related DLL conflicts. The ODBC Data Source
Administrator piece can get hosed out with DLL conflicts on
an MDAC installation. You'd probably want to start checking
the MDAC installation using component checker. You can
download it from:
http://msdn2.microsoft.com/en-us/data/aa937730.aspx
-Sue
On Tue, 13 Feb 2007 10:31:01 -0800, Jim Strickland <Jim
Strickland@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>I am running Windows XP Pro SP2. I have installed the SQL Native Client for
>XP. However, when I try to add a new data source through ODBC Connection
>Manager, SQL Native Client is not listed as an option. I have followed this
>procedure on three other systems with no problems. What would be causing th
e
>SQL Native Client to not show up in the list of available ODBC data sources?[/vbcol
]

Can't Find SQL Native Client in ODBC Connection Manager

I am running Windows XP Pro SP2. I have installed the SQL Native Client for
XP. However, when I try to add a new data source through ODBC Connection
Manager, SQL Native Client is not listed as an option. I have followed this
procedure on three other systems with no problems. What would be causing the
SQL Native Client to not show up in the list of available ODBC data sources?
MDAC issues, related DLL conflicts. The ODBC Data Source
Administrator piece can get hosed out with DLL conflicts on
an MDAC installation. You'd probably want to start checking
the MDAC installation using component checker. You can
download it from:
http://msdn2.microsoft.com/en-us/data/aa937730.aspx
-Sue
On Tue, 13 Feb 2007 10:31:01 -0800, Jim Strickland <Jim
Strickland@.discussions.microsoft.com> wrote:

>I am running Windows XP Pro SP2. I have installed the SQL Native Client for
>XP. However, when I try to add a new data source through ODBC Connection
>Manager, SQL Native Client is not listed as an option. I have followed this
>procedure on three other systems with no problems. What would be causing the
>SQL Native Client to not show up in the list of available ODBC data sources?

Can't find server

Hello
I installed the old MSDE 2000 (not release a) on a Windows XP Pro machine. I
manage the DB with the MSDE Manager from Vale Software. On the machine it
self, it works fine. I can select the DB and connect as 'sa' with password.
But on every other machine in the network, I can't connect to the DB. I can
ping to the server, that's no problem. I can chose the server in MSDE
Manager (and other DB-Tools like 'Aqua Data Studio' and 'DBVisualizer') but
I always get an error message like 'Cannot find server'. On the XP machine
there is no firewall running and -of course- the SQL-Server task is started.
The port 1433 isn't blocked.
Have enyone an idea why I can connect the DB on the machine it self but not
from every other machine in the network?
Thanks a lot
Dani
It's possible that the server does not have the network connectivity library
enabled.
i don't know how re-enable it in MSDE after MSDE is already installed.
Although i know it can be done, i read it a few days ago in the MSDE2000A
readme.
If it were SQL server, i'd say use the "Server Network Utility" (i think
it's called that). In that you can enable/disable tcpip,netbios,
multiprotocol, flatulance, etc.
"Daniel Geisseler" <d.geisseler@.gmx.net> wrote in message
news:2lk43sFd4pjhU1@.uni-berlin.de...
> Hello
> I installed the old MSDE 2000 (not release a) on a Windows XP Pro machine.
I
> manage the DB with the MSDE Manager from Vale Software. On the machine it
> self, it works fine. I can select the DB and connect as 'sa' with
password.
> But on every other machine in the network, I can't connect to the DB. I
can
> ping to the server, that's no problem. I can chose the server in MSDE
> Manager (and other DB-Tools like 'Aqua Data Studio' and 'DBVisualizer')
but
> I always get an error message like 'Cannot find server'. On the XP machine
> there is no firewall running and -of course- the SQL-Server task is
started.
> The port 1433 isn't blocked.
> Have enyone an idea why I can connect the DB on the machine it self but
not
> from every other machine in the network?
> Thanks a lot
> Dani
>
|||If you run svrnetcn.exe from the /Program Files/Microsoft SQL
Server/80/Tools/BINN folder it will bring up the Server network utility, you
can make sure the network libraries are enabled.
HTH
Dylan Kruger
"Ian Boyd" <admin@.SWIFTPA.NET> wrote in message
news:eGyjL5ZaEHA.1048@.tk2msftngp13.phx.gbl...
> It's possible that the server does not have the network connectivity
> library
> enabled.
> i don't know how re-enable it in MSDE after MSDE is already installed.
> Although i know it can be done, i read it a few days ago in the MSDE2000A
> readme.
> If it were SQL server, i'd say use the "Server Network Utility" (i think
> it's called that). In that you can enable/disable tcpip,netbios,
> multiprotocol, flatulance, etc.
>
> "Daniel Geisseler" <d.geisseler@.gmx.net> wrote in message
> news:2lk43sFd4pjhU1@.uni-berlin.de...
> I
> password.
> can
> but
> started.
> not
>
|||Yeah, exactly that's it! The TCP/IP was disabled. I don't now why but after
I startet again, it works fine.
1000 thanks to you...
Dani
1000 thanks
"Dylan kruger" <carmellobear1@.hotmail.com> schrieb im Newsbeitrag
news:eC7EjuaaEHA.3112@.tk2msftngp13.phx.gbl...
> If you run svrnetcn.exe from the /Program Files/Microsoft SQL
> Server/80/Tools/BINN folder it will bring up the Server network utility,
you[vbcol=seagreen]
> can make sure the network libraries are enabled.
> HTH
> Dylan Kruger
> "Ian Boyd" <admin@.SWIFTPA.NET> wrote in message
> news:eGyjL5ZaEHA.1048@.tk2msftngp13.phx.gbl...
MSDE2000A[vbcol=seagreen]
it
>
|||It's a new feature of MSDE, that by default it doesn't act like any other
server application on earth.
Go figure.
Probably Microsoft's tired of hearing people XXXXX about being
wormed/hacked/infected, and they just say, "Fine, your XXX get's no
connectivity anymore. Suck it!"
"Daniel Geisseler" <d.geisseler@.gmx.net> wrote in message
news:2lmm2oFept7kU1@.uni-berlin.de...
> Yeah, exactly that's it! The TCP/IP was disabled. I don't now why but
after[vbcol=seagreen]
> I startet again, it works fine.
> 1000 thanks to you...
> Dani
>
> 1000 thanks
> "Dylan kruger" <carmellobear1@.hotmail.com> schrieb im Newsbeitrag
> news:eC7EjuaaEHA.3112@.tk2msftngp13.phx.gbl...
> you
> MSDE2000A
think[vbcol=seagreen]
machine[vbcol=seagreen]
> it
I[vbcol=seagreen]
'DBVisualizer')[vbcol=seagreen]
but
>
|||I had a similar problem - I was not able to connect to the MSDE from
any other machine. I had tried openning the TCP/IP Port (1433) and even
shutting down the Firewall.
Eventually, I was able to able to fix the issue by adding the registry
value for "ProtocolList" under HKEY_LOCAL_MACHINE -> SOFTWARE ->
Microsoft -> MSSQLServer -> SuperSocketNetLib
But now I have a different issue. How can I connect to the MSDE
instance with DBVisualizer? I tried to create a connection but when I
try to select / edit a Driver the drop down is empty and I cannot get
one from the list that I get by hitting the Edit button.
Please help.
- manzoor

Can't find PInvoke sqlceme30.dll

I am using an O2 XDA II mini running Windows Mobile 2003 SE. Tried creating a Windows Mobile 5.0 Pocket PC project but during deployment, I get this error.

Can't find PInvoke sqlceme30.dll

I have searched thru the forums and found something similar. I tried all their recommendations but no luck. Is there anything I am doing wrong? I copied the DLL files in the device's \Windows directory (sqlceme30.dll, sql*.dll...around 5 DLLs)

I would appreciate any assistance

Please install SQL Mobile CAB, do not copy these DLLs to the device manually. Also it's not clear to me why exactly you would use Windows Mobile 5.0 project for Windows Mobile 2003 device instead of using Windows Mobile 2003 project?

This error is a runtime error, not deployment error, so it appears your application was deployed OK but can not load this DLL probably because you don't have SQL Mobile CAB installed. Normally VS 2005 would install it, but since you're using wrong project type it might fail to do so.

|||

Hi Ilya,

I was just testing it out. Not really for production. I just want to make sure I am doing things right. How do you install the CAB files in the device?

|||

1. Copy CAB file to the device.

2. Click on a CAB from device file explorer.

|||I was able to install SQL Server on my device. I just did the good old restart - - - a soft reset.|||

Hello,

i had the same problem, and i think the manual installation of the CAB file will work, but isn't there a way to deploy the needed cab with the pda application (to include everything in the deployable package of the application)?

Regards

Martin

|||

Sure. It's up to you to create that package. Usually it's an MSI for a desktop which installs NETCF, SQL Mobile and your application CABs via Active Sync to the connected device.

Note: CAB in a CAB is not possible since only one instance of WCELOAD is allowed and it's already running installing first CAB.

|||In my case, the file sqlceme30.dll doesn't appear in \windows directory.

I install only the cabs "sqlce30.ppc.wce5.armv4i.CAB" and

"NETCFv2.wm.armv4i.cab", first de sql and then the framework, as VS do

when deploy.

The solution is install first the framework and after the sql. In this order "sqlceme30.dll" appear in \windows.

I have installed Compact Framework SP1 with the latest patch.|||

Yes, you have to install NETCF first. If NETCF it not detected by SQL Mobile CAB, it won't install managed provider and related files and your managed application won’t work.

Can't find PInvoke sqlceme30.dll

I am using an O2 XDA II mini running Windows Mobile 2003 SE. Tried creating a Windows Mobile 5.0 Pocket PC project but during deployment, I get this error.

Can't find PInvoke sqlceme30.dll

I have searched thru the forums and found something similar. I tried all their recommendations but no luck. Is there anything I am doing wrong? I copied the DLL files in the device's \Windows directory (sqlceme30.dll, sql*.dll...around 5 DLLs)

I would appreciate any assistance

Please install SQL Mobile CAB, do not copy these DLLs to the device manually. Also it's not clear to me why exactly you would use Windows Mobile 5.0 project for Windows Mobile 2003 device instead of using Windows Mobile 2003 project?

This error is a runtime error, not deployment error, so it appears your application was deployed OK but can not load this DLL probably because you don't have SQL Mobile CAB installed. Normally VS 2005 would install it, but since you're using wrong project type it might fail to do so.

|||

Hi Ilya,

I was just testing it out. Not really for production. I just want to make sure I am doing things right. How do you install the CAB files in the device?

|||

1. Copy CAB file to the device.

2. Click on a CAB from device file explorer.

|||I was able to install SQL Server on my device. I just did the good old restart - - - a soft reset.|||

Hello,

i had the same problem, and i think the manual installation of the CAB file will work, but isn't there a way to deploy the needed cab with the pda application (to include everything in the deployable package of the application)?

Regards

Martin

|||

Sure. It's up to you to create that package. Usually it's an MSI for a desktop which installs NETCF, SQL Mobile and your application CABs via Active Sync to the connected device.

Note: CAB in a CAB is not possible since only one instance of WCELOAD is allowed and it's already running installing first CAB.

|||In my case, the file sqlceme30.dll doesn't appear in \windows directory.

I install only the cabs "sqlce30.ppc.wce5.armv4i.CAB" and

"NETCFv2.wm.armv4i.cab", first de sql and then the framework, as VS do

when deploy.

The solution is install first the framework and after the sql. In this order "sqlceme30.dll" appear in \windows.

I have installed Compact Framework SP1 with the latest patch.|||

Yes, you have to install NETCF first. If NETCF it not detected by SQL Mobile CAB, it won't install managed provider and related files and your managed application won’t work.

Can't find PInvoke DLL 'sqlceme30.dll'

I am developing for an ipaq handheld. I just upgraded to Windows Mobile 5.0 and tried to run my application and I get this message.

Can't find PInvoke DLL 'sqlceme30.dll'

I am using a sql Mobile DB and vs2005
found fix here: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=220816&SiteID=1
sql

Can't Execute Package from BIDS Solution Explorer Post SP2 Install

Yesterday, SQL Server 2005 SP2 was installed on our DEV Server (Windows 2003 SP1 x86) and now I cannot right-click a package in the Solutions Explorer window in BIDS and Execute Package. When I do, I get the following error

===================================

Object reference not set to an instance of an object. (Microsoft Visual Studio)

Program Location:

at Microsoft.DataTransformationServices.Project.DtsPackagesFolderProjectFeature.ExecuteTaskOrPackage(ProjectItem prjItem, String taskPath)

I know I could do this yesterday morning pre SP2. I've attempted this with a couple of different packages and solutions, so it is probably not a corrupt package (unless now they are all corrupt). I can execute in debug mode if I open the package first and then hit Start Debugging. However this is not always an optimal solution because I sometimes have many connected packages and sometimes what gets executed is not what is expected.

Your thoughts would be appreciated.

I'm having the identical problem. If I create a new package, it will work for a short period of time. I didn't measure the time precisely, but it is within 15 minutes and an hour or so. I appreciate your run-in-debug solution, but it is still not a clean fix.sql

Can't Deploy AdventureWorks Database

Hi All,

I created a named instance of SQL SERVER 2005 (Evaluation version) on Windows XP pro, attached the AdventureWorks and AdventureWorks DW databases to the database engine, and tried to deploy the AdventureWorks DW (Enterprise and Standard) database in Analysis Services using SQL SERVER Business Intelligence Development Studio.

For some reason, I encountered the following error (after deployment during processing):

Error 1 OLE DB error: OLE DB or ODBC error: Login timeout expired; HYT00; An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.; 08001; Named Pipes Provider: Could not open a connection to SQL Server [2]. ; 08001. 0 0

Please note that I used the configuration manager to enable named pipes and allow remote connections. I also, renamed the target server (to the named server instance instead of the localhost), disabled my Windows and Norton firewalls, and changed the deployment server edition to the Evaluation version in the Adventure Works DW Property page.

Nothing seems to work. Any help would be greatly appreciated!

Thanks,

Raj

Hi,

We also experienced a similar problem deploying the AdventureWorks DW using the Business Intelligence Development Studio. Our error is as follows:

Error 1 OLE DB error: OLE DB or ODBC error: Communication link failure; 08S01; Shared Memory Provider: The system cannot open the file. ; 08S01; Login failed for user 'NT AUTHORITY\SYSTEM'.; 28000; Cannot open database requested in login 'AdventureWorksDW'. Login fails.; 42000. 0 0

This error occurred after we had dropped and uninstalled the sample databases from a previous install. Please note we downloaded the samples from Microsoft and used the AdventureWorks Data Warehouse Database and Analysis Services Project to install the databases.

Brad

|||

We are having the exact same error. Did you all find a solution?

|||

I'm moving this post to the Tools forum since this isn't a setup or upgrade issue.

G'luck.

|||Hi everyone!
I just had the same problem and solved it. What you have to do is:
1) Right-click the project name, and choose properties
2) In the deployment tab change the server name from localhost to your instance name
3) Double-click the data source in solution explorer
4) In General tab click Edit to change the connection string
5) Choose Native OLE DB\Microsoft OLE DB Provider for SQL Server
6) Type in your server name
7) Select the AdventureWorksDW as database name and click OK
Now the deployment should be successfull...|||

Try:

Double click on AdvantureWork.ds from DataSource (From Solution Explorer). and in Impersonation Information Select the Use the Service Account.

Can't Deploy AdventureWorks Database

Hi All,

I created a named instance of SQL SERVER 2005 (Evaluation version) on Windows XP pro, attached the AdventureWorks and AdventureWorks DW databases to the database engine, and tried to deploy the AdventureWorks DW (Enterprise and Standard) database in Analysis Services using SQL SERVER Business Intelligence Development Studio.

For some reason, I encountered the following error (after deployment during processing):

Error 1 OLE DB error: OLE DB or ODBC error: Login timeout expired; HYT00; An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.; 08001; Named Pipes Provider: Could not open a connection to SQL Server [2]. ; 08001. 0 0

Please note that I used the configuration manager to enable named pipes and allow remote connections. I also, renamed the target server (to the named server instance instead of the localhost), disabled my Windows and Norton firewalls, and changed the deployment server edition to the Evaluation version in the Adventure Works DW Property page.

Nothing seems to work. Any help would be greatly appreciated!

Thanks,

Raj

Hi,

We also experienced a similar problem deploying the AdventureWorks DW using the Business Intelligence Development Studio. Our error is as follows:

Error 1 OLE DB error: OLE DB or ODBC error: Communication link failure; 08S01; Shared Memory Provider: The system cannot open the file. ; 08S01; Login failed for user 'NT AUTHORITY\SYSTEM'.; 28000; Cannot open database requested in login 'AdventureWorksDW'. Login fails.; 42000. 0 0

This error occurred after we had dropped and uninstalled the sample databases from a previous install. Please note we downloaded the samples from Microsoft and used the AdventureWorks Data Warehouse Database and Analysis Services Project to install the databases.

Brad

|||

We are having the exact same error. Did you all find a solution?

|||

I'm moving this post to the Tools forum since this isn't a setup or upgrade issue.

G'luck.

|||Hi everyone!
I just had the same problem and solved it. What you have to do is:
1) Right-click the project name, and choose properties
2) In the deployment tab change the server name from localhost to your instance name
3) Double-click the data source in solution explorer
4) In General tab click Edit to change the connection string
5) Choose Native OLE DB\Microsoft OLE DB Provider for SQL Server
6) Type in your server name
7) Select the AdventureWorksDW as database name and click OK
Now the deployment should be successfull...|||

Try:

Double click on AdvantureWork.ds from DataSource (From Solution Explorer). and in Impersonation Information Select the Use the Service Account.

Can't Deploy AdventureWorks Database

Hi All,

I created a named instance of SQL SERVER 2005 (Evaluation version) on Windows XP pro, attached the AdventureWorks and AdventureWorks DW databases to the database engine, and tried to deploy the AdventureWorks DW (Enterprise and Standard) database in Analysis Services using SQL SERVER Business Intelligence Development Studio.

For some reason, I encountered the following error (after deployment during processing):

Error 1 OLE DB error: OLE DB or ODBC error: Login timeout expired; HYT00; An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.; 08001; Named Pipes Provider: Could not open a connection to SQL Server [2]. ; 08001. 0 0

Please note that I used the configuration manager to enable named pipes and allow remote connections. I also, renamed the target server (to the named server instance instead of the localhost), disabled my Windows and Norton firewalls, and changed the deployment server edition to the Evaluation version in the Adventure Works DW Property page.

Nothing seems to work. Any help would be greatly appreciated!

Thanks,

Raj

Hi,

We also experienced a similar problem deploying the AdventureWorks DW using the Business Intelligence Development Studio. Our error is as follows:

Error 1 OLE DB error: OLE DB or ODBC error: Communication link failure; 08S01; Shared Memory Provider: The system cannot open the file. ; 08S01; Login failed for user 'NT AUTHORITY\SYSTEM'.; 28000; Cannot open database requested in login 'AdventureWorksDW'. Login fails.; 42000. 0 0

This error occurred after we had dropped and uninstalled the sample databases from a previous install. Please note we downloaded the samples from Microsoft and used the AdventureWorks Data Warehouse Database and Analysis Services Project to install the databases.

Brad

|||

We are having the exact same error. Did you all find a solution?

|||

I'm moving this post to the Tools forum since this isn't a setup or upgrade issue.

G'luck.

|||Hi everyone!
I just had the same problem and solved it. What you have to do is:
1) Right-click the project name, and choose properties
2) In the deployment tab change the server name from localhost to your instance name
3) Double-click the data source in solution explorer
4) In General tab click Edit to change the connection string
5) Choose Native OLE DB\Microsoft OLE DB Provider for SQL Server
6) Type in your server name
7) Select the AdventureWorksDW as database name and click OK
Now the deployment should be successfull...|||

Try:

Double click on AdvantureWork.ds from DataSource (From Solution Explorer). and in Impersonation Information Select the Use the Service Account.

cant delete odbc tracing file..

Hi all
I can not delete the odbc manager tracing file.
Even after disabling tracing (in the odbc manager)
i get a windows massage saing another program is using the odbc tracing
file...
Can i stop the odbc manager service?
What other programs may be using this log?
There is no other runing programm or sql server job.
Please help, this file is growing so fast!
TIA
Rea
Rea,
Refer the below snippet from :
'PRB: ODBC Tracing to SQL.LOG Can Slow SQL Server or Consume All Disk Space'
http://support.microsoft.com/?id=268591
<start quote>
To turn off ODBC Tracing and remove the associated file, follow these steps:
1.. To disable ODBC Tracing:
1.. For Microsoft Windows NT 4.0:
a.. On the Start menu, click on Control Panel, and then click on Data
Sources(ODBC).
b.. Click on the Tracing tab, and choose Stop Tracing Now.
2.. For Microsoft Windows 2000:
a.. On the Start menu, click on Control Panel, click on Administrative
Tools, and then click on Data Sources (ODBC).
b.. Click on the Tracing tab, and choose Stop Tracing Now.
2.. Stop all ODBC applications, and stop SQL Server. In some cases it may
be necessary to reboot the server to free up the file so that it can be
deleted.
3.. Delete the ODBC Tracing file, usually called "C:\SQL.LOG."
4.. Restart SQL Server.
<end quote>
Dinesh
SQL Server MVP
--
SQL Server FAQ at
http://www.tkdinesh.com
"Rea Peleg" <rea_p@.afek.co.il> wrote in message
news:eKbGsGHTEHA.1472@.TK2MSFTNGP09.phx.gbl...
> Hi all
> I can not delete the odbc manager tracing file.
> Even after disabling tracing (in the odbc manager)
> i get a windows massage saing another program is using the odbc tracing
> file...
> Can i stop the odbc manager service?
> What other programs may be using this log?
> There is no other runing programm or sql server job.
> Please help, this file is growing so fast!
> TIA
> Rea
>
|||Thanks alot !
"Dinesh T.K" <tkdinesh@.nospam.mail.tkdinesh.com> wrote in message
news:uaDVzOHTEHA.1732@.TK2MSFTNGP09.phx.gbl...
> Rea,
> Refer the below snippet from :
> 'PRB: ODBC Tracing to SQL.LOG Can Slow SQL Server or Consume All Disk
Space'
> http://support.microsoft.com/?id=268591
> <start quote>
> To turn off ODBC Tracing and remove the associated file, follow these
steps:
> 1.. To disable ODBC Tracing:
> 1.. For Microsoft Windows NT 4.0:
> a.. On the Start menu, click on Control Panel, and then click on
Data
> Sources(ODBC).
> b.. Click on the Tracing tab, and choose Stop Tracing Now.
> 2.. For Microsoft Windows 2000:
> a.. On the Start menu, click on Control Panel, click on
Administrative
> Tools, and then click on Data Sources (ODBC).
> b.. Click on the Tracing tab, and choose Stop Tracing Now.
> 2.. Stop all ODBC applications, and stop SQL Server. In some cases it
may
> be necessary to reboot the server to free up the file so that it can be
> deleted.
> 3.. Delete the ODBC Tracing file, usually called "C:\SQL.LOG."
> 4.. Restart SQL Server.
> <end quote>
> --
> Dinesh
> SQL Server MVP
> --
> --
> SQL Server FAQ at
> http://www.tkdinesh.com
> "Rea Peleg" <rea_p@.afek.co.il> wrote in message
> news:eKbGsGHTEHA.1472@.TK2MSFTNGP09.phx.gbl...
>

cant delete odbc tracing file..

Hi all
I can not delete the odbc manager tracing file.
Even after disabling tracing (in the odbc manager)
i get a windows massage saing another program is using the odbc tracing
file...
Can i stop the odbc manager service'
What other programs may be using this log?
There is no other runing programm or sql server job.
Please help, this file is growing so fast!
TIA
ReaRea,
Refer the below snippet from :
'PRB: ODBC Tracing to SQL.LOG Can Slow SQL Server or Consume All Disk Space'
http://support.microsoft.com/?id=268591
<start quote>
To turn off ODBC Tracing and remove the associated file, follow these steps:
1.. To disable ODBC Tracing:
1.. For Microsoft Windows NT 4.0:
a.. On the Start menu, click on Control Panel, and then click on Data
Sources(ODBC).
b.. Click on the Tracing tab, and choose Stop Tracing Now.
2.. For Microsoft Windows 2000:
a.. On the Start menu, click on Control Panel, click on Administrative
Tools, and then click on Data Sources (ODBC).
b.. Click on the Tracing tab, and choose Stop Tracing Now.
2.. Stop all ODBC applications, and stop SQL Server. In some cases it may
be necessary to reboot the server to free up the file so that it can be
deleted.
3.. Delete the ODBC Tracing file, usually called "C:\SQL.LOG."
4.. Restart SQL Server.
<end quote>
Dinesh
SQL Server MVP
--
--
SQL Server FAQ at
http://www.tkdinesh.com
"Rea Peleg" <rea_p@.afek.co.il> wrote in message
news:eKbGsGHTEHA.1472@.TK2MSFTNGP09.phx.gbl...
> Hi all
> I can not delete the odbc manager tracing file.
> Even after disabling tracing (in the odbc manager)
> i get a windows massage saing another program is using the odbc tracing
> file...
> Can i stop the odbc manager service'
> What other programs may be using this log?
> There is no other runing programm or sql server job.
> Please help, this file is growing so fast!
> TIA
> Rea
>|||Thanks alot !
"Dinesh T.K" <tkdinesh@.nospam.mail.tkdinesh.com> wrote in message
news:uaDVzOHTEHA.1732@.TK2MSFTNGP09.phx.gbl...
> Rea,
> Refer the below snippet from :
> 'PRB: ODBC Tracing to SQL.LOG Can Slow SQL Server or Consume All Disk
Space'
> http://support.microsoft.com/?id=268591
> <start quote>
> To turn off ODBC Tracing and remove the associated file, follow these
steps:
> 1.. To disable ODBC Tracing:
> 1.. For Microsoft Windows NT 4.0:
> a.. On the Start menu, click on Control Panel, and then click on
Data
> Sources(ODBC).
> b.. Click on the Tracing tab, and choose Stop Tracing Now.
> 2.. For Microsoft Windows 2000:
> a.. On the Start menu, click on Control Panel, click on
Administrative
> Tools, and then click on Data Sources (ODBC).
> b.. Click on the Tracing tab, and choose Stop Tracing Now.
> 2.. Stop all ODBC applications, and stop SQL Server. In some cases it
may
> be necessary to reboot the server to free up the file so that it can be
> deleted.
> 3.. Delete the ODBC Tracing file, usually called "C:\SQL.LOG."
> 4.. Restart SQL Server.
> <end quote>
> --
> Dinesh
> SQL Server MVP
> --
> --
> SQL Server FAQ at
> http://www.tkdinesh.com
> "Rea Peleg" <rea_p@.afek.co.il> wrote in message
> news:eKbGsGHTEHA.1472@.TK2MSFTNGP09.phx.gbl...
>

Can't delete a maintenance plan in SQL 2005

hi everyone,
Thank you for your help in advance. I just set up a MS SQL 2005 standard
server with SP2 for one of my finance software. The OS is Windows 2003 with
SP2.
The database itself is checked with "2000 sql compatible". I also have TCP,
and Named Pipes enable. The server is in the AD domain. I use both Windows
and SQL authentication with my sa account.
I just created a maintenance plan in the Studio console so that the backup
and reindex can run on the server db. However, the job failed last nite. I
decide delete the plan and set up another one. I connected to the server by
using the Studio console on itself and tried to remove the plan, but it
failed. I clicked on the error (a link displayed in the Studio) said the
following:
#############
Exception has been thrown by the target of an invocation. (mscorlib)
Additional information:
An error has occurred while establishing a connection to the server. When
connecting to the SQL server 2005, this failure may be caused by the fact
that under the default settings SQL server does not allow remote connections.
(provide: Named Pipes Provide, error: 40 - Could not open a connection to SQL
Server)(Microsoft SQL server, Error:53)
##############
I have made sure the remote connection (right click on the server object in
the Studio thing) is enabled. As mentioend, I also made sure the named pipes
is enabled (\\.\pipe\sql\query).
May you provide idea so that I can remove the plan successfully?
Thank you!
Bobson
Were you able to fix your problem? I have the same issue but didn't found
anything helpful yet.
Thanks
Denis Desjardins
"Bobson" wrote:

> hi everyone,
> Thank you for your help in advance. I just set up a MS SQL 2005 standard
> server with SP2 for one of my finance software. The OS is Windows 2003 with
> SP2.
> The database itself is checked with "2000 sql compatible". I also have TCP,
> and Named Pipes enable. The server is in the AD domain. I use both Windows
> and SQL authentication with my sa account.
> I just created a maintenance plan in the Studio console so that the backup
> and reindex can run on the server db. However, the job failed last nite. I
> decide delete the plan and set up another one. I connected to the server by
> using the Studio console on itself and tried to remove the plan, but it
> failed. I clicked on the error (a link displayed in the Studio) said the
> following:
> #############
> Exception has been thrown by the target of an invocation. (mscorlib)
> Additional information:
> An error has occurred while establishing a connection to the server. When
> connecting to the SQL server 2005, this failure may be caused by the fact
> that under the default settings SQL server does not allow remote connections.
> (provide: Named Pipes Provide, error: 40 - Could not open a connection to SQL
> Server)(Microsoft SQL server, Error:53)
> ##############
> I have made sure the remote connection (right click on the server object in
> the Studio thing) is enabled. As mentioend, I also made sure the named pipes
> is enabled (\\.\pipe\sql\query).
> May you provide idea so that I can remove the plan successfully?
> Thank you!
> Bobson
|||Dennis,
Great someone read my post Before telling my point of view... I would
like to ask if you do the following :
1.) Put the sql in the domain
2.) rename the server couple times as the task already created
3.) use different admin account to log on and config both sql and OS (I am
still thinking permission related)
I have no one to respond to me as I could not find any solution on the Net
(the closest one is to run some scripts and clean up registry). The problem
still remains. But I did a test by setting up a clean new server with the
SQL. And I cannot duplicate the problem! In the test I do not do anythings I
mentioned above...
I was about to submit an issue to MS... but the SQL admin finally said we
could ignore the issue...so I just seize my action.
May I get your person email so we can talk more about it? Mine is
ultrabobson@.hotmail.com
Thank you, and stay in touch.
Bobson
"Denis Desjardins" wrote:
[vbcol=seagreen]
> Were you able to fix your problem? I have the same issue but didn't found
> anything helpful yet.
> Thanks
> Denis Desjardins
> "Bobson" wrote:
|||Bobson,
I send you an email on your hotmail address but didn't have any answer yet.
Here's what i mention in my email:
Yes I actually renamed the server, or more precisely the virtual server name
since I’m running on a cluster, after the maintenance plan was created. I
know that’s related, but I just want to be able to delete those problematic
plans and recreated them afterward. Any idea?
"Bobson" wrote:
[vbcol=seagreen]
> Dennis,
> Great someone read my post Before telling my point of view... I would
> like to ask if you do the following :
> 1.) Put the sql in the domain
> 2.) rename the server couple times as the task already created
> 3.) use different admin account to log on and config both sql and OS (I am
> still thinking permission related)
> I have no one to respond to me as I could not find any solution on the Net
> (the closest one is to run some scripts and clean up registry). The problem
> still remains. But I did a test by setting up a clean new server with the
> SQL. And I cannot duplicate the problem! In the test I do not do anythings I
> mentioned above...
> I was about to submit an issue to MS... but the SQL admin finally said we
> could ignore the issue...so I just seize my action.
> May I get your person email so we can talk more about it? Mine is
> ultrabobson@.hotmail.com
> Thank you, and stay in touch.
> Bobson
>
> "Denis Desjardins" wrote:
|||Hi Dennis,
I am sorry if I might overlook it... Please try again with my
ultrabobson@.yahoo.com (or hotmail.com)
So you have very similar issue as what we did. We did not have any
reolsutions yet...even though we renamed the server back to the original
name. But it still could not resovle the issue. What we ran around was to
crate another plan.
I have couple of Technet tickets and I might try to submit the issue to
them. I may not do this tsoon, but I will keep you posted once I do that.
Stay in touch.
Bobson
"Denis Desjardins" wrote:
[vbcol=seagreen]
> Bobson,
> I send you an email on your hotmail address but didn't have any answer yet.
> Here's what i mention in my email:
> Yes I actually renamed the server, or more precisely the virtual server name
> since I’m running on a cluster, after the maintenance plan was created. I
> know that’s related, but I just want to be able to delete those problematic
> plans and recreated them afterward. Any idea?
>
> "Bobson" wrote:

Can't delete a maintenance plan in SQL 2005

hi everyone,
Thank you for your help in advance. I just set up a MS SQL 2005 standard
server with SP2 for one of my finance software. The OS is Windows 2003 with
SP2.
The database itself is checked with "2000 sql compatible". I also have TCP,
and Named Pipes enable. The server is in the AD domain. I use both Windows
and SQL authentication with my sa account.
I just created a maintenance plan in the Studio console so that the backup
and reindex can run on the server db. However, the job failed last nite. I
decide delete the plan and set up another one. I connected to the server by
using the Studio console on itself and tried to remove the plan, but it
failed. I clicked on the error (a link displayed in the Studio) said the
following:
#############
Exception has been thrown by the target of an invocation. (mscorlib)
Additional information:
An error has occurred while establishing a connection to the server. When
connecting to the SQL server 2005, this failure may be caused by the fact
that under the default settings SQL server does not allow remote connections
.
(provide: Named Pipes Provide, error: 40 - Could not open a connection to SQ
L
Server)(Microsoft SQL server, Error:53)
##############
I have made sure the remote connection (right click on the server object in
the Studio thing) is enabled. As mentioend, I also made sure the named pipes
is enabled (\\.\pipe\sql\query).
May you provide idea so that I can remove the plan successfully?
Thank you!
BobsonWere you able to fix your problem? I have the same issue but didn't found
anything helpful yet.
Thanks
Denis Desjardins
"Bobson" wrote:

> hi everyone,
> Thank you for your help in advance. I just set up a MS SQL 2005 standard
> server with SP2 for one of my finance software. The OS is Windows 2003 wit
h
> SP2.
> The database itself is checked with "2000 sql compatible". I also have TCP
,
> and Named Pipes enable. The server is in the AD domain. I use both Windows
> and SQL authentication with my sa account.
> I just created a maintenance plan in the Studio console so that the backup
> and reindex can run on the server db. However, the job failed last nite. I
> decide delete the plan and set up another one. I connected to the server b
y
> using the Studio console on itself and tried to remove the plan, but it
> failed. I clicked on the error (a link displayed in the Studio) said the
> following:
> #############
> Exception has been thrown by the target of an invocation. (mscorlib)
> Additional information:
> An error has occurred while establishing a connection to the server. When
> connecting to the SQL server 2005, this failure may be caused by the fact
> that under the default settings SQL server does not allow remote connectio
ns.
> (provide: Named Pipes Provide, error: 40 - Could not open a connection to
SQL
> Server)(Microsoft SQL server, Error:53)
> ##############
> I have made sure the remote connection (right click on the server object i
n
> the Studio thing) is enabled. As mentioend, I also made sure the named pip
es
> is enabled (\\.\pipe\sql\query).
> May you provide idea so that I can remove the plan successfully?
> Thank you!
> Bobson|||Dennis,
Great someone read my post Before telling my point of view... I would
like to ask if you do the following :
1.) Put the sql in the domain
2.) rename the server couple times as the task already created
3.) use different admin account to log on and config both sql and OS (I am
still thinking permission related)
I have no one to respond to me as I could not find any solution on the Net
(the closest one is to run some scripts and clean up registry). The problem
still remains. But I did a test by setting up a clean new server with the
SQL. And I cannot duplicate the problem! In the test I do not do anythings I
mentioned above...
I was about to submit an issue to MS... but the SQL admin finally said we
could ignore the issue...so I just seize my action.
May I get your person email so we can talk more about it? Mine is
ultrabobson@.hotmail.com
Thank you, and stay in touch.
Bobson
"Denis Desjardins" wrote:
[vbcol=seagreen]
> Were you able to fix your problem? I have the same issue but didn't found
> anything helpful yet.
> Thanks
> Denis Desjardins
> "Bobson" wrote:
>|||Bobson,
I send you an email on your hotmail address but didn't have any answer yet.
Here's what i mention in my email:
Yes I actually renamed the server, or more precisely the virtual server name
since I’m running on a cluster, after the maintenance plan was created. I
know that’s related, but I just want to be able to delete those problemati
c
plans and recreated them afterward. Any idea?
"Bobson" wrote:
[vbcol=seagreen]
> Dennis,
> Great someone read my post Before telling my point of view... I would
> like to ask if you do the following :
> 1.) Put the sql in the domain
> 2.) rename the server couple times as the task already created
> 3.) use different admin account to log on and config both sql and OS (I am
> still thinking permission related)
> I have no one to respond to me as I could not find any solution on the Net
> (the closest one is to run some scripts and clean up registry). The proble
m
> still remains. But I did a test by setting up a clean new server with the
> SQL. And I cannot duplicate the problem! In the test I do not do anythings
I
> mentioned above...
> I was about to submit an issue to MS... but the SQL admin finally said we
> could ignore the issue...so I just seize my action.
> May I get your person email so we can talk more about it? Mine is
> ultrabobson@.hotmail.com
> Thank you, and stay in touch.
> Bobson
>
> "Denis Desjardins" wrote:
>|||Hi Dennis,
I am sorry if I might overlook it... Please try again with my
ultrabobson@.yahoo.com (or hotmail.com)
So you have very similar issue as what we did. We did not have any
reolsutions yet...even though we renamed the server back to the original
name. But it still could not resovle the issue. What we ran around was to
crate another plan.
I have couple of technet tickets and I might try to submit the issue to
them. I may not do this tsoon, but I will keep you posted once I do that.
Stay in touch.
Bobson
"Denis Desjardins" wrote:
[vbcol=seagreen]
> Bobson,
> I send you an email on your hotmail address but didn't have any answer yet
.
> Here's what i mention in my email:
> Yes I actually renamed the server, or more precisely the virtual server na
me
> since I’m running on a cluster, after the maintenance plan was created.
I
> know that’s related, but I just want to be able to delete those problema
tic
> plans and recreated them afterward. Any idea?
>
> "Bobson" wrote:
>