New 3.0 server w/2.2.2 server

Any issue with bringing up a 3.0 server, extending the schema, etc. alongside a production 2.2.x server under the same "MessengerService"?
My plan is to test the 3.0 server which will be fronted by a Netscaler, then once happy with everything remove the 2.2.x server and via the Netscaler give the 3.0 server the name that the 2.2.x server had. A Netscaler is similar to an F5.
Thanks,
Al Hidalgo
UNM Hospitals

Thanks, I'll be doing this tomorrow. My fear was that schema updates could break our current production box.
We actually don't run the archive agent because of a campus agreement as some departments would not run Messenger if conversations were being archived.
Al
On 4/21/2015 at 2:17 PM, Stevo<[email protected]> wrote:
Al Hidalgo sounds like they 'said':
> Any issue with bringing up a 3.0 server, extending the schema, etc.
> alongside a production 2.2.x server under the same "MessengerService"?
>
> My plan is to test the 3.0 server which will be fronted by a
> Netscaler, then once happy with everything remove the 2.2.x server
> and via the Netscaler give the 3.0 server the name that the 2.2.x
> server had. A Netscaler is similar to an F5.
>
> Thanks,
>
> Al Hidalgo
> UNM Hospitals
So my response to Al's comment is...
Kicker is changing the default archiving agent to be the new box before
you move people to it.
Stevo

Similar Messages

  • Stored procedure not found when creating a new recordset binding in Dreamweaver CS6 with ColdFusion Server 11

    Stored procedure not found when creating a new recordset binding in Dreamweaver CS6 with ColdFusion Server 11.  I can see the tables and views in the database tab, but no stored procedures.  If I connect to a data source created in ColdFusion Server 6 I am able to see the stored procedures.

    Ben thanks for the reply!
    Yes that is the process I am following:
    In Dreamweaver, open the page that will run the stored procedure.
    In the Bindings panel (Window > Bindings), click the Plus button, and then select Stored Procedure.
    In the Data Source pop‑up menu, select a connection to the database containing the stored procedure
    Enter the ColdFusion Data Source user name and password.
    At this point in the procedure drop down I would get a message that said No Stored Procedure Found.
    Right now it appears to be working, I had to create a new site that pointed to the older CF 6 server's data source and create a page following the process above, then when I went back to the CF 11 site the stored procedures were now populated.  I need to make sure it is pulling from the correct server but right now it appears to be working.
    Thanks
    Dwight

  • I can't install Premiere Elements {new purchase} because of "Error 2350. 'FDI Server Error.'"

    I can't install Premiere Elements {new purchase} because of "Error 2350. 'FDI Server Error.'" I cannot "ignore"  I can only abort. Adobe says that my purchase is not supported even though it's new. Help anyone?

    Locoba
    What is the computer operating system involved? Can we assume Premiere Elements 12 as the new purchase? And, are you trying to install from an installation disc or from purchased online downloaded installation files?
    I have not run into Error 2350. FDI Server Error before, but here are some links that talk about Error 2350. Please see if any of them apply to your situation.
    http://helpx.adobe.com/creative-suite/kb/install-error-1311-1335-or.html
    Not Adobe, Error 2350. FDI Server Error.
    http://feedback.bizagi.com/suite/en/responses/error-2350-fdi-server-error
    More details on your situation may help in fine tuning the issue specific to your situation.
    How are you installing?
    Are you installing to default location?
    Is antivirus and firewalls disabled?
    ATR

  • Extend the EPM install to a new EOI and remove the old EOI's (server decommissioning). EPM version 11.1.2.1 and having essbase and planning; I understand removing EOI's is not as simple as 11.1.2.3 but any suggestion/steps would be of great help.

    Extend the EPM install to a new EOI and remove the old EOI's (server decommissioning). EPM version 11.1.2.1 and having essbase and planning; I understand removing EOI's is not as simple as 11.1.2.3 but any suggestion/steps would be of great help....

    Next time try to create a topic that is not the question.
    There was no option to remove epm instances in 11.1.2.1, basically the cloest you get is uninstalling the products on the server and hope that some of the info is removed from the epm registry
    Cheers
    John

  • My IPAD won't accept my wi-fi password. I have tried resetting all settings and network settings but still won't accept it. Can't download to new version of IOS either, says software update server could not be contacted.

    my IPAD won't accept my wi-fi password. I have tried resetting all settings and network settings but still won't accept it. Can't download to new version of IOS either, says software update server could not be contacted.

    Yes I have put in the correct password, its all numbers so can't get it wrong really.
    It has connected before as has my iPod and that won't connect either. I have checked that they aren't on the blocked list of the wi fi. Managed to download the new version of iOS and that hasn't made a difference.
    I have the wi fi plugged directly into the computer rather than the booster hub as the computer won't connect to it when its in the hub. I did get the iPad to connect to the internet when it twas in the hub but once I upgraded the iOS it won't accept the wifi password in the hub either.

  • I just tried updating my iPhone 5 to the new iOS7 and it keeps saying the activation server can not be reached...My phone has been down for almost an hour now. Can anyone help? thank you

    I just tried updating my iPhone 5 to the new iOS7 and it keeps saying the activation server can not be reached...My phone has been down for almost an hour now. Can anyone help? thank you

    Too many people are flooding Apple's servers, everyone is having this issue, try every so often, or wait until tomorrow.

  • New Installation for Mac Os X Snow Leopard Server

    Hi,
    I am new to mack sertvers. Any one know, can I install Mac OS X Snow Leopard on this Dell server?????
    Link for Dell server: http://www.dell.com/us/business/p/poweredge-r710/pd

    Given sufficient free disk and available memory (10 GB or more free disk, and 2 GB or more physical memory, respectively), most any desktop Intel Mac will work with Mac OS X Server 10.6 Snow Leopard Server.  This per the Snow Leopard Server 10.6 Technical Specifications.
    Laptops can also work, but are not supported AFAIK, and Mac OS X Server isn't particularly suited for laptops.
    Apple sells packaged configurations based on Mac Mini (Mac Mini Server) and Mac Pro (Mac Pro Server).
    The upcoming Lion Server requires specific Intel processors.

  • Best way to Restore Database to create a new Database having different dependent objects like linked server names in the procedures

    Hi All,
    Am creating a new test server by cloning the production server. Creating Dbs by restoring the production backup but wondering is there any best way to update the linked server names in open query of few SPs other than manual checking and updating.
    Thanks,
    Swapna

    It will not update the stored procedure rather it generates the scripts. You can validate and execute the script later.
    Try this link
    http://www.ideosity.com/ourblog/post/ideosphere-blog/2013/06/14/how-to-find-and-replace-text-in-all-stored-procedures
    --Prashanth

  • ADPrep Migration from Windows Server 2003 to 2012 Foundation Server fails with error 0x80004005

    Hi all,
    Having a problem the forums and Google have been unsuccessful in helping me with. Server is Windows 2003 R2, migrating to Windows Server 2012 foundation.  Have tried the AD Migration on the new 2012 Foundation server both as a standalone server
    and a domain server member before running the migration.  I get the following error:
    ADPrep execution failed --> System.ComponentModel.Win32Exception (0x80004005): A device attached to the system is not functioning
    I've checked the ADprep logs and have found the following:
    [2013/01/22:11:15:01.000]
    Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is cn=abd97102-88dd-4013-a009-0e2c2f967ff6,cn=Operations,cn=ForestUpdates,CN=Configuration,DC=apl,DC=local.
    [2013/01/22:11:15:01.001]
    LDAP API ldap_search_s() finished, return code is 0x0 
    [2013/01/22:11:15:01.001]
    Adprep checked to verify whether operation cn=abd97102-88dd-4013-a009-0e2c2f967ff6,cn=Operations,cn=ForestUpdates,CN=Configuration,DC=apl,DC=local has completed.
    [Status/Consequence]
    The operation GUID already exists so Adprep did not attempt to rerun this operation but is continuing.
    [2013/01/22:11:15:01.001]
    Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is cn=134428a8-0043-48a6-bcda-63310d9ec4dd,cn=Operations,cn=ForestUpdates,CN=Configuration,DC=apl,DC=local.
    [2013/01/22:11:15:01.001]
    LDAP API ldap_search_s() finished, return code is 0x20 
    [2013/01/22:11:15:01.001]
    Adprep verified the state of operation cn=134428a8-0043-48a6-bcda-63310d9ec4dd,cn=Operations,cn=ForestUpdates,CN=Configuration,DC=apl,DC=local. 
    [Status/Consequence]
    The operation has not run or is not currently running. It will be run next.
    [2013/01/22:11:15:01.021]
    Adprep was unable to complete because the call back function failed. 
    [Status/Consequence]
    Error message: Unable to access the computer "SERVER.apl.local". The network path was not found.
     (0x80070035).
    [User Action]
    Check the log file ADPrep.log, in the C:\Windows\debug\adprep\logs\20130122111500 directory for more information.
    DSID Info:
    DSID: 0x1811132a
    winerror = 0x1f
    NT BUILD: 9200
    NT BUILD: 16384
    [2013/01/22:11:15:01.021]
    Adprep was unable to update forest information. 
    [Status/Consequence]
    Adprep requires access to existing forest-wide information from the schema master in order to complete this operation.
    [User Action]
    Check the log file, ADPrep.log, in the C:\Windows\debug\adprep\logs\20130122111500 directory for more information. 
    We did have AVAST Antivirus installed on the server but this was removed.  Any idea's?
    Jason.
    Consultant | Nerd | Visionary. http://www.ethertech.com.au/ | http://www.deeperstates.com.au

    Hi Biswajit et. al., thanks for your help thus far, it is greatly appreciated...
    Unfortunately I had already disabled the NIC's on both hosts.  They currently remain disabled.  I've just tried turning off IPv6 as well and no luck.
    PortQry came back fine (I think) :)
    =============================================
     Starting portqry.exe -n server.apl.local -e 135 -p TCP ...
    Querying target system called:
     server.apl.local
    Attempting to resolve name to IP address...
    Name resolved to 10.0.0.3
    querying...
    TCP port 135 (epmap service): LISTENING
    Using ephemeral source port
    Querying Endpoint Mapper Database...
    Server's response:
    UUID: 3c4728c5-f0ab-448b-bda1-6ce01eb0a6d5 DHCP Client LRPC Endpoint
    ncalrpc:[dhcpcsvc]
    UUID: f1ec59ab-4ca9-4c30-b2d0-54ef1db441b7 Isolation Communication Endpoint
    ncalrpc:[LRPC00001d40.00000001]
    UUID: f1ec59ab-4ca9-4c30-b2d0-54ef1db441b7 Isolation Communication Endpoint
    ncalrpc:[LRPC00001448.00000001]
    UUID: 906b0ce0-c70b-1067-b317-00dd010662da 
    ncalrpc:[OLE4EF57D32A0DB45F9A64653468D7C]
    UUID: 906b0ce0-c70b-1067-b317-00dd010662da 
    ncalrpc:[LRPC000012ac.00000001]
    UUID: 2f5f6521-cb55-1059-b446-00df0bce31db Unimodem LRPC Endpoint
    ncacn_np:\\\\SERVER[\\pipe\\tapsrv]
    UUID: 2f5f6521-cb55-1059-b446-00df0bce31db Unimodem LRPC Endpoint
    ncalrpc:[tapsrvlpc]
    UUID: 2f5f6521-cb55-1059-b446-00df0bce31db Unimodem LRPC Endpoint
    ncalrpc:[unimdmsvc]
    UUID: 3473dd4d-2e88-4006-9cba-22570909dd10 WinHttp Auto-Proxy Service
    ncalrpc:[W32TIME_ALT]
    UUID: 3473dd4d-2e88-4006-9cba-22570909dd10 WinHttp Auto-Proxy Service
    ncacn_np:\\\\SERVER[\\PIPE\\W32TIME_ALT]
    UUID: 6bffd098-a112-3610-9833-46c3f874532d 
    ncalrpc:[OLE7C4E3B9B79D8492CBA384F149E08]
    UUID: 6bffd098-a112-3610-9833-46c3f874532d 
    ncacn_ip_tcp:10.0.0.3[1111]
    UUID: 6bffd098-a112-3610-9833-46c3f874532d 
    ncalrpc:[DHCPSERVERLPC]
    UUID: 5b821720-f63b-11d0-aad2-00c04fc324db 
    ncalrpc:[OLE7C4E3B9B79D8492CBA384F149E08]
    UUID: 5b821720-f63b-11d0-aad2-00c04fc324db 
    ncacn_ip_tcp:10.0.0.3[1111]
    UUID: 5b821720-f63b-11d0-aad2-00c04fc324db 
    ncalrpc:[DHCPSERVERLPC]
    UUID: 3d267954-eeb7-11d1-b94e-00c04fa3080d 
    ncalrpc:[LRPC00000480.00000001]
    UUID: 3d267954-eeb7-11d1-b94e-00c04fa3080d 
    ncacn_np:\\\\SERVER[\\pipe\\HydraLsPipe]
    UUID: 3d267954-eeb7-11d1-b94e-00c04fa3080d 
    ncacn_ip_tcp:10.0.0.3[1092]
    UUID: 12d4b7c8-77d5-11d1-8c24-00c04fa3080d 
    ncalrpc:[LRPC00000480.00000001]
    UUID: 12d4b7c8-77d5-11d1-8c24-00c04fa3080d 
    ncacn_np:\\\\SERVER[\\pipe\\HydraLsPipe]
    UUID: 12d4b7c8-77d5-11d1-8c24-00c04fa3080d 
    ncacn_ip_tcp:10.0.0.3[1092]
    UUID: 493c451c-155c-11d3-a314-00c04fb16103 
    ncalrpc:[LRPC00000480.00000001]
    UUID: 493c451c-155c-11d3-a314-00c04fb16103 
    ncacn_np:\\\\SERVER[\\pipe\\HydraLsPipe]
    UUID: 493c451c-155c-11d3-a314-00c04fb16103 
    ncacn_ip_tcp:10.0.0.3[1092]
    UUID: 45f52c28-7f9f-101a-b52b-08002b2efabe 
    ncalrpc:[OLE43978C47C6F54B5499302BAB2F50]
    UUID: 45f52c28-7f9f-101a-b52b-08002b2efabe 
    ncacn_ip_tcp:10.0.0.3[1090]
    UUID: 45f52c28-7f9f-101a-b52b-08002b2efabe 
    ncalrpc:[LRPC00001060.00000001]
    UUID: 45f52c28-7f9f-101a-b52b-08002b2efabe 
    ncacn_np:\\\\SERVER[\\pipe\\WinsPipe]
    UUID: 811109bf-a4e1-11d1-ab54-00a0c91e9b45 
    ncalrpc:[OLE43978C47C6F54B5499302BAB2F50]
    UUID: 811109bf-a4e1-11d1-ab54-00a0c91e9b45 
    ncacn_ip_tcp:10.0.0.3[1090]
    UUID: 811109bf-a4e1-11d1-ab54-00a0c91e9b45 
    ncalrpc:[LRPC00001060.00000001]
    UUID: 811109bf-a4e1-11d1-ab54-00a0c91e9b45 
    ncacn_np:\\\\SERVER[\\pipe\\WinsPipe]
    UUID: f5cc59b4-4264-101a-8c59-08002b2f8426 NtFrs Service
    ncalrpc:[OLE92F283EA5C2F497093CE6A52B7D8]
    UUID: f5cc59b4-4264-101a-8c59-08002b2f8426 NtFrs Service
    ncacn_ip_tcp:10.0.0.3[1067]
    UUID: f5cc59b4-4264-101a-8c59-08002b2f8426 NtFrs Service
    ncalrpc:[LRPC00000d10.00000001]
    UUID: d049b186-814f-11d1-9a3c-00c04fc9b232 NtFrs API
    ncalrpc:[OLE92F283EA5C2F497093CE6A52B7D8]
    UUID: d049b186-814f-11d1-9a3c-00c04fc9b232 NtFrs API
    ncacn_ip_tcp:10.0.0.3[1067]
    UUID: d049b186-814f-11d1-9a3c-00c04fc9b232 NtFrs API
    ncalrpc:[LRPC00000d10.00000001]
    UUID: a00c021c-2be2-11d2-b678-0000f87a8f8e PERFMON SERVICE
    ncalrpc:[OLE92F283EA5C2F497093CE6A52B7D8]
    UUID: a00c021c-2be2-11d2-b678-0000f87a8f8e PERFMON SERVICE
    ncacn_ip_tcp:10.0.0.3[1067]
    UUID: a00c021c-2be2-11d2-b678-0000f87a8f8e PERFMON SERVICE
    ncalrpc:[LRPC00000d10.00000001]
    UUID: 50abc2a4-574d-40b3-9d66-ee4fd5fba076 
    ncacn_ip_tcp:10.0.0.3[1048]
    UUID: 906b0ce0-c70b-1067-b317-00dd010662da 
    ncalrpc:[LRPC000004d4.00000001]
    UUID: 906b0ce0-c70b-1067-b317-00dd010662da 
    ncacn_ip_tcp:10.0.0.3[1032]
    UUID: 906b0ce0-c70b-1067-b317-00dd010662da 
    ncalrpc:[LRPC000004d4.00000001]
    UUID: 906b0ce0-c70b-1067-b317-00dd010662da 
    ncacn_ip_tcp:10.0.0.3[1032]
    UUID: 906b0ce0-c70b-1067-b317-00dd010662da 
    ncalrpc:[LRPC000004d4.00000001]
    UUID: 906b0ce0-c70b-1067-b317-00dd010662da 
    ncacn_ip_tcp:10.0.0.3[1032]
    UUID: 906b0ce0-c70b-1067-b317-00dd010662da 
    ncalrpc:[LRPC000004d4.00000001]
    UUID: 906b0ce0-c70b-1067-b317-00dd010662da 
    ncacn_ip_tcp:10.0.0.3[1032]
    UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
    ncacn_np:\\\\SERVER[\\PIPE\\lsass]
    UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
    ncalrpc:[audit]
    UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
    ncalrpc:[securityevent]
    UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
    ncalrpc:[protected_storage]
    UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
    ncacn_np:\\\\SERVER[\\PIPE\\protected_storage]
    UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
    ncalrpc:[dsrole]
    UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
    ncacn_ip_tcp:10.0.0.3[1026]
    UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
    ncalrpc:[NTDS_LPC]
    UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
    ncacn_http:10.0.0.3[1027]
    UUID: 12345778-1234-abcd-ef00-0123456789ab 
    ncacn_np:\\\\SERVER[\\PIPE\\lsass]
    UUID: 12345778-1234-abcd-ef00-0123456789ab 
    ncalrpc:[audit]
    UUID: 12345778-1234-abcd-ef00-0123456789ab 
    ncalrpc:[securityevent]
    UUID: 12345778-1234-abcd-ef00-0123456789ab 
    ncalrpc:[protected_storage]
    UUID: 12345778-1234-abcd-ef00-0123456789ab 
    ncacn_np:\\\\SERVER[\\PIPE\\protected_storage]
    UUID: 12345778-1234-abcd-ef00-0123456789ab 
    ncalrpc:[dsrole]
    UUID: 12345778-1234-abcd-ef00-0123456789ab 
    ncacn_ip_tcp:10.0.0.3[1026]
    UUID: 12345778-1234-abcd-ef00-0123456789ab 
    ncalrpc:[NTDS_LPC]
    UUID: 12345778-1234-abcd-ef00-0123456789ab 
    ncacn_http:10.0.0.3[1027]
    UUID: 12345778-1234-abcd-ef00-0123456789ac 
    ncacn_np:\\\\SERVER[\\PIPE\\lsass]
    UUID: 12345778-1234-abcd-ef00-0123456789ac 
    ncalrpc:[audit]
    UUID: 12345778-1234-abcd-ef00-0123456789ac 
    ncalrpc:[securityevent]
    UUID: 12345778-1234-abcd-ef00-0123456789ac 
    ncalrpc:[protected_storage]
    UUID: 12345778-1234-abcd-ef00-0123456789ac 
    ncacn_np:\\\\SERVER[\\PIPE\\protected_storage]
    UUID: 12345778-1234-abcd-ef00-0123456789ac 
    ncalrpc:[dsrole]
    UUID: 12345778-1234-abcd-ef00-0123456789ac 
    ncacn_ip_tcp:10.0.0.3[1026]
    UUID: 12345778-1234-abcd-ef00-0123456789ac 
    ncalrpc:[NTDS_LPC]
    UUID: 12345778-1234-abcd-ef00-0123456789ac 
    ncacn_http:10.0.0.3[1027]
    UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface
    ncacn_np:\\\\SERVER[\\PIPE\\lsass]
    UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface
    ncalrpc:[audit]
    UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface
    ncalrpc:[securityevent]
    UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface
    ncalrpc:[protected_storage]
    UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface
    ncacn_np:\\\\SERVER[\\PIPE\\protected_storage]
    UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface
    ncalrpc:[dsrole]
    UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface
    ncacn_ip_tcp:10.0.0.3[1026]
    UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface
    ncalrpc:[NTDS_LPC]
    UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface
    ncacn_http:10.0.0.3[1027]
    UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface
    ncacn_np:\\\\SERVER[\\PIPE\\lsass]
    UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface
    ncalrpc:[audit]
    UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface
    ncalrpc:[securityevent]
    UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface
    ncalrpc:[protected_storage]
    UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface
    ncacn_np:\\\\SERVER[\\PIPE\\protected_storage]
    UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface
    ncalrpc:[dsrole]
    UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface
    ncacn_ip_tcp:10.0.0.3[1026]
    UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface
    ncalrpc:[NTDS_LPC]
    UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface
    ncacn_http:10.0.0.3[1027]
    UUID: 12345678-1234-abcd-ef00-01234567cffb 
    ncacn_np:\\\\SERVER[\\PIPE\\lsass]
    UUID: 12345678-1234-abcd-ef00-01234567cffb 
    ncalrpc:[audit]
    UUID: 12345678-1234-abcd-ef00-01234567cffb 
    ncalrpc:[securityevent]
    UUID: 12345678-1234-abcd-ef00-01234567cffb 
    ncalrpc:[protected_storage]
    UUID: 12345678-1234-abcd-ef00-01234567cffb 
    ncacn_np:\\\\SERVER[\\PIPE\\protected_storage]
    UUID: 12345678-1234-abcd-ef00-01234567cffb 
    ncalrpc:[dsrole]
    UUID: 12345678-1234-abcd-ef00-01234567cffb 
    ncacn_ip_tcp:10.0.0.3[1026]
    UUID: 12345678-1234-abcd-ef00-01234567cffb 
    ncalrpc:[NTDS_LPC]
    UUID: 12345678-1234-abcd-ef00-01234567cffb 
    ncacn_http:10.0.0.3[1027]
    UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
    ncacn_np:\\\\SERVER[\\PIPE\\lsass]
    UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
    ncalrpc:[audit]
    UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
    ncalrpc:[securityevent]
    UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
    ncalrpc:[protected_storage]
    UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
    ncacn_np:\\\\SERVER[\\PIPE\\protected_storage]
    UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
    ncalrpc:[dsrole]
    UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
    ncacn_ip_tcp:10.0.0.3[1026]
    UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
    ncalrpc:[NTDS_LPC]
    UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
    ncacn_http:10.0.0.3[1027]
    UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
    ncalrpc:[OLE8B33809919104CE5B44970B01637]
    UUID: 1ff70682-0a51-30e8-076d-740be8cee98b 
    ncalrpc:[wzcsvc]
    UUID: 1ff70682-0a51-30e8-076d-740be8cee98b 
    ncalrpc:[OLE396AE4FBEFCC4DD2B44D0F0A3691]
    UUID: 1ff70682-0a51-30e8-076d-740be8cee98b 
    ncacn_np:\\\\SERVER[\\PIPE\\atsvc]
    UUID: 378e52b0-c0a9-11cf-822d-00aa0051e40f 
    ncalrpc:[wzcsvc]
    UUID: 378e52b0-c0a9-11cf-822d-00aa0051e40f 
    ncalrpc:[OLE396AE4FBEFCC4DD2B44D0F0A3691]
    UUID: 378e52b0-c0a9-11cf-822d-00aa0051e40f 
    ncacn_np:\\\\SERVER[\\PIPE\\atsvc]
    UUID: 0a74ef1c-41a4-4e06-83ae-dc74fb1cdd53 
    ncalrpc:[wzcsvc]
    UUID: 0a74ef1c-41a4-4e06-83ae-dc74fb1cdd53 
    ncalrpc:[OLE396AE4FBEFCC4DD2B44D0F0A3691]
    UUID: 0a74ef1c-41a4-4e06-83ae-dc74fb1cdd53 
    ncacn_np:\\\\SERVER[\\PIPE\\atsvc]
    UUID: 3c4728c5-f0ab-448b-bda1-6ce01eb0a6d5 DHCP Client LRPC Endpoint
    ncalrpc:[DNSResolver]
    Total endpoints found: 125
    ==== End of RPC Endpoint Mapper query response ====
    portqry.exe -n server.apl.local -e 135 -p TCP exits with return code 0x00000000.
    =============================================
     Starting portqry.exe -n server.apl.local -e 389 -p BOTH ...
    Querying target system called:
     server.apl.local
    Attempting to resolve name to IP address...
    Name resolved to 10.0.0.3
    querying...
    TCP port 389 (ldap service): LISTENING
    Using ephemeral source port
    Sending LDAP query to TCP port 389...
    LDAP query response:
    currentdate: 01/28/2013 14:11:54 (unadjusted GMT)
    subschemaSubentry: CN=Aggregate,CN=Schema,CN=Configuration,DC=apl,DC=local
    dsServiceName: CN=NTDS Settings,CN=SERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=apl,DC=local
    namingContexts: DC=apl,DC=local
    defaultNamingContext: DC=apl,DC=local
    schemaNamingContext: CN=Schema,CN=Configuration,DC=apl,DC=local
    configurationNamingContext: CN=Configuration,DC=apl,DC=local
    rootDomainNamingContext: DC=apl,DC=local
    supportedControl: 1.2.840.113556.1.4.319
    supportedLDAPVersion: 3
    supportedLDAPPolicies: MaxPoolThreads
    highestCommittedUSN: 1310788
    supportedSASLMechanisms: GSSAPI
    dnsHostName: SERVER.apl.local
    ldapServiceName: apl.local:[email protected]
    serverName: CN=SERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=apl,DC=local
    supportedCapabilities: 1.2.840.113556.1.4.800
    isSynchronized: TRUE
    isGlobalCatalogReady: TRUE
    domainFunctionality: 2
    forestFunctionality: 2
    domainControllerFunctionality: 2
    ======== End of LDAP query response ========
    UDP port 389 (unknown service): LISTENING or FILTERED
    Using ephemeral source port
    Sending LDAP query to UDP port 389...
    LDAP query response:
    currentdate: 01/28/2013 14:11:57 (unadjusted GMT)
    subschemaSubentry: CN=Aggregate,CN=Schema,CN=Configuration,DC=apl,DC=local
    dsServiceName: CN=NTDS Settings,CN=SERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=apl,DC=local
    namingContexts: DC=apl,DC=local
    defaultNamingContext: DC=apl,DC=local
    schemaNamingContext: CN=Schema,CN=Configuration,DC=apl,DC=local
    configurationNamingContext: CN=Configuration,DC=apl,DC=local
    rootDomainNamingContext: DC=apl,DC=local
    supportedControl: 1.2.840.113556.1.4.319
    supportedLDAPVersion: 3
    supportedLDAPPolicies: MaxPoolThreads
    highestCommittedUSN: 1310788
    supportedSASLMechanisms: GSSAPI
    dnsHostName: SERVER.apl.local
    ldapServiceName: apl.local:[email protected]
    serverName: CN=SERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=apl,DC=local
    supportedCapabilities: 1.2.840.113556.1.4.800
    isSynchronized: TRUE
    isGlobalCatalogReady: TRUE
    domainFunctionality: 2
    forestFunctionality: 2
    domainControllerFunctionality: 2
    ======== End of LDAP query response ========
    UDP port 389 is LISTENING
    portqry.exe -n server.apl.local -e 389 -p BOTH exits with return code 0x00000000.
    =============================================
     Starting portqry.exe -n server.apl.local -e 636 -p TCP ...
    Querying target system called:
     server.apl.local
    Attempting to resolve name to IP address...
    Name resolved to 10.0.0.3
    querying...
    TCP port 636 (ldaps service): LISTENING
    portqry.exe -n server.apl.local -e 636 -p TCP exits with return code 0x00000000.
    =============================================
     Starting portqry.exe -n server.apl.local -e 3268 -p TCP ...
    Querying target system called:
     server.apl.local
    Attempting to resolve name to IP address...
    Name resolved to 10.0.0.3
    querying...
    TCP port 3268 (msft-gc service): LISTENING
    Using ephemeral source port
    Sending LDAP query to TCP port 3268...
    LDAP query response:
    currentdate: 01/28/2013 14:11:57 (unadjusted GMT)
    subschemaSubentry: CN=Aggregate,CN=Schema,CN=Configuration,DC=apl,DC=local
    dsServiceName: CN=NTDS Settings,CN=SERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=apl,DC=local
    namingContexts: DC=apl,DC=local
    defaultNamingContext: DC=apl,DC=local
    schemaNamingContext: CN=Schema,CN=Configuration,DC=apl,DC=local
    configurationNamingContext: CN=Configuration,DC=apl,DC=local
    rootDomainNamingContext: DC=apl,DC=local
    supportedControl: 1.2.840.113556.1.4.319
    supportedLDAPVersion: 3
    supportedLDAPPolicies: MaxPoolThreads
    highestCommittedUSN: 1310788
    supportedSASLMechanisms: GSSAPI
    dnsHostName: SERVER.apl.local
    ldapServiceName: apl.local:[email protected]
    serverName: CN=SERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=apl,DC=local
    supportedCapabilities: 1.2.840.113556.1.4.800
    isSynchronized: TRUE
    isGlobalCatalogReady: TRUE
    domainFunctionality: 2
    forestFunctionality: 2
    domainControllerFunctionality: 2
    ======== End of LDAP query response ========
    portqry.exe -n server.apl.local -e 3268 -p TCP exits with return code 0x00000000.
    =============================================
     Starting portqry.exe -n server.apl.local -e 3269 -p TCP ...
    Querying target system called:
     server.apl.local
    Attempting to resolve name to IP address...
    Name resolved to 10.0.0.3
    querying...
    TCP port 3269 (msft-gc-ssl service): LISTENING
    portqry.exe -n server.apl.local -e 3269 -p TCP exits with return code 0x00000000.
    =============================================
     Starting portqry.exe -n server.apl.local -e 53 -p BOTH ...
    Querying target system called:
     server.apl.local
    Attempting to resolve name to IP address...
    Name resolved to 10.0.0.3
    querying...
    TCP port 53 (domain service): LISTENING
    UDP port 53 (domain service): LISTENING
    portqry.exe -n server.apl.local -e 53 -p BOTH exits with return code 0x00000000.
    =============================================
     Starting portqry.exe -n server.apl.local -e 88 -p BOTH ...
    Querying target system called:
     server.apl.local
    Attempting to resolve name to IP address...
    Name resolved to 10.0.0.3
    querying...
    TCP port 88 (kerberos service): LISTENING
    UDP port 88 (kerberos service): LISTENING or FILTERED
    portqry.exe -n server.apl.local -e 88 -p BOTH exits with return code 0x00000002.
    =============================================
     Starting portqry.exe -n server.apl.local -e 445 -p TCP ...
    Querying target system called:
     server.apl.local
    Attempting to resolve name to IP address...
    Name resolved to 10.0.0.3
    querying...
    TCP port 445 (microsoft-ds service): LISTENING
    portqry.exe -n server.apl.local -e 445 -p TCP exits with return code 0x00000000.
    =============================================
     Starting portqry.exe -n server.apl.local -e 137 -p UDP ...
    Querying target system called:
     server.apl.local
    Attempting to resolve name to IP address...
    Name resolved to 10.0.0.3
    querying...
    UDP port 137 (netbios-ns service): LISTENING or FILTERED
    Using ephemeral source port
    Attempting NETBIOS adapter status query to UDP port 137...
    Server's response: MAC address 000423c733ec
    UDP port: LISTENING
    portqry.exe -n server.apl.local -e 137 -p UDP exits with return code 0x00000000.
    =============================================
     Starting portqry.exe -n server.apl.local -e 138 -p UDP ...
    Querying target system called:
     server.apl.local
    Attempting to resolve name to IP address...
    Name resolved to 10.0.0.3
    querying...
    UDP port 138 (netbios-dgm service): LISTENING or FILTERED
    portqry.exe -n server.apl.local -e 138 -p UDP exits with return code 0x00000002.
    =============================================
     Starting portqry.exe -n server.apl.local -e 139 -p TCP ...
    Querying target system called:
     server.apl.local
    Attempting to resolve name to IP address...
    Name resolved to 10.0.0.3
    querying...
    TCP port 139 (netbios-ssn service): LISTENING
    portqry.exe -n server.apl.local -e 139 -p TCP exits with return code 0x00000000.
    =============================================
     Starting portqry.exe -n server.apl.local -e 42 -p TCP ...
    Querying target system called:
     server.apl.local
    Attempting to resolve name to IP address...
    Name resolved to 10.0.0.3
    querying...
    TCP port 42 (nameserver service): LISTENING
    portqry.exe -n server.apl.local -e 42 -p TCP exits with return code 0x00000000.
    Jason.
    Consultant | Nerd | Visionary. http://www.ethertech.com.au/ | http://www.deeperstates.com.au

  • How  remote managed server to connect to admin server

    I have an admin server on one machine and created a managed server on different
    machine, I am not able to start managed server from either machine. When I used
    the admin server machine to start the managed server remotely I got this message
    Connecting to http://fkeita:7001...
    <Jul 17, 2002 11:11:06 AM EDT> <Notice> <Security> <090082> <Security initializi
    ng using realm myrealm.>
    <Jul 17, 2002 11:11:06 AM EDT> <Notice> <WebLogicServer> <000328> <Starting WebL
    ogic Managed Server "managedserver3" for domain "admindomain">
    <Jul 17, 2002 11:11:28 AM EDT> <Emergency> <WebLogicServer> <000350> <Unable to
    create a server socket on Channel Default for: BFINKELMAN/90.0.0.25, port: 8002.
    java.net.BindException: Cannot assign requested address: JVM_Bind Perhaps the
    a
    ddress BFINKELMAN/90.0.0.25 is incorrect or another process is using port 8002.>
    <Jul 17, 2002 11:11:29 AM EDT> <Emergency> <Security> <090085> <Server failed
    to
    bind to any port such that it is not reachable from the console.>
    <Jul 17, 2002 11:11:29 AM EDT> <Emergency> <WebLogicServer> <000342> <Unable to
    initialize the server: Fatal initialization exception>
    When I tried to connect managed server from its machine to admin server (running
    on separate machine ) I got this error
    Starting WebLogic Server...
    Connecting to http://fkeita:7001...
    <Jul 17, 2002 11:15:18 AM EDT> <Notice> <Security> <090082> <Security initializi
    ng using realm myrealm.>
    <Jul 17, 2002 11:15:18 AM EDT> <Critical> <WebLogicServer> <000364> <Server fail
    ed during initialization. Exception:java.lang.SecurityException: Authentication
    for user system denied
    java.lang.SecurityException: Authentication for user system denied
    at weblogic.security.service.SecurityServiceManager.doBootAuthorization(
    SecurityServiceManager.java:978)
    at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
    erviceManager.java:1116)
    at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
    at weblogic.Server.main(Server.java:31)
    >
    <Jul 17, 2002 11:15:18 AM EDT> <Emergency> <WebLogicServer> <000342> <Unable to
    initialize the server: Fatal initialization exception
    Throwable: java.lang.SecurityException: Authentication for user system denied
    java.lang.SecurityException: Authentication for user system denied
    at weblogic.security.service.SecurityServiceManager.doBootAuthorization(
    SecurityServiceManager.java:978)
    at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
    erviceManager.java:1116)
    at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
    at weblogic.Server.main(Server.java:31)
    >
    The WebLogic Server did not start up properly.
    Exception raised:
    java.lang.SecurityException: Authentication for user system denied
    at weblogic.security.service.SecurityServiceManager.doBootAuthorization(
    SecurityServiceManager.java:978)
    at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
    erviceManager.java:1116)
    at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
    at weblogic.Server.main(Server.java:31)
    Reason: Fatal initialization exception
    Throwable: java.lang.SecurityException: Authentication for user system denied
    java.lang.SecurityException: Authentication for user system denied
    at weblogic.security.service.SecurityServiceManager.doBootAuthorization(
    SecurityServiceManager.java:978)
    at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
    erviceManager.java:1116)
    at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
    at weblogic.Server.main(Server.java:31)
    Thanks.

    Is your applications deployed to Cluster?
    If yes it will automatically deploy to new managed servers added to cluster when it comes to running mode

  • Connecting managed server to cluster's administration server

    Hello,
    I have a problem when trying to connect managed server to cluster's
    administration server.
    When starting the managed server I get a security exception:
    [javax.naming.AuthenticationException [Root exception is
    java.lang.SecurityException: Administrators must log in over admin port with
    admin protocol.]]
    weblogic.management.configuration.ConfigurationException: admin URL:
    t3://192.168.14.15:7001 - with nested exception:
    [javax.naming.AuthenticationException [Root exception is
    java.lang.SecurityException: Administrators must log in over admin port with
    admin protocol.]]
    at
    weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:893)
    at weblogic.management.Admin.start(Admin.java:303)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:331)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
    at weblogic.Server.main(Server.java:35)
    I get the same result when testing the connection setup with
    java weblogic.Admin -url 192.168.14.15:7001 -username system -password xyz
    CONNECT 1
    Background for this problem:
    I'm trying to evaluate WLS6.0 clustering for my RMI services. I have two
    machines setup with my test domain (DEdomain) and one cluster (DECluster)
    within it.
    In administration server (machine A) I defined two servers to be run in
    machine A and machine B:
    DEserver2 in machine B (to be started as managed server) and DEserver3
    in machine A
    I'm going to bind a same service into these above servers of my DECluster.
    In machine B's startManagedWeblogic.sh I have:
    java -ms64m -mx64m -classpath
    $CLASSPATH -Dweblogic.Domain=DEdomain -Dweblogic.Name=$SERVER_NAME -Dweblogi
    c.management.server=$ADMIN_URL -Djava.security.policy==$WL_HOME/lib/weblogic
    .policy -Dweblogic.management.username=system -Dweblogic.management.password
    =$WLS_PW weblogic.Server
    In machine A I have administration server DEserver1 listening port 7001.
    And for the domain and cluster building I followed all relevant e-docs
    manual pages. It's still somewhat blurry what kind of preparations I have to
    make in managed server side to join the domain; for example do I have to
    have identical domain directory structure within machine B and do I have to
    configure something with admin console or is everything handled by
    connecting to the administation server and reading the domain's config.xml
    from machine A.
    I'm sure I have missed some fundamental idea for building clustered services
    and would greatly appreciate if someone had any good tips or ideas.
    Best regards,
    Harri

    Hi Kumar,
    and thank you. That fixed my problem
    Best regards,
    Harri
    "Kumar Allamraju" <[email protected]> wrote in message
    news:[email protected]...
    It appears you had set the administration port & listen port on the admin
    server.
    Logging onto admin server via admin port is broken currently. I wouldsuggest
    you to set only listen port
    and see how that goes.
    Kumar
    "Harri Töhönen" wrote:
    Hello,
    I have a problem when trying to connect managed server to cluster's
    administration server.
    When starting the managed server I get a security exception:
    [javax.naming.AuthenticationException [Root exception is
    java.lang.SecurityException: Administrators must log in over admin portwith> > admin protocol.]
    weblogic.management.configuration.ConfigurationException: admin URL:
    t3://192.168.14.15:7001 - with nested exception:
    [javax.naming.AuthenticationException [Root exception is
    java.lang.SecurityException: Administrators must log in over admin portwith> > admin protocol.]
    at
    weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:893)
    at weblogic.management.Admin.start(Admin.java:303)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:331)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
    at weblogic.Server.main(Server.java:35)
    I get the same result when testing the connection setup with
    java weblogic.Admin -url 192.168.14.15:7001 -username system -password
    xyz
    CONNECT 1
    Background for this problem:
    I'm trying to evaluate WLS6.0 clustering for my RMI services. I have two
    machines setup with my test domain (DEdomain) and one cluster(DECluster)
    within it.
    In administration server (machine A) I defined two servers to be run in
    machine A and machine B:
    DEserver2 in machine B (to be started as managed server) andDEserver3
    in machine A
    I'm going to bind a same service into these above servers of myDECluster.
    >>
    In machine B's startManagedWeblogic.sh I have:
    java -ms64m -mx64m -classpath
    $CLASSPATH -Dweblogic.Domain=DEdomain -Dweblogic.Name=$SERVER_NAME -Dweblogi
    >>
    c.management.server=$ADMIN_URL -Djava.security.policy==$WL_HOME/lib/weblogic
    >>
    .policy -Dweblogic.management.username=system -Dweblogic.management.password
    =$WLS_PW weblogic.Server
    In machine A I have administration server DEserver1 listening port 7001.
    And for the domain and cluster building I followed all relevant e-docs
    manual pages. It's still somewhat blurry what kind of preparations Ihave to
    make in managed server side to join the domain; for example do I have to
    have identical domain directory structure within machine B and do I haveto
    configure something with admin console or is everything handled by
    connecting to the administation server and reading the domain'sconfig.xml
    from machine A.
    I'm sure I have missed some fundamental idea for building clusteredservices
    and would greatly appreciate if someone had any good tips or ideas.
    Best regards,
    Harri

  • FileMaker Server problem on Mac Mini Server - Mac Mini won't boot

    I just installed a brand new Mac Mini Server today, and also FileMaker Server 11. A first-timer for both Mac OS X Server and FileMaker Server, I made an error as explained below, and right now I don't know how to get back on track with the system. It won't boot.
    So, how did this happen?
    At first everything was proceeding according to plan. I configured the pre-installed Mac OS X Server on the Mac Mini with users, groups and services. This was tested from clients and this seemed to work just fine. Then I installed and configured FileMaker Server. This was also tested from a client, and the example database that came with FMS was served up just fine.
    The problem arose when I tried to install my existing FileMaker databases. I simply checked to see where in the file system the example database was located, and then copied my old databases to that location (I think it was Library > FileMaker Server > Data > Databases or something close to it - can't check it now...). I had the FileMaker Server Admin Console running, and hit the Refresh button hoping that this would make FileMaker Server find the databases.
    This was my first error. I should have read ahead in the instructions to see that one is supposed to use an Upload Database assistant instead...
    What happened when I hit refresh was that the FileMaker Server Admin Console became completely unresponsive with a spinning ball as cursor. I left it for about an hour hoping it would terminate, but gave up and tried to shut it down. It wouldn't close, so I force quit it from the Finder. Then I tried to shut down FileMaker Server, but I needed to force quit this as well. After this I thought it would be best to reboot the Mac Mini, so I shut it down, but now it won't even boot, it just stays on the screen with the spinning wheel for ever!
    I have tried all the keyboard options while booting, but nothing seems to help. In safe mode, the grey progress bar just grows to about one third, then disappears and leaves the eternally spinning wheel.
    The server version of the Mac Mini doesn't have an optical drive, only two internal hard drives. I tried to reinstall from scratch using the optical drive on another Mac on the network. The startup disk appeared when I tried to boot the Mac Mini holding down the option key, and after about 20 minutes or so of the spinning wheel I could actually access the discs. I started by running Disk Utility to check disk permissions. There were a lot of repairs concerning permissions and groups, especially on "Library". It said "ACL differs on Library", I don't know what this is but this was repaired. I then ran Repair Disk. The volume appeared to be OK.
    When I tried to reinstall Mac OS X Server however, this failed with the message
    "You can't upgrade this version of Mac OS X because a newer version is installed. Mac OS X Server couldn't be installed on this disk." I don't know how this can be, but I may have run software update earlier today.
    What should I try next? Should I erase the primary HD and try to install again? Or should I install the system software on the secondary HD? Or should I just try to reboot as is in the hope that the disk permission repairs did the trick...?
    Any helpful pointers would be greatly appreciated!

    Hello there, I came across your post when browsing the forum for passive advice. I am in the same boat as you and am a first timer for both of these tools. I work for a company who now needs to expand its network and database capabilities. I have been assigned this task and these are the tools i have opted for. I have not yet purchased them and i am pleased to find someone who has my desired setup. Could you please advise on the simplicity of the setup and whether an advanced knowledge is required.
    I want to use it in a mixed operating system environment. Is this possible?
    Regards
    Matthew

  • SQL Server 2005 replaced with SQL Server 2014 trying to connect front end Access as guest (read only ODBC)

    We have replaced a SQL Server 2005 with a SQL Server 2014 (new physical server.)  Have the new server set up to use SQL Server login OR Windows user login. Had old server connecting (for a particular DB) to front end Access (2010 or 2013) as guest for
    anyone logged into the Windows NT Network with a read only ODBC connection. Have the DB in the new server set to include guest as db_datareader (with only SELECT permission for the securables of each table and view being linked) but when any Windows user not
    specifically listed as a SQL DB user tries to use the front end they get an error of:
    Microsoft SQL Server Login
    Connection failed:
    SQL State: '28000'
    SQL Server Error: 18456
    [Microsoft][OCBC SQL Server Driver][SQL Server] Login failed for user {domain\user}.
    After closing that pop-up window a server login window appears. Of course, since the guest user is not specifically listed as a user in the DB that fails also. It seems like there should be a very simple solution to this, but I can't seem to find it. I want
    to allow anyone logged in on the Windows system (locally) to be able to open the MS Access file (on their work station machine) and run their own (read only; select) queries on the SQL Server database. Any suggestions?
    Thanks a billion in advance ----

    Thanks for the response Olaf. I have now spent weeks researching this. I realize that using the guest account in most situations is not advised. As mentioned, I have restricted the guest account to allow the db_datareader role only, and have explicitly denied
    all other roles, as well as allowing select only, and still have no access for the guest account.
    The suggested fix in the second link you provided, of using Windows groups is not plausible for my situation either. We are a scientific field research institution, with a few long term users and lots of users that may have Windows accounts for a few months,
    and then they are gone. It would be a nightmare for the network tech to try to keep a group account up to date, and we need to give access (read only, of course) to anyone logged into the system. Realize that the ONLY access of any kind to this database is
    thru MS Access ACCDB, using a (by default) read only OCDB connection.
    This type of access is used particularly because researchers need to be able to set up their own queries, and the MS Access query interface is particularly convenient for people who are not themselves SQL experts, yet are trying to get some very advanced
    levels of output. Putting the database online is not practical because then we are back to the need for a comprehensive query interface, and just picking up general subsets of the data online (from a basic web page search feature) would be out of the question,
    since the result set would involve hundreds of thousands if not millions of records.
    So - that said - what exactly would you suggest, assuming we don't have the funds to buy a whole new system, and have spent plenty of money with Microsoft's Enterprise level MS Office so that all work stations have MS Access, and Microsoft's SQL Server,
    as well as running our network on Microsoft's network software.

  • WIndows 7 64-bit system printing to a Windows 2000 server configured as a print server

    Is there any way to configure a new Windows 7 64-bit computer to use a Windows 2000 server configured as a print server ?
    The printer that I would like to connect to is an HP 4240n LaserJet. I appears that there is only a 64-bit Universal Print Driver available. The server currently uses HP 32-bit PCL5e or PCL6 drivers for all other connected computers. Connection is through a Hewlett-Packard Network Port, using DLC/LLC transport for the embedded 4240n print server.  
    Installing  the HP 64-bit UPD to the WIndows 7 64-bit system, and then attempting to redirect the local port to the Win2k network print server has not worked.
    Thanks for any advice.

    Hi:
    See if this works...
    Run msconfig.
    In the System Configuration screen, Boot tab, Advanced Options, if there is a check mark in the box next to Maximum memory. Remove that checkmark and save your changes.
    Reboot and hopefully Windows recognises all the Ram ( minus the reserved ) after restarting.
    Please give that a try, and post back and let us know if that frees up some system memory for you.
    Paul

  • Creating a connection pool using SQL Server 2000, Sun ONE Application Serve

    Has any one succesfully configured SQL Server 2000 to work with Sun ONE Application Server 7 on Windows 2000 server service pack 4? I am embarking on a new J2EE project and I need to configure it as soon as possible.
    The problem I am having is that, when I ping the data souce name, there is a connection error.
    I have set the data source name and other details as follows:
    Under JDBC, I have set the parameters for the connection pool as follows:
    Data Source Name:      com.microsoft.jdbc.sqlserver.SQLServerDriver
    Database Name:          jdbc:microsoft:sqlserver://localhost:1433;DatabaseName=Test
    User:               test
    Password:          test
    In the JVM settings page, I have set the prefix class path as follows for the location of the Microsoft JDBC
    drivers that I downloaded as follows:
    c:\microsoft\drivers/lib/msbase.jar
    c:\microsoft\drivers/lib/msutil.jar
    c:\microsoft\drivers/lib/mssqlserver.jar
    Under JVM Options, there is a strange setting which I don't understand: perhaps this is the cause of the
    connction error?
    -Djdbc.drivers=com.pointbase.jdbc.jdbcUniversalDriver
    Please help????

    I'm in a similar boat...
    Trying to setup AS7 JDBC and followed the instructions on the link you provided and get the following exception. I kept the case the same, thinking 'setpassword" was incorrect, so I tried changing the property to "Password", but get the same exception but it points to "setPassword" instead.
    SEVERE: RAR5041:Cannot get jdbc connection
    com.sun.enterprise.repository.J2EEResourceException
    java.lang.NoSuchMethodException: setpassword
    at com.sun.enterprise.repository.JdbcConnectionPool.createDataSource(JdbcConnectionPool.java:243)
    at com.sun.enterprise.resource.JdbcUrlAllocator.createResource(JdbcUrlAllocator.java:80)
    at com.sun.enterprise.resource.IASNonSharedResourcePool.createSteadyResources(IASNonSharedResourcePool.java:856)
    at com.sun.enterprise.resource.IASNonSharedResourcePool.initPool(IASNonSharedResourcePool.java:416)
    at com.sun.enterprise.resource.IASNonSharedResourcePool.internalGetResource(IASNonSharedResourcePool.java:625)
    at com.sun.enterprise.resource.IASNonSharedResourcePool.getResource(IASNonSharedResourcePool.java:520)
    at com.sun.enterprise.resource.PoolManagerImpl.getResourceFromPool(PoolManagerImpl.java:263)
    at com.sun.enterprise.resource.JdbcXAConnection.<init>(JdbcXAConnection.java:74)
    at com.sun.enterprise.resource.Jdbc10XaAllocator.createResource(Jdbc10XaAllocator.java:94)
    at com.sun.enterprise.resource.IASNonSharedResourcePool.createSteadyResources(IASNonSharedResourcePool.java:856)
    at com.sun.enterprise.resource.IASNonSharedResourcePool.initPool(IASNonSharedResourcePool.java:416)
    at com.sun.enterprise.resource.IASNonSharedResourcePool.internalGetResource(IASNonSharedResourcePool.java:625)
    at com.sun.enterprise.resource.IASNonSharedResourcePool.getResource(IASNonSharedResourcePool.java:520)
    at com.sun.enterprise.resource.PoolManagerImpl.getResourceFromPool(PoolManagerImpl.java:263)
    at com.sun.enterprise.resource.PoolManagerImpl.getResource(PoolManagerImpl.java:170)
    at com.sun.enterprise.resource.JdbcDataSource.internalGetConnection(JdbcDataSource.java:241)
    at com.sun.enterprise.resource.JdbcDataSource.getConnection(JdbcDataSource.java:98)
    at com.rvi.database.jdbcConnection.getConnection(jdbcConnection.java:93)
    at com.webapp.database.ArticlesDAO.selectByYear(ArticlesDAO.java:102)
    at com.webapp.actions.ArticleAction.list(ArticleAction.java:96)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.apache.struts.actions.DispatchAction.dispatchMethod(DispatchAction.java:280)
    at org.apache.struts.actions.DispatchAction.execute(DispatchAction.java:216)
    at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484)
    at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274)
    at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
    at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:507)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at org.apache.catalina.core.StandardWrapperValve.invokeServletService(StandardWrapperValve.java:720)
    at org.apache.catalina.core.StandardWrapperValve.access$000(StandardWrapperValve.java:118)
    at org.apache.catalina.core.StandardWrapperValve$1.run(StandardWrapperValve.java:278)
    at java.security.AccessController.doPrivileged(Native Method)
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:274)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:505)
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:212)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:505)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:203)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:505)
    at com.iplanet.ias.web.connector.nsapi.NSAPIProcessor.process(NSAPIProcessor.java:157)
    at com.iplanet.ias.web.WebContainer.service(WebContainer.java:598)

  • Is there a way in install a trial version of Project server on a Licensed edition server of sharepoint 2013?

    Is there a way in install a trial version of Project server on a Licensed edition server of sharepoint 2013? Is there anyway around this or do I need to make a new box all trial versions to test this out?
    Thanks
    James T.F

    James,
    Yes, it is possible , however I wont recommend to do it. Since, once Project trial period expires  you need to uninstall project server which can not be done without uninstalling SharePoint. Unless you are willing to rebuild the farm once your
    testing is completed
    Hrishi Deshpande
    Senior Consultant

Maybe you are looking for