RDA Pull From Windows Server 2003 Gives Native Error 28035
Mar 28, 2006
I currently have a Vs.Net 2003 Pocket PC application that uses sql server ce 2.0 to push and pull data from Sql Server 2000 to the Pocket PC. The sscesa20.dll isapi agent is installed on a Windows 2000 server and points to another server that hosts the SQL database. In this configuration everything works like a charm. I am in the process of upgrading my application server to Windows 2003 Server but the RDA PULL process does not work, giving an Native Error of 28035 EVERY time. I use the exact same code in the app but when I point to the isapi agent on the 2003 box it does not work. When I connect to the the sscesa20.dll via the Pocket IE it returns the "Sql Server CE Server Agent" message. When I do an RDA.Submit it works and the SQL table is updated as expected.
I have configured IIS 6 with the proper web extensions
I have turned off the firewall and antivirus on the server.
I have reinstalled the server agent several times.
I set up the sscesa20.dll manually.
I removed all file level security.
I opened up the virtual directory.
I verified the ddl versions match.
I'm dead in the water right now. I'm not sure what else to try.
Any help would be greatly appreciated.
View 5 Replies
ADVERTISEMENT
Oct 12, 2006
RDA - vb 2005 app - desktop & pocket pc emulator - error: 80072F76 native error: 28035
PDA info:
.NET CF 1.0 env-string...
MS SQL client
MS SQLCE 2.0 dev
MS SQLCE 2.0
DESKTOP info:
Microsoft SQL Server Management Studio Express 9.00.2047.00
Microsoft Data Access Components (MDAC) 2000.085.1117.00
(xpsp_sp2_rtm.040803-2158)
Microsoft MSXML 2.6 3.0 6.0
Microsoft Internet Explorer 6.0.2900.2180
Microsoft .NET Framework 2.0.50727.42
Operating System 5.1.2600
copied an app from http://www.codeproject.com/netcf/PocketPCwithSQLCE/PocketPCwithSQLCE_Src.zip
modified its CONFIG.XML to...
<?xml version="1.0" encoding="utf-8" ?>
<Configuration>
<DatabaseServer>192.168.1.89</DatabaseServer>
<DatabaseName>D1Temp</DatabaseName>
<DatabaseLogin>sa</DatabaseLogin>
<DatabasePassword></DatabasePassword>
<SQLCEURL>http://192.168.1.89/SqlMobile/sqlcesa30.dll</SQLCEURL>
<LocalDBConnect>Provider=Microsoft.SQLServer.OLEDB.CE.2.0; Data Source=My DocumentsMyFav.sdf;</LocalDBConnect>
<LocalDBLocation>My Documents</LocalDBLocation>
<LocalDBName>MyFav.sdf</LocalDBName>
<IISLogin>192.168.1.89/Jason</IISLogin>
<IISPassword>batman2005</IISPassword>
</Configuration>
error is "Header information is either corrupted or missing. [,,, header name,,]"
have spent weeks google-ing trying to get this to work, to no avail.
Has ANYONE got RDA PULL to work with above setups?
View 1 Replies
View Related
Feb 29, 2008
I get and error when installing MS SQL 2005 on Windows 2003 server with SP2. It bombs at the very end of the install and Microsoft notification program generated he message below to be sent to Microsoft. Please help. At a stand still.
-------------------------------------------------------------------------------------------------------------------
EventType : sql90setup P1 : unknown P2 : 0x645 P3 : unknown
P4 : 0x645 P5 : unknown P6 : unknown P7 : sqlserver2005_bc.msi@
Below is the summary.txt
-------------------------------------
Microsoft SQL Server 2005 9.00.1399.06
==============================
OS Version : Microsoft Windows Server 2003 family, Standard Edition Service Pack 2 (Build 3790)
Time : Thu Feb 28 22:52:28 2008
Machine : ESAPPS
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_SQLSupport_1.log
--------------------------------------------------------------------------------
Machine : ESAPPS
Product : Microsoft SQL Server Native Client
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_SQLNCLI_1.log
--------------------------------------------------------------------------------
Machine : ESAPPS
Product : Microsoft Office 2003 Web Components
Product Version : 11.0.6558.0
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_OWC11_1.log
--------------------------------------------------------------------------------
Machine : ESAPPS
Product : MSXML 6.0 Parser
Product Version : 6.00.3883.8
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_MSXML6_1.log
--------------------------------------------------------------------------------
Machine : ESAPPS
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_SQLSupport_2.log
--------------------------------------------------------------------------------
Machine : ESAPPS
Product : Microsoft SQL Server Native Client
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_SQLNCLI_2.log
--------------------------------------------------------------------------------
Machine : ESAPPS
Product : Microsoft Office 2003 Web Components
Product Version : 11.0.6558.0
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_OWC11_2.log
--------------------------------------------------------------------------------
Machine : ESAPPS
Product : Microsoft SQL Server VSS Writer
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_SqlWriter_1.log
--------------------------------------------------------------------------------
Machine : ESAPPS
Product : MSXML 6.0 Parser
Product Version : 6.00.3883.8
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_MSXML6_2.log
--------------------------------------------------------------------------------
Machine : ESAPPS
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_SQLSupport_3.log
--------------------------------------------------------------------------------
Machine : ESAPPS
Product : Microsoft SQL Server Native Client
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_SQLNCLI_3.log
--------------------------------------------------------------------------------
Machine : ESAPPS
Product : Microsoft Office 2003 Web Components
Product Version : 11.0.6558.0
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_OWC11_3.log
--------------------------------------------------------------------------------
Machine : ESAPPS
Product : Microsoft SQL Server 2005 Books Online (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_BOL_1.log
--------------------------------------------------------------------------------
Machine : ESAPPS
Product : MSXML 6.0 Parser
Product Version : 6.00.3883.8
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_MSXML6_3.log
--------------------------------------------------------------------------------
Machine : ESAPPS
Product : SQLXML4
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_SQLXML4_1.log
--------------------------------------------------------------------------------
SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%Microsoft SQL Server90Setup BootstrapLOGSummary.txt.
Time : Thu Feb 28 23:01:11 2008
List of log files:
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_Core(Local).log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_SQLSupport_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_SQLNCLI_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_OWC11_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_BackwardsCompat_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_MSXML6_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_SQLSupport_2.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_SQLNCLI_2.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_OWC11_2.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_SqlWriter_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_MSXML6_2.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_SQLSupport_3.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_SQLNCLI_3.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_OWC11_3.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_BOL_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_MSXML6_3.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_SQLXML4_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_Datastore.xml
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_.NET Framework 2.0.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_Core.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGSummary.txt
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_.NET Framework 2.0 LangPack.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_.NET Framework Upgrade Advisor.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_.NET Framework Upgrade Advisor LangPack.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_.NET Framework Windows Installer.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_.NET Framework Windows Installer LangPack.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_Support.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_SCC.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_WI.log
View 2 Replies
View Related
Jun 17, 2005
I have a windows 2003 server with the latest service pack and patches. This server also acts a domain controller.
View 4 Replies
View Related
Mar 29, 2007
I do a clean install of SQL Server + RS + SP1 with standard setup on Windows Server 2003. I create a simple report (select * from aTable). This report (actually any report) shows the error message "For security reasons DTD is prohibited in this XML document. To enable DTD processing set the ProhibitDtd property on XmlReaderSettings to false and pass the settings into XmlReader.Create method."
This has to do with security settings in Windows Server 2003. On Windows XP everything works fine.
Any help would be greatly appreciated. Thanks!
Edit: The reports do work in the preview tab in BIDS.
View 5 Replies
View Related
Dec 3, 2007
I am attempting to install SQL Server 2005 on a Laptop with Windows 2003 Standard Edition.
The installation fails and the File Summary.txt has the following entries:
Microsoft SQL Server 2005 9.00.1399.06
==============================
OS Version : Microsoft Windows Server 2003 family, Standard Edition Service Pack 2 (Build 3790)
Time : Fri Nov 30 09:36:53 2007
Machine : SAPDEMO
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_SQLSupport_1.log
--------------------------------------------------------------------------------
Machine : SAPDEMO
Product : Microsoft SQL Server Native Client
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_SQLNCLI_1.log
--------------------------------------------------------------------------------
Machine : SAPDEMO
Product : Microsoft SQL Server VSS Writer
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_SqlWriter_1.log
--------------------------------------------------------------------------------
Machine : SAPDEMO
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_SQLSupport_2.log
--------------------------------------------------------------------------------
Machine : SAPDEMO
Product : Microsoft SQL Server Native Client
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_SQLNCLI_2.log
--------------------------------------------------------------------------------
Machine : SAPDEMO
Product : Microsoft SQL Server 2005 Books Online (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_BOL_1.log
--------------------------------------------------------------------------------
Machine : SAPDEMO
Product : SQLXML4
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_SQLXML4_1.log
--------------------------------------------------------------------------------
SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%Microsoft SQL Server90Setup BootstrapLOGSummary.txt.
Time : Fri Nov 30 09:38:41 2007
List of log files:
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_Core(Local).log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_SQLSupport_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_SQLNCLI_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_SqlWriter_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_MSXML6_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_SQLSupport_2.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_SQLNCLI_2.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_BOL_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_SQLXML4_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_Datastore.xml
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_.NET Framework 2.0.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_Core.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGSummary.txt
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_.NET Framework 2.0 LangPack.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_.NET Framework Upgrade Advisor.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_.NET Framework Upgrade Advisor LangPack.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_.NET Framework Windows Installer.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_.NET Framework Windows Installer LangPack.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_SNAC.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_Support.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_SCC.log
The Log File, SQLSetup0004_<hostname>_Core.log, has the following entries:
Microsoft SQL Server 2005 Setup beginning at Mon Dec 03 08:54:09 2007
Process ID : 2980
C:SAP_CDCD2x86EnterpriseEditionServerssetup.exe Version: 2005.90.1399.0
Running: LoadResourcesAction at: 2007/11/3 8:54:9
Complete: LoadResourcesAction at: 2007/11/3 8:54:9, returned true
Running: ParseBootstrapOptionsAction at: 2007/11/3 8:54:9
Loaded DLL:C:SAP_CDCD2x86EnterpriseEditionServersxmlrw.dll Version:2.0.3604.0
Complete: ParseBootstrapOptionsAction at: 2007/11/3 8:54:9, returned true
Running: ValidateWinNTAction at: 2007/11/3 8:54:9
Complete: ValidateWinNTAction at: 2007/11/3 8:54:9, returned true
Running: ValidateMinOSAction at: 2007/11/3 8:54:9
Complete: ValidateMinOSAction at: 2007/11/3 8:54:9, returned true
Running: PerformSCCAction at: 2007/11/3 8:54:9
Complete: PerformSCCAction at: 2007/11/3 8:54:9, returned true
Running: ActivateLoggingAction at: 2007/11/3 8:54:9
Complete: ActivateLoggingAction at: 2007/11/3 8:54:9, returned true
Delay load of action "DetectPatchedBootstrapAction" returned nothing. No action will occur as a result.
Action "LaunchPatchedBootstrapAction" will be skipped due to the following restrictions:
Condition "EventCondition: __STP_LaunchPatchedBootstrap__2980" returned false.
Running: PerformSCCAction2 at: 2007/11/3 8:54:9
Loaded DLL:C:WINDOWSsystem32msi.dll Version:3.1.4000.4042
Loaded DLL:C:WINDOWSsystem32msi.dll Version:3.1.4000.4042
Complete: PerformSCCAction2 at: 2007/11/3 8:54:9, returned true
Running: PerformDotNetCheck at: 2007/11/3 8:54:9
Complete: PerformDotNetCheck at: 2007/11/3 8:54:9, returned true
Running: ComponentUpdateAction at: 2007/11/3 8:54:9
Complete: ComponentUpdateAction at: 2007/11/3 8:55:6, returned true
Running: DetectLocalBootstrapAction at: 2007/11/3 8:55:6
Complete: DetectLocalBootstrapAction at: 2007/11/3 8:55:6, returned true
Running: LaunchLocalBootstrapAction at: 2007/11/3 8:55:6
Error: Action "LaunchLocalBootstrapAction" threw an exception during execution. Error information reported during run:
"C:Program FilesMicrosoft SQL Server90Setup Bootstrapsetup.exe" finished and returned: 1605
Aborting queue processing as nested installer has completed
Message pump returning: 1605
Regards
View 1 Replies
View Related
May 23, 2007
hello folks
i have recently started to work with the analysis services and i am having some problems.
i have made a web application that for now just tries to connect to an analysis server.
The server is installed on an xp sp 2 system.
for testing, i used my local computer, which is running also win xp sp2. After deploying, the application can connect to the AS server on the other machine. the problem occurs when i try to deploy the applicatuion on the production server, which is running win 2k3 server on 32 bit. When deploying, i use the same connection string, so it should try to connect to the AS server installed on a win xp sp2 system.
The first thing that came to my mind was to check the MDAC versions, be cause of the message: "Provider cannot be found. It may not be properly installed."
on my computer, where the application worked ok, the version is MDAC 2.8 SP 1 Windows XP SP 2
on the win2k3 server, the MDAC version is : MDAC 2.8 SP2.... i thought it was the version of the service pack, so o searched for the update of MDAC 2.8 SP1, trying to install mdac 2.8 sp2 to see if i was to see the same error, but i found that mdac 2.8 sp2 is only for win2k3 server, and for win xp is mdac 2.8 sp1, according to this link: http://support.microsoft.com/default.aspx/kb/884103
Now i got confused and have no clues how to make this work...
Can anybody give any hint?
View 2 Replies
View Related
Jul 12, 2007
We just replaced an older Windows 2000 sp4 server with a new Window 2003 Standard Edition sp2 server to run our batch processing. We noticed that when the SQL command times out we now get the following error in the ADO command object error collection.
[DBNETLIB][ConnectionWrite (send()).] General network error. Check you network documentation.
Native Error: 11
SQL State: HY018
msado15.dll version 2.82.3959 is on this server.
On other servers running Windows 2003 Enterprise Edition sp1 the error on the ADO command object is normal with.
Timeout expired
Native Error: 0
SQL State: HYT00
msado15.dll version 2.82.1830 is on this server.
The SQL server they are talking to is on the other side of a firewall. It is SQL 2005 sp2 running on Windows 2000 sp4.
I have also tested this on a Windows 2003 sp2 server that doesn't have to cross a firewall and get the correct Timeout error. It also has the same version of msado15.dll as problem server.
The application is a collection of VB6 Components that are running in COM+ applications. I have isolated the test application to our one SQL interface component and have build a test vbs that can reproduce this on demand. The VB6 Components were not modified in any way for this change and have been working fine for many years prior to this.
All other aspects of our batch processing works as expected. Transactions are working fine. As long as the SQL doesn't timeout everything is normal. DTCPing was used to ensure both servers have correct ports open to allow DTC traffic. Checked the SynAttackProtect setting on SQL and this is not an issue since other clients have no problems.
One point I would like to add is that this new server was initially setup with a temporary server name and then was changed to use the name of the original server on move day. Don't know if this has any impact or not.
View 31 Replies
View Related
Jan 8, 2008
I am running a .Net application (VB.Net, .Net Framework 2.0) on a Windows CE 5.0 handheld device. I am relatively having good success with SQL CE replication, however sometimes (2 users out of 30 every 2 weeks), are freezing up in the application.
Here is what CE SQl software versions I installed:
sqlce30.dev.ENU.wce5.armv4i.CAB
sqlce30.repl.wce5.armv4i.CAB
sqlce30.wce5.armv4i.CAB
I have a trace log in my application, and here is what pops up before the hang (warm rebooting the handheld works)
NativeError: 28037
SQL Msg: A request to send data to the computer running IIS has failed. For more information, see HRESULT.
NativeError: 28600
SQL Msg: The database is currently synchronizing with the server.
I am using a Thread to syncronize (microsofts built in class), as you can see I am well aware of 28600, it just means some other thread is already syncing, so I can wait until next time to syncronize. However, my users apps are freezing just after both error codes occur. Anything in the code below causing issues??? (maybe _repl.Dispose() is freezing up my handheld, because its freezing after this line of code (see below code):
"MTM.SPUD.Utilities.Utilities.Log("[DEBUGQLThread#" + threadId + "]: End of Thread Life.")"
Public Sub AsyncSyncronize(ByRef PendingData As Boolean, ByVal Publication As String, ByVal Subscription As String, ByRef LastSyncDateTime As DateTime)
Dim _repl As New SqlCeReplication()
Try
...
savedAsyncResult = _repl.BeginSynchronize(objDelegate1, objDelegate2, objDelegate3, objDelegate4, _repl)
Catch ex As Exception
Finally
End Try
End Sub
Public Sub OnSynchronizeComplete(ByVal asyncResult As IAsyncResult)
Dim _repl As SqlCeReplication = Nothing
Dim threadId As String = ""
Try
_repl = DirectCast(asyncResult.AsyncState, SqlCeReplication)
threadId = _repl.InternetPassword
_repl.EndSynchronize(asyncResult)
dataIsPending = False
Catch exce As SqlCeException
_repl.CancelSynchronize()
MTM.SPUD.Utilities.Utilities.Log("[DEBUGQLThread#" + threadId + "]: SQLCE OnSynchronizeComplete() NativeError: " + exce.NativeError.ToString + "SQL Msg: " + exce.Message.ToString)
dataIsPending = True
If exce.NativeError.ToString = "28600" Then
MTM.SPUD.Utilities.Utilities.Log("[WARNINGQLThread#" + threadId + "]: Will try again next time")
Return
End If
Catch ex As Exception
Return
'MTM.SPUD.Utilities.Utilities.Log("App Exception: " + ex.Message)
'Throw New Exception("EndSynchronize Failed: " + ex.Message)
Finally
MTM.SPUD.Utilities.Utilities.Log("[DEBUGQLThread#" + threadId + "]: End of Thread Life.")
If _repl IsNot Nothing Then
_repl.Dispose()
_repl = Nothing
End If
End Try
End Sub
View 3 Replies
View Related
Jan 23, 2008
Hello, pls Some of my factory guys can log on the same user name at the same time, so I want a situation where a user name may be able to log on, one at a time. Whoever that is reading this, note this is not a misplacement, this is the fact that I don't have means of solving it, I am also of opinion that some have full knowledge of windows 2003 server
View 1 Replies
View Related
Apr 22, 2004
I have SQL 2k on a W2003 Server.
I have SP3 installed.
My problem is that i cant connect to the server via telnet:
"C:>telnet localhost 1433
Connecting to localhost...Could not open connection to the host, on port 1433: Connect failed."
I try telnet 127.0.0.1 also.
In the Server Network Utility TCP/IP is ENABLED and the port number is 1433.
Who can help me?
(Sorry for my english)
View 2 Replies
View Related
Nov 25, 2006
We have purchased Windows 2003 Small Business Edition Premium.
Our company uses Analysis Manager / Analysis Services and also MDX functions. However Release2 only appears to have SQL 2005 Workgroup edition with it and these features do not seem to be present.
Does anybody know how I upgrade to get these functions? I don’t know if these functions can be downloaded or whether we have to upgrade by purchasing SQL Server Standard 2005 edition outright?
Thanks, Stephen.
View 1 Replies
View Related
Jul 23, 2005
Hi,I am unable to connect to a database in my SQL 2000 Server installed ona Windows 2003 Server machine from an asp page. It gives the thefollowing error:Microsoft OLE DB Provider for SQL Server (0x80004005)Login failed for user 'sa'. Reason: Not associated with a trusted SQLServer connection.I also sometimes get:MSDataShape (0x80004005)Data provider could not be initialized.I can connect with the same connection string and parameters from avisual basic 6 application.I can also connect the web client with the same DB in SQL 2000 runningon Windows 2000/XP.The authentication mode is mixed.I believe it is something to do with security. Please advise me on whatto do. It is very urgent.
View 11 Replies
View Related
Oct 19, 2006
Hi,
I have a client requiring SQL 7.0 installed on Windows 2003 Server Std. Just wondering if its supported and possible to install SQL 97 on Windows 2003 servers.
Thanks
View 1 Replies
View Related
Oct 26, 2004
Hello y'all,
I have to do a new install of SERVER 2000 using WINDOWS 2003 . Has anyone done this. If so, what are the steps. Should I expect any problems ? Any help appreciated.
Thanx
View 1 Replies
View Related
Jan 15, 2004
I have been searching the net and haven't found anything that has worked so far for resolving this issue, hopefully someone on here can provide some insight?
I did a fresh install of a Windows 2003 Standard Edition server (as part of a workgroup, not a domain..the server is only temporary for testing) and installed MSDE 2000A (the version that contains all current service packs). I can use the MSDE server locally on the server without any issue...however when I try to connect to MSDE with a workstation, it tells me that Access is denied or the Server does not exist.
The ICF is disabled, and all passowrds being entered have been checked, however I still can not connect to the sql server. Does anyone have any ideas on this or run into this problem before?
View 2 Replies
View Related
Mar 7, 2008
Set up - windows server 2003 - SQL server 2000 + tools installed
Not sure why its happening but recently when running some scripts onto one of the databases held on the server windows crashes.
I say crashes - it is non responsive but the mouse cursor can be moved.
these scripts are not being run from the server but from one of many machines on our companies network.
Any suggestions would be great
View 1 Replies
View Related
Jul 23, 2005
I have XP workstations and windows 2003 SBS. I setup an ODBC for anapplication (tried both User and System DSN), but after a few usage, I getthe following error:Connection failed:SQLState: 'HY000'SQL Server Error: 0[Microsoft][ODBC SQL Server Driver]Cannot generate SSPI context.Any ideas? Is this a bug?--Thank youPlease post only
View 3 Replies
View Related
Jul 20, 2005
I have been searching the net and haven't found anything that hasworked so far for resolving this issue, hopefully someone on here canprovide some insight?I did a fresh install of a Windows 2003 Standard Edition server (aspart of a workgroup, not a domain..the server is only temporary fortesting) and installed MSDE 2000A (the version that contains allcurrent service packs). I can use the MSDE server locally on theserver without any issue...however when I try to connect to MSDE witha workstation, it tells me that Access is denied or the Server doesnot exist.The ICF is disabled, and all passowrds being entered have beenchecked, however I still can not connect to the sql server. Doesanyone have any ideas on this or run into this problem before?
View 1 Replies
View Related
Jan 18, 2008
I have a windows server 2003 R2 sharing a filesystem using NFS. I have created a group and passwd file and mapped the ids' to the unix login ids' . I', able to mount but when I try to cd to the directory I get "NFS access failed for server testsrvr: RPC: Authentication error". On the win2k3 server I'm getting an event error "There was a mapping failure". I have the Admin id on the win2k3 server mapped to the unix root login .
View 1 Replies
View Related
Jul 13, 2007
At first I thought it was just me, but has anyone else noticed that SQL 2005 suffers a performance hit when you install Windows Server 2003 SP2?
Since SP2, memory and hard drive usage has gone through the roof on a number of servers I use. It may just be coincidence... but it seems unlikely.
View 6 Replies
View Related
Nov 12, 2006
I am following the MCTS Self-Paced Training Kit for Exam 70-431 (implementation and maintenance of sql server 2005) and one of the prerequisites is that I have Microsoft Windows Server 2003 running on my computer on an NTFS file system (NTFS) partition. Now am I right in thinking Windows Server 2003 is an operating system. If it is can I install it alongside XP Professional which I am currently running. I am currently afraid to go ahead with the installation as I am worried it will overwrite XP, which would be disastrous as I have a great deal of data on it.
Thanks
vik
View 4 Replies
View Related
Nov 13, 2007
I have a problem i have been working on moving sql2000 databases to 2005.
I have two servers running on one machine.
Is there a way to make my 2005 server a default server
I want to make 2005 a default server instead of 2000.
Because in my connection string from the applications i connect to server using external ip & it's connecting to 2000 instead of 2005.
How can i solve this problem
let me know
thanks
View 7 Replies
View Related
Apr 2, 2007
I have SQL Server 2000 running on Windows 2003 Server. I have Windows 2000 Server running IIS. I am trying to connect my asp running on 2000 to my SQL Server running on 2003, but I run into the problem when I have to machines connecting to the database. The first machine works, but the second machine comes up with the page is not found. When the first machine is done with getting the data, I am able to refresh on the second machine and it works. Some reason it is only allowing one connection at a time on the same database. Any help would be greatly appreciated. Thanks
View 2 Replies
View Related
May 6, 2005
Wondering if there is a different way to setup mail because of Windows Server 2003 instead of Windows Server 2000? The server I'm being asked to get mail working on will have an exchange email account and I'm not familiar with setting this up. On my 2000 machine I had to use Outlook 2000 with option for Corporate or Workgroup an a POP email account. Any help is appreciated.
View 2 Replies
View Related
Jul 14, 2004
I am going to start installing sql server soon, do I have to have IIS installed? Is it a requirement?
Thanks.
View 2 Replies
View Related
Oct 27, 2004
anyone has tried? please advice possible issues, workarounds
tks
View 1 Replies
View Related
Dec 8, 2005
Hi,
I've noticed declining performance on our main accounting server. We have a Windows 2003 server running SQL 2000 Enterprise and 8 GBs of RAM.
Has anyone used the "boost SQL Server priority on windows" before? If so, were there any major benefits in using it?
This server is excusively used for SQL btw...
Thanks,
DJ
View 3 Replies
View Related
May 19, 2008
Hi all,
I have SQL server 2005 enterprise edition on windows server 2003 machine. when i took the back of the database from this sytem and try to restore the backup on SQL server 2005 R2 enterprise edition on client machine. it is giving me following error
"
Restore failed for Server '10.112.12.229'. (Microsoft.SqlServer.Smo)
ADDITIONAL INFORMATION:
System.Data.SqlClient.SqlError: The operating system returned the error '5(Access is denied.)' while attempting 'RestoreContainer::ValidateTargetForCreation' on 'c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLFX_Global_backup_200805141500.mdf'. (Microsoft.SqlServer.Smo)
"
Please tell what is the error about?
Can it be possible to restore a back up of different operating system machine to other ?
View 5 Replies
View Related
Oct 2, 2007
Hi there,
We've got a Windows 2003 (64 bit edition) box to use as our Database server.
I installed SQL Server 2005 (Standard Edition) on the machine, but I have a feeling it has installed the 32 bit version and not the 64 bit version.
The reason I think this is that the MSSQL directory is under the 32 bit program files directory and not the 64 bit directory, and also when I look at the service properties it says it's running from WOW6432 registry entry.
Is there a separate disc for the 64bit version? Does the installer automatically work out which version to install or is there some sort of switch I have to do to tell it to install the 64 bit version.
Many thanks for your time.
Simon
View 3 Replies
View Related
Jul 27, 2005
Hi,I tried to Develop one Report in SQL Reporting Service. I haveinstalled SQL Reporting Serivice in Windows 2003 machine. SQL ServerDatabase is in another machine, running on Windows 2000. I developedand deployed the report and all went fine.When I tried to see the report through the Report Service Manager WebPage it is comming properly. But When I tried to See the report inanother web page, I'm not able to see the images. But the Data isgetting Displayed and only Image is not comming. When I exported thereport to Excel, the Image is comming over there.I am using Report Viewer control (Which came as Sample Program) inthe ASPX Page to render the report. I'm using SQL Server 2000 with SP3aand SQL Server 2000 reporting Service with SP1.I tried setting the Mime Time for the GIF image and even "*.*" inthe Mime Type settings of IIS 6.0. Even then its not displaying theimage.Can any one help me out in solving the problem?Thanks in Advance.With RegdsKrish
View 1 Replies
View Related
Jan 28, 2008
Does SQL Server 2000 CE 2.0 work on Windows Mobile 2003?
Thank you,
Ken Carlino
ServiceMaster
View 6 Replies
View Related
Oct 18, 2007
I've got a Windows Server 2003 for Small Business Server. It had got SQL installed. But then SQL was uninstalled. Now I need to put SQL back in, but I don't see how!
There're three CD-Rom but I don't see how and from which CD to install back SQL.
PS: Correct me if I'm wrong, Windows Server 2003 is sold with SQL 2005, right?
View 3 Replies
View Related
