OWC not working on windows server 2008

Hi,
I am moving from Windows 2003 to windows 2008 server.
OWC components are working fine for my applications in windows 2003 where it is failing in windows 2008.
we are getting Authentication issues in the application.
Application is asking for windows login credentials after navigating few screens.
Its failing even after giving credentials also.
Can some one please help us on this.

Hello Girish,
OWC is not supported any longer. See Office Web Components “Roadmap” and
Description of the versions and support for Office Web Components (OWC) for more information.
You may find the
Replacing OWC Reporting with Excel Services article helpful.

Similar Messages

Web Service Client(Console App) not working on Windows Server 2008 R2 Standard Edition

I am trying to consume an ASMX Web Service in a console app, its working fine in Windows 7,Windows Server 2012 Standard,Windows Server 2008 R2 DataCenter,Windows Server 2008 R2 Enterprise, But its not working in Windows Server 2008 R2 Standard Edition which
is the deployment server.
I tried consuming the ASMX web service using Web Reference and Service Reference as well but its not helping. Its throwing up the following error,
Message:There is an error in XML document (1, 331491).
Inner Exception : System.Xml.XmlException: '.', hexadecimal value 0x00, is an invalid character. Line 1, position 331491.
The scenario is that i call the web service and it returns me an XML i am not able to receive the XML on Windows Server 2008 R2 Standard Edition.
Please provide suggestions on this I need to resolve this ASAP.

Hi,
This question is better asked here:
http://social.msdn.microsoft.com/Forums/en-US/home?forum=asmxandxml
Experts here are more familiar about it and they can give you more efficient suggestion.
Thank you.

Addon not working on Windows Server 2008 OS

Dear Friends,
I have developed an addon in XP and its working fine with XP operating system but it is not working on Windows Server 2008 Standard. Error is "An Attempt was made to load a program with an incorrect format.(Exception from HRESULT: 0x8007000B)".
Regards,
Mahesh.
Edited by: mahesh A on Sep 19, 2009 9:26 AM

Hi,
Since only Windows 2008 SBS is supported with SAP Business One and that Server is available for 64bit Hardware as defined by Microsoft, I guess you should look into that direction.
Regards
Mario

Group Chat feature in Office Communications Server 2007 R2 does not work in Windows Server 2008 R2 domains

   Hello to all, there are two confliting articles about this topic:
   1-
http://technet.microsoft.com/en-us/library/upgrade-domain-controllers-to-windows-server-2008-r2(v=ws.10).aspx#BKMK_Whatsnew : this one says that it does not work "The Group Chat feature in Office Communications Server 2007 R2 does not work in Windows
Server 2008 R2 domains". This article was updated in 2013.
   2-
http://technet.microsoft.com/en-us/library/ee692314(office.13).aspx: this other article says that it will function "Office Communications Server 2007 R2 Group Chat will function in a Windows Server 2008 R2 forest". This article was updated in
2010 and was refered by the first one.
   What is the correct support position for Group Chat feature in Office Communications Server 2007 R2 and Windows Server 2008 R2 domains?
   Regards, EEOC.

Hi,
I notice the following sentence in the link below “Office Communications Server 2007 R2, Group Chat will not function in a Windows Server 2008 R2 forest or when Group Chat member servers are joined to a Windows Server 2008 R2 domain.
We know of an issue with changes in Windows 2008 R2 that requires a Group Chat Client and Group Chat Admin Tools hotfix. The Group Chat Client and Group Chat Admin Tools hotfixes are currently scheduled for mid-April 2010.”
http://blogs.technet.com/b/nexthop/archive/2010/11/06/supportability-for-office-communications-server-2007-r2-and-windows-server-2008-r2.aspx
So in my opinion, if you update to the latest version of Windows Server 2008 R2, OCS Server 2007 R2 and Group Chat Client, Group Chat Admin Tools to the latest version, it should work.
However, the best method for you is make a lab to test the problem firstly.
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

BMR/Systemstate backup not working on windows server 2008 error 2147942487

Hi, trying to backup system image using SCDPM 2010 RTM.Most of the server are getting healthy backups except for this one server which is giving error:
Affected area: Computer\System Protection
Occurred since: 1/27/2014 2:43:27 PM
Description: The replica of System Protection Computer\System Protection on server.DOMAIN.COM is inconsistent with the protected data source. All protection activities for data source will fail until the replica is synchronized with consistency check. You can recover data from existing recovery points, but new recovery points cannot be created until the replica is consistent.
For SharePoint farm, recovery points will continue getting created with the databases that are consistent. To backup inconsistent databases, run a consistency check on the farm. (ID 3106)
DPM cannot create a backup because Windows Server Backup (WSB) on the protected computer encountered an error (WSB Event ID: 517, WSB Error Code: 0x80070057). (ID 30229 Details: Internal error code: 0x809909FB)
More information
Recommended action: For resolution actions and more information on the WSB error, go to http://technet.microsoft.com/en-us/library/cc734488(WS.10).aspx.
Synchronize with consistency check.
Run a synchronization job with consistency check...
Resolution: To dismiss the alert, click below
Inactivate alert
On the server, event viewer show the following events:
1. Backup Log:
Backup started at '2014-01-27T11:26:21.356950100Z' failed with following error code '2147942487'.
2. Application Log:
The description for Event ID 517 from source Microsoft-Windows-Backup cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
27-Jan-14 11:26:21 AM
2147942487
%%2147942487
The resource loader failed to find MUI file
However, when I observe the backup process using "wbadmin get status", it reaches 99% then stops.
Running backup of volume Local Disk(C:), copied (97%).
Running backup of volume Local Disk(C:), copied (98%).
Running backup of volume Local Disk(C:), copied (99%).
Backup stopped before completing.
Summary of backup:
Backup stopped before completing.
The parameter is incorrect.
The server hardware is HP blade with two disk which are mirrored, and has 12 GB free space. below is the output from systeminfo command:
Host Name: server
OS Name: Microsoftr Windows Serverr 2008 Enterprise
OS Version: 6.0.6002 Service Pack 2 Build 6002
OS Manufacturer: Microsoft Corporation
OS Configuration: Member Server
OS Build Type: Multiprocessor Free
Registered Owner: Admin
Registered Organization: -
Product ID: 55041-339-7818202-76771
Original Install Date: 04-Aug-08, 3:15:18 PM
System Boot Time: 21-Jan-14, 3:58:47 PM
System Manufacturer: HP
System Model: ProLiant BL460c G1
System Type: x64-based PC
Processor(s): 2 Processor(s) Installed.
[01]: Intel64 Family 6 Model 23 Stepping 6 GenuineIntel ~3000 Mhz
[02]: Intel64 Family 6 Model 23 Stepping 6 GenuineIntel ~3000 Mhz
BIOS Version: HP I15, 02-May-11
Windows Directory: C:\Windows
System Directory: C:\Windows\system32
Boot Device: \Device\HarddiskVolume1
System Locale: en-us;English (United States)
Input Locale: en-us;English (United States)
Time Zone: (GMT+03:00) Kuwait, Riyadh
Total Physical Memory: 16,381 MB
Available Physical Memory: 8,320 MB
Virtual Memory: Max Size: 21,821 MB
Virtual Memory: Available: 13,722 MB
Virtual Memory: In Use: 8,099 MB
Page File Location(s): C:\pagefile.sys
Domain: DOMAIN.COM
Logon Server: N/A
Hotfix(s): 157 Hotfix(s) Installed.
[01]: {47740627-D81D-4A45-A215-03B075A18EC7}
[02]: {3D019598-7B59-447A-80AE-815B703B84FF}
[03]: {A8E86480-A9C1-4414-8AA2-B05A485C82F0}
[04]: {C444285D-5E4F-48A4-91DD-47AAAA68E92D}
[05]: {DB33A524-845E-4855-9E90-A5619BCDD527}
[06]: {ECC3A660-90E3-4A89-9FE8-F8B3C633B12E}
[07]: {65AFCB03-3111-47E2-B1ED-198D6B0BC96E}
[08]: {F5E29D9D-519A-36C7-87E3-9A22A8180B1B}
[09]: KB971513
[10]: KB971512
[11]: 944036
[12]: 982861
[13]: KB960362
[14]: KB2079403
[15]: KB2117917
[16]: KB2141007
[17]: KB2160329
[18]: KB2183461
[19]: KB2207566
[20]: KB2286198
[21]: KB2296011
[22]: KB2296199
[23]: KB2305420
[24]: KB2345886
[25]: KB2347290
[26]: KB2387149
[27]: KB2388210
[28]: KB2416400
[29]: KB2416470
[30]: KB2419640
[31]: KB2423089
[32]: KB2436673
[33]: KB2442962
[34]: KB2443685
[35]: KB2447568
[36]: KB2467659
[37]: KB938464
[38]: KB942288
[39]: KB948609
[40]: KB948610
[41]: KB949189
[42]: KB950762
[43]: KB950974
[44]: KB951066
[45]: KB951698
[46]: KB951978
[47]: KB952004
[48]: KB952287
[49]: KB953733
[50]: KB954155
[51]: KB954459
[52]: KB955020
[53]: KB955069
[54]: KB955302
[55]: KB955430
[56]: KB955839
[57]: KB956250
[58]: KB956572
[59]: KB956744
[60]: KB956802
[61]: KB957097
[62]: KB957200
[63]: KB957321
[64]: KB957388
[65]: KB958481
[66]: KB958483
[67]: KB958623
[68]: KB958624
[69]: KB958644
[70]: KB958687
[71]: KB959130
[72]: KB959426
[73]: KB960225
[74]: KB960803
[75]: KB961371
[76]: KB961501
[77]: KB967190
[78]: KB967723
[79]: KB968389
[80]: KB968537
[81]: KB969058
[82]: KB969897
[83]: KB969897
[84]: KB969947
[85]: KB970238
[86]: KB970430
[87]: KB970653
[88]: KB971468
[89]: KB971486
[90]: KB971557
[91]: KB971657
[92]: KB971737
[93]: KB971930
[94]: KB971961
[95]: KB972036
[96]: KB972270
[97]: KB972636
[98]: KB973346
[99]: KB973507
[100]: KB973525
[101]: KB973565
[102]: KB973687
[103]: KB973917
[104]: KB974145
[105]: KB974318
[106]: KB974455
[107]: KB974470
[108]: KB974571
[109]: KB975364
[110]: KB975467
[111]: KB975517
[112]: KB975560
[113]: KB975759
[114]: KB975929
[115]: KB976098
[116]: KB976264
[117]: KB976470
[118]: KB976662
[119]: KB976749
[120]: KB976768
[121]: KB976772
[122]: KB977165
[123]: KB978251
[124]: KB978262
[125]: KB978542
[126]: KB978601
[127]: KB978886
[128]: KB979099
[129]: KB979306
[130]: KB979309
[131]: KB979482
[132]: KB979687
[133]: KB979688
[134]: KB979899
[135]: KB979910
[136]: KB980182
[137]: KB980195
[138]: KB980218
[139]: KB980232
[140]: KB980248
[141]: KB980302
[142]: KB980436
[143]: KB980842
[144]: KB981322
[145]: KB981332
[146]: KB981793
[147]: KB981852
[148]: KB982132
[149]: KB982214
[150]: KB982519
[151]: KB982664
[152]: KB982666
[153]: KB982799
[154]: KB983589
[155]: KB948465
[156]: KB960568
[157]: KB968930
Network Card(s): 1 NIC(s) Installed.
[01]: HP NC373i Multifunction Gigabit Server Adapter
Connection Name: Local Area Connection 2
DHCP Enabled: No
IP address(es)
[01]: x.x.x.x
[02]: fe80::f494:43c2:7d90:e774
Hyper-V Requirements: VM Monitor Mode Extensions: No
Virtualization Enabled In Firmware: No
Second Level Address Translation: No
Data Execution Prevention Available: No
Things I have tried:
1. I tried to backup manually to external HDD using wsb snap-in, but it has failed in the same way.
2. Stop and re-add protection.
3. I have researched the error, some results suggest that some bad sectors might exist, however, when I run the command, it forces me to schedule the command on next boot. when I reboot, it loads windows after that gives a message "Cannot open the volume
for direct access"
How to end this loop? please help. Thanks for considering my question ...

Hello Ebttikar,
Please try clean boot then test how the issue goes. Following are the detailed steps about clean boot:
Log on to the computer by using an account that has administrator rights.
Click Start, type msconfig.exe in the Start Search box, and then press ENTER to start the System Configuration Utility.
On the General tab, click Selective Startup, and then click to clear the Load startup items check box. (The Use Original Boot.ini check box is unavailable.)
On the Services tab, click to select the Hide all Microsoft services check box, and then click Disable all.
Click OK, Choose Don’t show this message again and then click Restart.
Please check if RDP session issue is still the same.
Please let me know the result.
Best regards,
Sophia Sun
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Problem Windows 8 logon script not working from windows server 2008 R2

hi there , this is third post regard this problem, here is my problem goes .....
Is a very simple logon script for mapping drive purpose .... PLS take note Domain users can access and run this script for domain users using windows XP / WINDOWS VISTA / WINDOSWS 7 and only users " WINDOWS 8.1 " Does NOT run
at all . the script I put on logon script in Windows server 2008R2 group policy ...
@jrv :- http://social.technet.microsoft.com/profile/jrv/?ws=usercard-mini , insist said is my group policy setup problem so I post here agn...
Manually run the script on WINDOWS 8.1 is 100 % perfect so it is definitely not my logon script issue , PLS any guidance pls share for me ok ?? thanks
Below is my script syntax ;-
@echo off
REM Login.bat Version 1.0
REM Exit if user has logged on to the Server
IF %COMPUTERNAME%.==SL2011. GOTO END
REM Delete pre-existing drive mappings
REM
REM Map M: to SL2011 on sl2011
NET USE M: /DELETE >nul
NET USE M: \\SL2011\sl2011 /YES >nul
REM
REM Map Y: to AccScan on rss2
NET USE Y: /DELETE >nul
NET USE Y: \\rss2\Public\AccScan /YES >nul
REM

Hi Tee Ee Foong,
According to your post, the gpresult showed the GPO was applied and the script could run successfullymanully in the client. Right? Please follow the following step to narrow down
the issue:
1. Change the script to the following command: add
> %SystemDrive%\Users\test.txt to the script.
2. Log on to a client with a regular user account, run gpupdate/force, and then re-log on to this client.
3. Check if the test.txtfile exists in this location %SystemDrive%\Users.
If the test.txtfile exists, the GPO with logon script is applied successfully when user logs on. But the result of running logon script achieves the goal we excepted or not which
is still not sure.
Regards,
Lany Zhang

GPP Delete policy not working on Windows Server 2008 R2 RDS when deleting shared printers with status access denied.

Hi!
I Have one AD Security group for each shared printer, I have one GPP that map the printer if the user is in the security group that belong to the printer. And one GPP to delete the printer if the user is NOT member of the security group. The security group
is also applied in “Security” tab on the printsrv with PRINT rights and “everyone” is removed. This works 100 % on Windows 7 clients and Windows 2003 Terminal Servers. But on Windows 2008 R2 RDS this dont work.The Delete Policy will not delete the shared
printer. No warning in any logs, and the gpresult shows that the gpo setting applyed sucessfully. The only way I can make the Delete policy work is if i give the user print rights on the printer on the printsrv. Looks like for the policy to work on 2008
R2 the user must have print rights on the printer object on the printserver. The GPP Delete Policy will not delete printers that have status : access denied. Anyone else had this problem?

Hi,
Based on your description, it seems that we need to give users appropriate permissions, for the error
Access is denied is more or less related to permissions.
However, we can avoid deploying the GPP printer delete policy. As far as I know, we can use Item-Lvel Targeting of GPP to push the shared printers
to the targeted users or groups.
Regarding ILT, the following articles can be referred to for more information.
Preference Item-Level Targeting
http://technet.microsoft.com/en-us/library/cc733022.aspx
Security Group Targeting
http://technet.microsoft.com/en-us/library/cc772471.aspx
Best regards,
Frank Shen

Bluetooth Driver does not install or work on Windows Server 2008 R2

Bluetooth is the only hardware device on my T500 which is not working in Windows Server 2008 R2. Even leveraging the Bluetooth stack copied over from Win7 it is not possible to use the Broadcom BT on the PC.

Very good. According to the version number, you are on the original release of CR XI R2. This release did not support WIN 2008 Server. You will have to update the development computer to SP 6. SP 6 is here:
https://smpdl.sap-ag.de/~sapidp/012002523100015859952009E/crxir2win_sp6.exe
Recompile the app. Uninstall the runtime from the client box. Create a new deployment project using the SP 6 runtime.
MSI:
https://smpdl.sap-ag.de/~sapidp/012002523100000633302010E/crxir2sp6_net_si.zip
MSM:
https://smpdl.sap-ag.de/~sapidp/012002523100000634042010E/crxir2sp6_net_mm.zip
Install the above runtime on the client computer. Run.
Oh, and keep your fingers crossed...
- Ludek

Hp deskjet 2545 printer driver not supporting on windows server 2008 r2

I have purchased a 3 in 1 hp deskjet 2545 printer. I am trying to configure in on my home laptop (HCL) operating system: windows server 2008 R2, but unable to configure it. customer support executive told me hp deskjet 2545 printer driver is not compatible on windows server 2008 R2. but I have checked in my office and it is working fine on my office 2008 server. Please help.

Hello Arvindk,
Welcome to the HP Support Forums! I understand you are trying to use your HP Deskjet 2545 with your Windows Server 2008 R2. Because you are using a server your question will be best answered on the Commercial Forums: http://h30499.www3.hp.com/hpeb/
I was able to find this document for Installing the Printer Software on Windows Server 2003 or 2008, which may be helpful for you.
Thanks,
HevnLgh
I work on behalf of HP
Please click “Accept as Solution” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos Thumbs Up" to the left of the reply button to say “Thanks” for helping!

Hard drive not recognized during windows server 2008 setup

hard drive not recognized during windows server 2008 setup

Hi,
Whether the hard disk is recognized in BIOS?
Connect it to another computer to see if it could be recognzied incase the cause is the disk itself. Also please check if it is really a RAID instead of a single hard disk - a single disk should be recognized directly while RAID cannot be recognized until
a suitable driver is installed.
Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Does the lnkfix_vista.zip work for window server 2008 R2 enterprise ?

All icons on my exchange 2010 server show as .lnk, any icon I click on starts notepad... does the lnkfix_vista.zip work on Windows server 2008 R2 enterprise ?
thank you.

This issue because there is no SPN for the Front End pool FQDN. Rather than adding an SPN I just deleted my front end server from the topology builder and added a new one using the FQDN of the actual lync server and it worked fine.
Also you can refer below link
http://howexchangeworks.com/2013/07/creating-central-management-store-fails-while-publishing-lync-2013-topology.html
Please remember, if you see a post that helped you please click (Vote As Helpful" and if it answered your question, please click (Mark As Answer).

Get-Hotfix InstalledOn property not returning hotfix installed Date and Time on Windows Server 2008 SP2 but works on Windows Server 2008 R2 SP1

Hi,
I am working on a validation script to get the list of hotfixes installed on Domain Controllers every month as part of our monthly DC patching process. I have been successful in getting these details for DC's with (Windows Server 2008
R2 SP1, Powershell v2.0) using the below command.
Get-HotFix -cn $computer | Select-Object PSComputerName,HotFixID,Description,InstalledBy,InstalledOn | where InstalledOn -ge (Get-Date -Day 1 -Format d) | FT -AutoSize
I execute the above from a jump box with powershell v4.0 (Server 2008 R2)
However, when I try the same command from the jump box to query DC's with (Server 2008 SP2, powershell v2.0). It doesn't return the InstalledOn date and time. It was giving error for the InstalledOn property and hence I renamed it to $_.InstalledOn. Now
I don't get error but still no details displayed for InstalledOn property.
I tried using the below, as could see on few forums that this might resolve the issue. I also tried removing the "where" part but still no installation date returned.
Get-HotFix -cn $computer | Select-Object HotFixID, Description, InstalledBy, @{l="InstalledOn";e={[DateTime]::Parse($_.psbase.properties["installedon"].value,$([System.Globalization.CultureInfo]::GetCultureInfo("en-US")))}}
| where {$_.InstalledOn -ge (Get-Date -Day 1 -Format d)} | FT -AutoSize
Have tried this locally on the 2008 SP2 DC but still not working. Please advise what is going wrong?
Note: If I execute the below command locally on the 2008 SP2 DC, I am getting the InstalledOn output. However, when executed from the jump box with powershell v4.0 (Server 2008 R2) to query
the same 2008 SP2 DC, it just gives the prompt again without any error or output. This behavior is consistent for other 2008 SP2 DC's in the environment.
Get-HotFix -cn $computer | Select-Object HotfixID,Description,InstalledBy,InstalledOn | where {$_.InstalledOn -ge (Get-Date -Day 1 -Format d)} | FT -AutoSize

Hi jrv, I have already tried the Win32_QuickFixEngineering option, which doesn't work either. Apologies for not mentioning the workarounds that I have already tried.
Get-Hotfix seems to be just a wrapper for Win32_QuickFixEngineering as per the below article. (http://technet.microsoft.com/en-us/library/hh849836.aspx)
I have seen a mention of using the WU ActiveX control on few forums, but was too lazy to read it through.
After rigorous testing, it makes me realize that somewhere the Get-Hotfix dates formatting\comparison isn't working.

Distributed transaction using linked server not working in SQL Server 2008 64 bit

Hi. I have had an issue trying to get distributed transactions to work in SQL Server 2008 using a linked server. The error message I get is
OLE DB provider "SQLNCLI10" for linked server "pod1" returned message "No transaction is active.".
Msg 7391, Level 16, State 2, Line 3
The operation could not be performed because OLE DB provider "SQLNCLI10" for linked server "pod1" was unable to begin a distributed transaction.
My Environment:
Windows Server 2008 Enterprise 64 bit, SQL Server 2008 Enterprise 64 bit
Problem occurs with multiple different builds of SQL Server 2008 - I have been able to reproduce the problem with 10.0.1600.0, 10.0.1779.0 (CU 2), as well as 10.0.2531 (SP1)
I am aware that other people have had this issue and have reviewed all existing posts. I have verified that the MSDTC is configured correctly on both machines. I have also used DTCTester to verify that DTC is working correctly on all machines in question.
None of the mentioned resolutions has solved this problem for me.
I am not seeing this problem occur on my 32 bit test machines - it is only occurring if at least one of the two machines is 64 bit.

Hi All,
I realise that this topic may be a little bit out-of-date but if someone gets here from some search engine trying to find a solution for DTC problems, this MAY be useful.
So... I recently had the same issue, tried all the approaches described in KB and other articles, but it didn't help. Because my task to solve this was not of the highest priority I forgot about it for some time.
Today I was troubleshooting some other issue and, by accident discovered source of that first problem:
In the EventViewer I found Error entry logged by MSDTC saying:
"The local MS DTC detected that the MS DTC on vm-server1 (other machine name that also runs DTC - my comment) has the same unique identity as the local MS DTC. This means that the two MS DTC will not be able to communicate
with each other. This problem typically occurs if one of the systems were cloned using unsupported cloning tools. MS DTC requires that the systems be cloned using supported cloning tools such as SYSPREP. Running 'msdtc -uninstall' and then 'msdtc -install'
from the command prompt will fix the problem. Note: Running 'msdtc -uninstall' will result in the system losing all MS DTC configuration information."
So I followed suggestion and run:
msdtc -uninstall
msdtc -install
This solved my problems with DTC. Hope it will help someone.
Piotr

Transact-SQL debugger not working in SQL Server 2008: "...debugger does not support SQL Server 2005 or earlier..."

I have recently installed SQL Server 2008. When I try to execute a query against an Access database, I receive this debugging error:
"Unable to start Transact-SQL debugger. The Transact-SQL debugger does not support SQL Server 2005 or earlier versions of SQL Server. (SQLEditors)"
Nor will the query execute; I get a transport-level error 0. Any thoughts?

Hi Davidmhjr,
>>Unable to start the Transact-SQL Debugger. The Transact-SQL Debugger does not support SQL Server 2005 or earlier versions of SQL Server. (SQLEditors).
Have you tried to restart the server once you have installed SQL Server 2008? As Naomi N mentioned please check the version of SQL Server you are using.
If you tried to connect to SQL Server 2005 from SQL Server 2008 SSMS, you would not be able to debug and get this error, it happens because T-SQL debugger includes both server-side and client-side components. The server-side debugger components are installed
with each instance of the SQL Server 2008 Database Engine. The client-side components are installed when you install the SQL Server 2008 client-side tools.
So it works with SQL Server 2008 only so far. Another way is you can triy to use SQL Server 2005 SSMS to connect to SQL Server 2005.
More information about configuration requirement to run T-SQL debugger as below, please refer:
There are no configuration requirements to run the Transact-SQL debugger when SQL Server Management Studio is running on the same computer as the instance of the SQL Server Database Engine. However, to run the Transact-SQL debugger when SQL Server Management
Studio is running on a different computer from the instance of the Database Engine, you must enable program and port exceptions by using the Windows Firewall Control Panel application on both computers.
On the computer that is running the instance of the Database Engine, in Windows Firewall, specify the following information:
•Add TCP port 135 to the exceptions list.
•Add the program sqlservr.exe to the exceptions list. By default, sqlservr.exe is installed in C:\Program Files\Microsoft SQL Server\MSSQL10.InstanceName\MSSQL\Binn, where InstanceName is MSSQLSERVER for the default instance, and the instance name for
any named instance.
•If the domain policy requires network communications to be done through IPsec, you must also add UDP port 4500 and UDP port 500 to the exception list.
On the computer that is running SQL Server Management Studio, in Windows Firewall, specify the following information:
•Add TCP port 135 to the exceptions list.
•Add program ssms.exe (SQL Server Management Studio) to the exceptions list. By default, ssms.exe is installed in C:\Program Files\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE.
Hope it is helpful.
Regards, Amber zhang

DBCA error ORA-01034 oracle not available on Windows server 2008 r2 64

Hi All,
I have installed oracle 11.2.0.1 on my system having OS Windows server 2008. Then after that through DBCA i was creating the database during that i got ORA-01034 oracle not available. if any body know how to resolve it please reply me.
Thanks & Regards,
Arya

Did you got the error in between when DBCA executed some percentage of work? PLease check its logfiles to get the exact error.

OWC not working on windows server 2008

Similar Messages

Maybe you are looking for