CR Migration 2008 XI R3

Change in records per page/ page breaks after migrating to XI R3 Infoview from XI R2.
There is no issue with the CR 2008 Client. Format exactly matches with XI R2 client. The difference is with the XI R3 Infoview.
I compared the XI R3 Infoview Preferences settings with XI R2 Preferences. They are almost similar. How to get the exact XI R2 infoview Page Breaks / Records Per Page on XI R3 Infoview.
Thanks!

Simplified somewhat, what this report is doing is looking up open orders in one database and checking to see if something specific happened to it in another database.  If so, it generates the XML that needs to be applied to the first database to update it.  The XML references the order number and line number.  What I mean is that instead of the data coming out as
Order Line  XML Snippet
12345 1234 ...<order>12345</order><line>1234</line><status>received</status>...
22345 2234 ...<order>22345</order><line>2234</line><status>received</status>...
32345 3234 ...<order>32345</order><line>3234</line><status>received</status>...
42345 4234 ...<order>42345</order><line>4234</line><status>received</status>...
I get
Order Line  XML Snippet
12345 1234 ...<order>42345</order><line>4234</line><status>received</status>...
22345 2234 ...<order>42345</order><line>4234</line><status>received</status>...
32345 3234 ...<order>42345</order><line>4234</line><status>received</status>...
42345 4234 ...<order>42345</order><line>4234</line><status>received</status>...
I have Base Column Widths on Details, so there should be no merging attempted, but I'll check and make sure.
It seems to me, though, that the DLL is being told the wrong value to export...
Carl

Similar Messages

  • 2008 and 2014 side by side

    Hi
    Can we install SQL Server 2014 std on a server which already has 2008 std installed so we can migrate 2008 apps gradually?
    Thanks
    Regads

    Yes, You can have a new named SQL 2014 instance.
    http://thomaslarock.com/2014/06/upgrading-to-sql-server-2014-a-dozen-things-to-check/
    --Prashanth

  • SQL 2008 to 2014

    Hi
    I have 2008 std and 2014 std installed side by side on the same server. How do I migrate 2008 dbs to 2014 so they are also upgraded to 2014 db format?
    Thanks
    Regards

    Hello,
    You can perform backup/restore and detach/attach methods.
    https://msdn.microsoft.com/en-us/library/ms187510.aspx
    https://msdn.microsoft.com/en-us/library/ms177429.aspx
    https://msdn.microsoft.com/en-us/library/ms189625.aspx
    You can use the following article to transfer SQL Server logins, if needed.
    http://support.microsoft.com/kb/918992
    Hope this helps.
    Regards,
    Alberto Morillo
    SQLCoffee.com

  • Launch VSTA Editor Requires Administrator Privs?

    This is a follow-up to another posting I had about problems with launching the VSTA editor from various scripts.  I have been experimenting with this further and while available RAM seems to have something to do with it, more clearly appears to be that
    launching VSTA requires me to be logged on as administrator.  IT security only allows us developers to get Admin for one hour at a time -- have to request it, log off, then log back on.  After an hour it expires and we would have to request again,
    log off and then back on yet again for another hour.  Needless to say, this would be rather frustrating.   Any ideas about how/why launching VSTA from SSDT script tasks or components would require administrator privs and how I could get around that?
    Thanks kindly,
    Mike

    Hi Mike,
    Thanks for the note.  Unfortunately, things are still frustrating us.  I tried your suggestions and the VSTA editor still will not open.
     I actually completely re-formatted my machine (Windows 7) and applied Windows updates.  Then I only installed BI tools (our BI group has an install setup from a share that installs SQL Server Data Tools for Visual Studio 2012 (I was unable to insert
    an image -- kept getting a note about not being able to link images until my account has been confirmed -- that's new.    I then opened my migrated 2008 Solution and a package that included a Task Script and clicked "Edit Script".  Even with
    ONLY those applications installed on my box the VSTA editor will not open.  I then installed the tools you noted above (Runtime and Design-time for 64 bit) and VSTA editor will still not open.  Each time I even just open SQL Server Data Tools for
    VS 2012 Windows Event log captures the errors I pasted below -- one about VS 2012 being incompatible with this version of windows and one security event (Audit Failure) that indicates "Sensitive Privilege Use".   
    Another colleague had one machine where the VSTA editor in 2012 was reliably opening for him but then he imported (and converted) a 2008 package
    and now the editor will no longer open for him either.   On my machine I did not try simply creating a new package in SQL Server Data Tools for VS 2012 and see if that worked.   On a VMWare instance that can be easily created we are going to try
    a fresh Windows 7 install with just SSDT for VS2012 and create a new package with a Script Task to see if that works.  If that works we are starting to think there is something in the 2008 packages that breaks the VSTA editor when they are opened in 2012???
     Does that make any sense at all?
    Log Name:
     Application Source:
         Microsoft-Windows-ApplicationExperienceInfrastructure Date:          4/23/2014
    9:22:31 AM Event ID:      1 Task Category: None Level:         Warning Keywords:       User:          MFAD\mjg32 Computer:      R0207781.mfad.mfroot.org Description:
    The application (Visual Studio 2012, from vendor Microsoft) has the following problem: Visual Studio 2012 is incompatible with this version of Windows. For more information, contact Microsoft. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>     <Provider Name="Microsoft-Windows-ApplicationExperienceInfrastructure" Guid="{5EC13D8E-4B3F-422E-A7E7-3121A1D90C7A}" />     <EventID>1</EventID>     <Version>0</Version>
        <Level>3</Level>     <Task>0</Task>     <Opcode>2</Opcode>     <Keywords>0x8000000000000000</Keywords>     <TimeCreated SystemTime="2014-04-23T14:22:31.218012400Z"
    />     <EventRecordID>10213</EventRecordID>     <Correlation />     <Execution ProcessID="7256" ThreadID="3400" />     <Channel>Application</Channel>     <Computer>R0207781.mfad.mfroot.org</Computer>
        <Security UserID="S-1-5-21-2996307970-2646299502-106099678-50135" />   </System>   <EventData>     <Data Name="DBType">15</Data>     <Data Name="AppNameCount">19</Data>  
      <Data Name="AppName">Visual Studio 2012</Data>     <Data Name="VendorNameCount">10</Data>     <Data Name="VendorName">Microsoft</Data>     <Data Name="SummaryCount">106</Data>
        <Data Name="Summary">Visual Studio 2012 is incompatible with this version of Windows. For more information, contact Microsoft.</Data>     <Data Name="SessionID">1</Data>   </EventData> </Event>
    Log Name:      Security
    Source:        Microsoft-Windows-Security-Auditing
    Date:          4/23/2014 9:24:30 AM
    Event ID:      4673 Task Category: Sensitive Privilege Use
    Level:         Information
    Keywords:      Audit Failure User:          N/A
    Computer:      R0207781.mfad.mfroot.org
    Description: A privileged service was called.
    Subject:            
    Security ID:                 
    MFAD\mjg32            
    Account Name:                       
    mjg32            
    Account Domain:                    
    MFAD            
    Logon ID:                    
    0x1a92c Service:            
    Server: Security            
    Service Name: - Process:            
    Process ID:      0x1d7c            
    Process Name:           
    C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\devenv.exe
    Service Request Information:            
    Privileges:                   
    SeCreateGlobalPrivilege Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>     <Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-A5BA-3E3B0328C30D}" />
        <EventID>4673</EventID>
        <Version>0</Version>     <Level>0</Level>
        <Task>13056</Task>
        <Opcode>0</Opcode>     <Keywords>0x8010000000000000</Keywords>
        <TimeCreated SystemTime="2014-04-23T14:24:30.502939700Z" />
        <EventRecordID>49848</EventRecordID>
        <Correlation />     <Execution ProcessID="612" ThreadID="640" />
        <Channel>Security</Channel>
        <Computer>R0207781.mfad.mfroot.org</Computer>
        <Security />   </System>
      <EventData>     <Data Name="SubjectUserSid">S-1-5-21-2996307970-2646299502-106099678-50135</Data>
        <Data Name="SubjectUserName">mjg32</Data>
        <Data Name="SubjectDomainName">MFAD</Data>
        <Data Name="SubjectLogonId">0x1a92c</Data>
        <Data Name="ObjectServer">Security</Data>
        <Data Name="Service">-</Data>
        <Data Name="PrivilegeList">SeCreateGlobalPrivilege</Data>
        <Data Name="ProcessId">0x1d7c</Data>
        <Data Name="ProcessName">C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\devenv.exe</Data>
      </EventData> </Event>
    Log Name:      Security
    Source:        Microsoft-Windows-Security-Auditing
    Date:          4/23/2014 9:24:30 AM
    Event ID:      4673 Task Category: Sensitive Privilege Use
    Level:         Information
    Keywords:      Audit Failure User:          N/A
    Computer:      R0207781.mfad.mfroot.org
    Description: A privileged service was called.
    Subject:            
    Security ID:                 
    MFAD\mjg32            
    Account Name:                       
    mjg32            
    Account Domain:                    
    MFAD            
    Logon ID:                    
    0x1a92c Service:            
    Server: Security            
    Service Name: - Process:            
    Process ID:      0x1d7c            
    Process Name:           
    C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\devenv.exe
    Service Request Information:            
    Privileges:                   
    SeCreateGlobalPrivilege Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>     <Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-A5BA-3E3B0328C30D}" />
        <EventID>4673</EventID>
        <Version>0</Version>     <Level>0</Level>
        <Task>13056</Task>
        <Opcode>0</Opcode>     <Keywords>0x8010000000000000</Keywords>
        <TimeCreated SystemTime="2014-04-23T14:24:30.502939700Z" />
        <EventRecordID>49848</EventRecordID>
        <Correlation />     <Execution ProcessID="612" ThreadID="640" />
        <Channel>Security</Channel>
        <Computer>R0207781.mfad.mfroot.org</Computer>
        <Security />   </System>
      <EventData>     <Data Name="SubjectUserSid">S-1-5-21-2996307970-2646299502-106099678-50135</Data>
        <Data Name="SubjectUserName">mjg32</Data>
        <Data Name="SubjectDomainName">MFAD</Data>
        <Data Name="SubjectLogonId">0x1a92c</Data>
        <Data Name="ObjectServer">Security</Data>
        <Data Name="Service">-</Data>
        <Data Name="PrivilegeList">SeCreateGlobalPrivilege</Data>
        <Data Name="ProcessId">0x1d7c</Data>
        <Data Name="ProcessName">C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\devenv.exe</Data>
      </EventData> </Event>

  • Need help with Microsoft Office for Mac upgrade question.

    My MacBook died, great computer after six years! I just purchased my new MacBook Pro last night. I noticed that the MacBook Pro/OS X Lion does not support PPC software as I was trying to install MS Office 2004, which I have the 2008 upgrade for. Since the 2008 is just the upgrade it wants a previous version already installed and I cannot install 2004 MS Office, does this mean that I have to start over and just buy MS Office 2011?

    I'm afraid so. Too bad you didn't apply the 2008 upgrade while your old MacBook was working. Then you could have migrated 2008 to the new machine from the MacBook's hard drive even if the rest of the MacBook was dead.

  • Migrating to new macbook air with Lion, entourage 2008 doesn't work

    I  bought a new macbook air with lion installed. trying to migrate data from my old macbook with snow leopard. Got most data across, and installed my most frequently used applications:
    - office 2008: most office apps 2008 work, if buggily. entourage not, see below.
    - firefox (hangs up when downloading updates)
    - dropbox (ditto)
    <these two problems may have something to do with internet proxy settings, will try to sort that out later>
    MAIN ISSUE:
    entourage wont open at all.  so for now i'm using my old comp for e-mail and the new for the rest.
    MY OPTIONS:
    please advise (1) what you think is the most time & nerve-saving option (2) how to do it smoothly:
    A) try to get office 2008 to work.
    when trying to open entourage, it tells me this version (office 2008 12.0) cannot open this entourage database (12.3)
    error for other apps says there is a problem with database, and rebuilding several times did not fix it.
    would have to start with updating to the version i used last (office 2008 12.3). Problem is the ms office updater does not seem to work on lion. the first update does not open, says it does not support powermac.
    B) buying office 2011, and migrating entourage 2008 to outlook.
    I suppose the best way to do this is to install office 2011 on the old mac first, then on the new one, then move database, right?
    C) migrating from entourage 2008 to lion mail.
    best way to do this would be to import entourage email to leopard mail, then move those files to the new mac?  and move entourage addresses into the mac addressbook. my major concern is that i have a lot of mailing rules, and a fair bunch of notes. a lot. i;d rather not have to recreate those by hand. Is there a way to import rules from entourage to mail?
    i also habe a huge backstock of mail, over 10,000, and a correspondigly huge addressbook (within entourage). i'm ready to abandon entourage at last (though i used it for a decade), but i want to have my addresses, my rules, and at least the last 3 yrs of emails. i get about 130 mails a day so i need plenty of automatic organizing capability.
    i never had issues  my old mac/snow leopard, i just ran out of ram and the one usb broke, so i figured it's time. kinda sorry i did not just get the usb repaired and extra ram. what a hassle these migrations always are.
    cheers!
    maedi

    Kappy wrote:
    Yes, repairing first is a sound idea. In my experience I've only moved from Entourage to the OS X applications or from one version of Entourage to another. In the latter I've been able to just copy over the Microsoft User Data folder. But I have not used Entourage for quite some time.
    Microsoft don't make it quite that easy to migrate to their own applications, but the import from a 'tidy' .rge file works well, I had a lot of issues with the first few I migrated but after performing a database repair prior to import all proceeded smoothly.

  • Problems after print server migration to Windows Server 2008 R2

    Hi all,
    New forum member, first time poster. I am at my wits end and have concussion from banging my head on the desk for several days running. Hopefully someone here may be able to help.
    Environment
    I have recently moved our printing environment from a Windows Server 2003 machine to a new Server 2008 R2 machine in prep for rolling out Windows 7 x64 clients. We have 30-40 printers, majority of which are HP's (M2727's, P4015dn's, CM3530's, P2035's & a CM8060).
    My procedure for setting up the printers on the new server involved manually creating each printer and using up-to-date drivers, we wanted to start fresh. The HP's are all using the HP Universal PCL 5 or PCL 6 (61.115.1.10527) x86 & x64 driver. We use Desktop Authority on logon to install the required printers for each client.
    Problems
    Since everyone is now running through the 2008 R2 server we have had a bunch of intermittent problems pop up all over the place, mostly with our HP printers. When using the PCL6 driver some applications print a page or 10 of garbled gibberish (wingdings etc), so most printers are now using the PCL5 driver. Other applications print the error "PCL XL error" when using PCL6. Sometimes reinstalling the printer on the client machine will resolve these errors, however they tend to resurface.
    When we use the PCL5 driver our M2727's intermittently report "Out Of Memory" on the printer display (they are stock with 64M RAM each) - upgrading the RAM may fix this but we never had this problem before on the 2003 server. This problem is not specific to the size of the printed document - it could be a 20 page report or a 2 page excel document. Resetting the printer will generally clear this issue temporarily. This is currently our most annoying/biggest issue.
    Some people are having issues printing to a FujiXerox 340A-AP printer - in particular 1 person is able to print fine, where as another prints and the print margin appears to be far too small. After confirming all print margins on the server then reinstalling the printer on the client machine, the problem still persists. We have two FujiXerox printers, the second one is working as intended for 8-10 users with the exact same settings.
    Attempted Fixes
    These are some of the attempted fixes that I have tried:
    Turning it off and on
    Upgrading the firmware on the M2727's to resolve garbled printing & out of memory
    Upgrading the firmware on the CM3530's to resolve garbled printing
    Reinstalling all HP Universal PCL5/PCL6 x86 & x64 drivers on the print server
    Ensuring that the 2008 R2 server is 100% up-to-date with MS patches
    Backing up all printers on print server, removing the print server role, deleting all printers & drivers, rebooting, reinstalling the print server role and restoring all printers from backup
    Upgraded Desktop Authority to the latest version - as this application is in charge of installing the printers on logon
    As you can see we are having a lot of problems and nothing seems to make any sense. None of this happened before Windows Server 2008 R2 was brought in to the equation.
    If anyone is able to provide any assistance that would be greatly appreciated.
    Many thanks,
    Hartz.
    tldr; our printers are screwed since migrating to Windows Server 2008 R2.

    Hi all,
    New forum member, first time poster. I am at my wits end and have concussion from banging my head on the desk for several days running. Hopefully someone here may be able to help.
    Environment
    I have recently moved our printing environment from a Windows Server 2003 machine to a new Server 2008 R2 machine in prep for rolling out Windows 7 x64 clients. We have 30-40 printers, majority of which are HP's (M2727's, P4015dn's, CM3530's, P2035's & a CM8060).
    My procedure for setting up the printers on the new server involved manually creating each printer and using up-to-date drivers, we wanted to start fresh. The HP's are all using the HP Universal PCL 5 or PCL 6 (61.115.1.10527) x86 & x64 driver. We use Desktop Authority on logon to install the required printers for each client.
    Problems
    Since everyone is now running through the 2008 R2 server we have had a bunch of intermittent problems pop up all over the place, mostly with our HP printers. When using the PCL6 driver some applications print a page or 10 of garbled gibberish (wingdings etc), so most printers are now using the PCL5 driver. Other applications print the error "PCL XL error" when using PCL6. Sometimes reinstalling the printer on the client machine will resolve these errors, however they tend to resurface.
    When we use the PCL5 driver our M2727's intermittently report "Out Of Memory" on the printer display (they are stock with 64M RAM each) - upgrading the RAM may fix this but we never had this problem before on the 2003 server. This problem is not specific to the size of the printed document - it could be a 20 page report or a 2 page excel document. Resetting the printer will generally clear this issue temporarily. This is currently our most annoying/biggest issue.
    Some people are having issues printing to a FujiXerox 340A-AP printer - in particular 1 person is able to print fine, where as another prints and the print margin appears to be far too small. After confirming all print margins on the server then reinstalling the printer on the client machine, the problem still persists. We have two FujiXerox printers, the second one is working as intended for 8-10 users with the exact same settings.
    Attempted Fixes
    These are some of the attempted fixes that I have tried:
    Turning it off and on
    Upgrading the firmware on the M2727's to resolve garbled printing & out of memory
    Upgrading the firmware on the CM3530's to resolve garbled printing
    Reinstalling all HP Universal PCL5/PCL6 x86 & x64 drivers on the print server
    Ensuring that the 2008 R2 server is 100% up-to-date with MS patches
    Backing up all printers on print server, removing the print server role, deleting all printers & drivers, rebooting, reinstalling the print server role and restoring all printers from backup
    Upgraded Desktop Authority to the latest version - as this application is in charge of installing the printers on logon
    As you can see we are having a lot of problems and nothing seems to make any sense. None of this happened before Windows Server 2008 R2 was brought in to the equation.
    If anyone is able to provide any assistance that would be greatly appreciated.
    Many thanks,
    Hartz.
    tldr; our printers are screwed since migrating to Windows Server 2008 R2.

  • Events 1863 and 2093 post SBS 2003 SP2 Migration to 2008 R2 SP1

    I have migrated AD from a 2003 SBS SP2 server to a 2008 R2 SP1 server using the following article: http://technet.microsoft.com/en-us/library/dd379526.aspx
    I realize now that this was not the right article as it is for 2003 SP2 Standard, however I don't need to migrate Exchange or other applications.
    That was 3 days ago, yesterday morning I noticed the following events in the 2008 error log: Error 1863 and Warning 2093
    There appears to be no issue with the domain currently, everyone was able to login in without issue this morning. Both servers are continuing to run, although I plan to demote the 2003 and decommission the hardware if there are no issues (as advised by the
    post-migration instructions of the above article). I don't need the 2003 SBS server anymore, should I just transfer the FSMO's now and demote the server?
    I can provide full text of the events, but I have removed identifying information:
    Log Name:      Directory Service
    Source:        Microsoft-Windows-ActiveDirectory_DomainService
    Date:          2/17/2014 4:18:14 AM
    Event ID:      1863
    Task Category: Replication
    Level:         Error
    Keywords:      Classic
    User:          ANONYMOUS LOGON
    Computer:     SERVERNEW.generic.local
    Description:
    This is the replication status for the following directory partition on this directory server.
    Directory partition:
    CN=Schema,CN=Configuration,DC=generic,DC=local
    This directory server has not received replication information from a number of directory servers within the configured latency interval.
    Latency Interval (Hours):
    24
    Number of directory servers in all sites:
    1
    Number of directory servers in this site:
    1
    The latency interval can be modified with the following registry key.
    Registry Key:
    HKLM\System\CurrentControlSet\Services\NTDS\Parameters\Replicator latency error interval (hours)
    To identify the directory servers by name, use the dcdiag.exe tool.
    You can also use the support tool repadmin.exe to display the replication latencies of the directory servers.   The command is "repadmin /showvector /latency <partition-dn>".
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-ActiveDirectory_DomainService" Guid="{0e8478c5-3605-4e8c-8497-1e730c959516}" EventSourceName="NTDS KCC" />
        <EventID Qualifiers="49152">1863</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>5</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8080000000000000</Keywords>
        <TimeCreated SystemTime="2014-02-17T09:18:14.599176800Z" />
        <EventRecordID>243</EventRecordID>
        <Correlation />
        <Execution ProcessID="504" ThreadID="660" />
        <Channel>Directory Service</Channel>
        <Computer>SERVERNEW.generic.local</Computer>
        <Security UserID="S-1-5-7" />
      </System>
      <EventData>
        <Data>CN=Schema,CN=Configuration,DC=generic,DC=local</Data>
        <Data>1</Data>
        <Data>1</Data>
        <Data>24</Data>
        <Data>System\CurrentControlSet\Services\NTDS\Parameters</Data>
      </EventData>
    </Event>
    Log Name:      Directory Service
    Source:        Microsoft-Windows-ActiveDirectory_DomainService
    Date:          2/17/2014 4:18:14 AM
    Event ID:      2093
    Task Category: Replication
    Level:         Warning
    Keywords:      Classic
    User:          ANONYMOUS LOGON
    Computer:      SERVERNEW.generic.local
    Description:
    The remote server which is the owner of a FSMO role is not responding.  This server has not replicated with the FSMO role owner recently.
    Operations which require contacting a FSMO operation master will fail until this condition is corrected.
    FSMO Role: CN=Schema,CN=Configuration,DC=generic,DC=local
    FSMO Server DN: CN=NTDS Settings,CN=SERVEROLD,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=generic,DC=local
    Latency threshold (hours): 24
    Elapsed time since last successful replication (hours): 25
    User Action:
    This server has not replicated successfully with the FSMO role holder server.
    1. The FSMO role holder server may be down or not responding. Please address the problem with this server.
    2. Determine whether the role is set properly on the FSMO role holder server. If the role needs to be adjusted, utilize NTDSUTIL.EXE to transfer or seize the role. This may be done using the steps provided in KB articles 255504 and 324801 on http://support.microsoft.com.
    3. If the FSMO role holder server used to be a domain controller, but was not demoted successfully, then the objects representing that server are still in the forest. This can occur if a domain controller has its operating system reinstalled or if a forced
    removal is performed.  These lingering state objects should be removed using the NTDSUTIL.EXE metadata cleanup function.
    4. The FSMO role holder may not be a direct replication partner. If it is an indirect or transitive partner, then there are one or more intermediate replication partners through which replication data must flow. The total end to end replication latency should
    be smaller than the replication latency threshold, or else this warning may be reported prematurely.
    5. Replication is blocked somewhere along the path of servers between the FSMO role holder server and this server.  Consult your forest topology plan to determine the likely route for replication between these servers. Check the status of replication using
    repadmin /showrepl at each of these servers.
    The following operations may be impacted:
    Schema: You will no longer be able to modify the schema for this forest.
    Domain Naming: You will no longer be able to add or remove domains from this forest.
    PDC: You will no longer be able to perform primary domain controller operations, such as Group Policy updates and password resets for non-Active Directory Domain Services accounts.
    RID: You will not be able to allocation new security identifiers for new user accounts, computer accounts or security groups.
    Infrastructure: Cross-domain name references, such as universal group memberships, will not be updated properly if their target object is moved or renamed.

    Hi JPowered,
    Thank you for posting your issue in the forum.
    I am trying to involve someone familiar with this topic to further look at this issue. There might be some time delay. Appreciate your patience.
    Thank you for your understanding and support.
    Best Regards,
    Justin Gu

  • HT204350 Hey, migration from an old mac late 2008 aluminium to a brand new mac book air. Only the new one has firewire. Transmissiom via wifi estimates ~50h. Is there a faster Way to sync? Tanks in advance

    Hey, migration from an old mac late 2008 aluminium to a brand new mac book air. Only the new one has firewire. Transmissiom via wifi estimates ~50h. Is there a faster Way to sync? Tanks in advance

    I'll venture that your problem here is that you're using two very different versions of Mac OS X.  The USB adapter has been useful to me when making big downloads or while using other networks, but it might not be your case. 
    Here's what I would advise, though it may be less than stellar:  Copy the files you need into folders and move them through a USB flash drive or using that external hard drive of yours. (Could the format be the reason your MBA can't see it?). Some stuff like calendars and contacts can be exported too. At least in Lion, I haven't used Tiger in a while. 
    Good luck.

  • SSRS 2012: Report Header PrintOnFirstPage-problem after report migration from SSRS 2008

    Hi ,
    I developed my report using VS 2008 IDE and the report header property "PrintOnFirstPage" is set to False.
    The content of the header are some textboxes and lines that should show only on page number > 1.
    This works fine in VS 2008 IDE in preview mode as well as with reports rendered by SSRS 2008 report server.
    Recently I migrate&convert the same report to SSRS 2012 I noticed a different rendering behaviour of my report.
    So in VS 2010 preview mode, the page headers content (textboxe etc.)  is not visible on first page but the headers space did not colapse as it does in VS 2008 IDE preview mode.
    I checked all the report properties but unable to find a solution to my problem.
    I was able to reprduce the same behaviour by creating a new report using VS2010 IDE.
    Any ideas are greatly appreciated
    Thanks
    Bodo

    Hi BodoHH,
    I have tested on my local enviorment and can't reproduce the issue, the issue can be caused by many factors, it can be caused by the properties setting and can also caused by the visual studio, Detais information below for your reference:
    As you mentioned that you have check all the report properties, please also check the tablix,Page Header,report body properties to see if the size are the same with that in the SSRS2008.
    Please open this rdl report in the report builder to see if the print layout is correct, if it works fine, the issue can be caused by the visual studio.
    Please also try to upload the rdl report to report manager to check the layout.
    Please also provide the snaphot of the layout in VS2010 to let us better analysis about the issue.
    If you still have any problem, please feel free to ask.
    Regards,
    Vicky Liu
    If you have any feedback on our support, please click
    here.
    Vicky Liu
    TechNet Community Support

  • Events 1863 and 2093 post 2003 Migration to 2008 R2

    I have migrated AD from a 2003 SBS SP2 server to a 2008 R2 SP1 server using the following article: http://technet.microsoft.com/en-us/library/dd379526.aspx
    That was 2 days ago, this morning I noticed the following events in the 2008 error log: Error 1863 and Warning 2093
    There appears to be no issue with the domain currently, everyone was able to login in without issue this morning. Both servers are continuing to run, although I plan to demote the 2003 and decommission the hardware if there are no issues (as advised by the
    post-migration instructions of the above article). I can provide full text of the events, but I have removed identifying information:
    Log Name:      Directory Service
    Source:        Microsoft-Windows-ActiveDirectory_DomainService
    Date:          2/17/2014 4:18:14 AM
    Event ID:      1863
    Task Category: Replication
    Level:         Error
    Keywords:      Classic
    User:          ANONYMOUS LOGON
    Computer:     SERVERNEW.generic.local
    Description:
    This is the replication status for the following directory partition on this directory server.
    Directory partition:
    CN=Schema,CN=Configuration,DC=generic,DC=local
    This directory server has not received replication information from a number of directory servers within the configured latency interval.
    Latency Interval (Hours):
    24
    Number of directory servers in all sites:
    1
    Number of directory servers in this site:
    1
    The latency interval can be modified with the following registry key.
    Registry Key:
    HKLM\System\CurrentControlSet\Services\NTDS\Parameters\Replicator latency error interval (hours)
    To identify the directory servers by name, use the dcdiag.exe tool.
    You can also use the support tool repadmin.exe to display the replication latencies of the directory servers.   The command is "repadmin /showvector /latency <partition-dn>".
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-ActiveDirectory_DomainService" Guid="{0e8478c5-3605-4e8c-8497-1e730c959516}" EventSourceName="NTDS KCC" />
        <EventID Qualifiers="49152">1863</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>5</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8080000000000000</Keywords>
        <TimeCreated SystemTime="2014-02-17T09:18:14.599176800Z" />
        <EventRecordID>243</EventRecordID>
        <Correlation />
        <Execution ProcessID="504" ThreadID="660" />
        <Channel>Directory Service</Channel>
        <Computer>SERVERNEW.generic.local</Computer>
        <Security UserID="S-1-5-7" />
      </System>
      <EventData>
        <Data>CN=Schema,CN=Configuration,DC=generic,DC=local</Data>
        <Data>1</Data>
        <Data>1</Data>
        <Data>24</Data>
        <Data>System\CurrentControlSet\Services\NTDS\Parameters</Data>
      </EventData>
    </Event>
    Log Name:      Directory Service
    Source:        Microsoft-Windows-ActiveDirectory_DomainService
    Date:          2/17/2014 4:18:14 AM
    Event ID:      2093
    Task Category: Replication
    Level:         Warning
    Keywords:      Classic
    User:          ANONYMOUS LOGON
    Computer:      SERVERNEW.generic.local
    Description:
    The remote server which is the owner of a FSMO role is not responding.  This server has not replicated with the FSMO role owner recently.
    Operations which require contacting a FSMO operation master will fail until this condition is corrected.
    FSMO Role: CN=Schema,CN=Configuration,DC=generic,DC=local
    FSMO Server DN: CN=NTDS Settings,CN=SERVEROLD,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=generic,DC=local
    Latency threshold (hours): 24
    Elapsed time since last successful replication (hours): 25
    User Action:
    This server has not replicated successfully with the FSMO role holder server.
    1. The FSMO role holder server may be down or not responding. Please address the problem with this server.
    2. Determine whether the role is set properly on the FSMO role holder server. If the role needs to be adjusted, utilize NTDSUTIL.EXE to transfer or seize the role. This may be done using the steps provided in KB articles 255504 and 324801 on http://support.microsoft.com.
    3. If the FSMO role holder server used to be a domain controller, but was not demoted successfully, then the objects representing that server are still in the forest. This can occur if a domain controller has its operating system reinstalled or if a forced
    removal is performed.  These lingering state objects should be removed using the NTDSUTIL.EXE metadata cleanup function.
    4. The FSMO role holder may not be a direct replication partner. If it is an indirect or transitive partner, then there are one or more intermediate replication partners through which replication data must flow. The total end to end replication latency should
    be smaller than the replication latency threshold, or else this warning may be reported prematurely.
    5. Replication is blocked somewhere along the path of servers between the FSMO role holder server and this server.  Consult your forest topology plan to determine the likely route for replication between these servers. Check the status of replication using
    repadmin /showrepl at each of these servers.
    The following operations may be impacted:
    Schema: You will no longer be able to modify the schema for this forest.
    Domain Naming: You will no longer be able to add or remove domains from this forest.
    PDC: You will no longer be able to perform primary domain controller operations, such as Group Policy updates and password resets for non-Active Directory Domain Services accounts.
    RID: You will not be able to allocation new security identifiers for new user accounts, computer accounts or security groups.
    Infrastructure: Cross-domain name references, such as universal group memberships, will not be updated properly if their target object is moved or renamed.

    Hi,
    The guide you are using is not for SBS. If you look at the detailed supported migration scenarios you will see this matrix:
    Source server   processor
    Source server operating system
    Destination server operating system
    Destination server processor
    x86- or x64-based
    Windows Server 2003 with Service Pack 2 (SP2)
    Windows Server 2008 R2, both full and Server Core installation   options
    x64-based
    x86- or x64-based
    Windows Server 2003 R2
    Windows Server 2008 R2, both full and Server Core installation   options
    x64-based
    x86- or x64-based
    Windows Server 2008, both full and Server Core   installation options
    Windows Server 2008 R2, both full and Server Core installation   options
    x64-based
    x64-based
    Windows Server 2008 R2
    Windows Server 2008 R2, both full and Server Core installation   options
    x64-based
    x64-based
    Server Core installation option of Windows Server 2008 R2
    Windows Server 2008 R2, both full and Server Core installation   options
    x64-based
    There is no Small Business Server specified.
    This forum is not really for SBS migrations and you can also ask on the SBS forums
    for better advice about SBS.
    And yes, if you want to decommission the SBS server, running as a DC, you will at some point have to transfer the FSMO roles to the destination server. Please follow the steps in the guide I posted earlier to migrate the roles or applications that you need.
    And also ask more details on the SBS forums.
    Marius
    http://mariusene.wordpress.com/

  • SSIS PACKAGE MIGRATION FROM 2005 to 2008 - Script task/component errors

    HI All,
    We have to migrate ssis packages (about 300) from ssis 2005 to 2008 .
    1. I understand that the major concern is regarding the script component/tasks.
    I searched a lot about this and also consulted with many friends , all of them are aware of this issue but not able to provide what could be the issues and the solution.
    Can some one help me with the common script issues that can happen during migration and the solution for the same.
     2. I do have one more question.
    As per my understanding given in the below link 
    http://blogs.msdn.com/b/mattm/archive/2008/03/21/package-upgrade-wizard.aspx
    there is this part which says ... 
    Once the packages have been chosen, the next page asks you to pick the output location. This can be:
    Same as the source location
    File System
    SSIS Service (Package Store)
    SQL Server 
    Does this mean I can deploy in sql server directly on fly while upgrading ?
    Any help highly appreciated .
    Regards
    Praveen..

    Hi Praveen,
    Question 1: The error may occur if there are duplicate input columns in the Script Task/Component or the current user cannot access the C:\Windows\Temp directory. Except for the link provided by SanBhaumik, you can also refer to the following
    threads:
    http://www.sqlservercentral.com/Forums/Topic811208-148-1.aspx 
    http://social.technet.microsoft.com/Forums/sqlserver/en-US/5c11eb57-59d6-4f81-bfdc-13bd6489a0ac/sql-server-2008-ssis-package-script-component-error?forum=sqlintegrationservices 
    Question 2: We can directly save the package to the File System, SSIS Package Store, or SQL Server by selecting the proper destination during the package upgrade. However, this operation is not equal to the package install operation identically.
    For example, if we have enabled package configurations for a package, the package configurations won’t be upgraded or installed during the package upgrade.
    Regards,
    Mike Yin
    TechNet Community Support

  • Issue in Web Service after the Windows migration from 2003 to 2008

    My application is a web service and it was working fine in windows server 2003 .after it was migrated to 2008 ,the web service is working fine and but when its consumed in another web application which is also migrated to windows server 2008 ,its saying
    "request channel  timed out while waiting for a reply for 00:30:29.9820000.Increase the time out value passed to the request or increase the SendTimeout value on the binding .the time alloted to this operation may have been a portion of
    a longer time out" error.The iis setting of my application in production has anonymous authentication enabled but the kerberos is not generating tokens and hence its also not working fine.When we disable the anonymous authentication the kerberos
    token is generated but the application is prompting for credentails.Please help me to resolve the issue

    Hi,
    Since this issue is more related to IIS, I suggest you refer to IIS forum below to get more efficient support:
    http://forums.iis.net/
    Best Regards,
    Amy

  • Server 2003 R2 DC migration to 2008 R2 worked? but exchange 2007 has stopped

    Hi everyone,
    This is a single DC running on Server 2003 R2 which I migrated to a fresh install of Server 2008 R2. This appears to have worked without issue. DNS is working dcdiag and netdiag didn't report problems.
    When I demote the 2003 server however Exchange 2007 stops working. It appears that it is still looking to talk to the 2003 server based on this
    EVENT ID: 2012 All DC Servers in use are not responding DC.mydomain.com
    Can anyone help fix this issue pls. I cant find where Exchange has stored the old domain name.
    TYIA

    TY both for taking the time to reply.
    I have gotten to the problem. The fact you both pointed me to event 2080 was instrumental in guiding me down the right path. Once I read this MS article I could see the new DC was missing
    the SACL rights. This was a tad frustrating as I had previously checked that Manage auditing and security log was correctly configured in the Default Domain Controllers Policy, was applied to Domain
    computers and the new server was in the correct container.
    However when your up to your ass in a croc filled swamp you sometimes forget the odd thing; I didn't run RSOP, if I had at the time, I would have never have had to post for help. Yes you guessed it the policy wasn't enabled!! A quick enable and gpupdate
    /force and all was well.
    Still, always the optimist, I learned about event 2080, and uncovered and fixed problems with the clients servers where they had ghost nics....
    Just to clarify in case others read this post.
    This wan't SBS
    It was a single DC domain running on server 2003 R2 x64
    Exchange 2007 running on a seperate server 2003 R2 x64.
    The domain name didn't change. What I meant was the new DC had a different name
    the New DC is a fresh install of server 2008 R2,  IPv6 is enabled
    The old DC had adprep /forestprep then adprep /domainprep run on it
    The 5 fsmo roles were moved from the old DC to the 2008 DC
    Just need to move DHCP and other bits n pieces and job done :)
    Thanks for the help

  • I just upgraded from my 2008 MacBook to a new Macbook Pro. How do I get my time capsule to work on my new MacBook? I did data migration, but the time capsule did not pick it up. Any ideas?

    I just upgraded from my 2008 MacBook to a new Macbook Pro. How do I get my time capsule to work on my new MacBook? I did data migration, but the time capsule did not pick it up. Any ideas?

    If you migrated all the info from time machine to your new MBP. The TM will usually ask to connect to the old backups.. sorry I am not sure is this what you want to do.. Personally I think you start a fresh backup.
    BTW Time Capsule does not do anything.. it is a dumb hard disk in a box.. it is TM that does everything.
    Look at B5 and B6 here about connecting to your backup.
    http://pondini.org/TM/Troubleshooting.html

Maybe you are looking for